WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] swiotlb=force in Konrad's xen-pcifront-0.8.2 pvops domU

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] swiotlb=force in Konrad's xen-pcifront-0.8.2 pvops domU kernel with PCI passthrough
From: Dante Cinco <dantecinco@xxxxxxxxx>
Date: Fri, 19 Nov 2010 09:52:46 -0800
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, mathieu.desnoyers@xxxxxxxxxx, andrew.thomas@xxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, keir.fraser@xxxxxxxxxxxxx, chris.mason@xxxxxxxxxx
Delivery-date: Fri, 19 Nov 2010 09:53:42 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0PbuF5IBxaLiFpDNb0UPE7WWscCHKYc3f9DuYX0nXNQ=; b=PbJ5xPpNhOUZzZyL2OGEAVUWxDCRbrnIRw3WsoM6Lma1vXIKaLS6O9Nl5xhFh3d12i fwsZCUAO4JIFOzSVfWKDsMnDmHCgJ86ECbAUaGWywqwPKc1KLiDBzM+QltoZpd4eXh/1 lejNh/CQhmNx2ELtLbcJxE6HACPG/0dCPN4hM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=dOckoQs+z2gnAMV/ON5Xxb6QFo5pcA/lMAR2lsB/uT99oiOx+nuxTUz1jVY3Fvzs6f M9tk822ffCj1Tw8q9je6Za3Avt2T6qM6wIRozzmGKt/4mUwGCVdPopIjUTRfrLGyvUlJ YoQ/nHYTMj/R3XIYUQ3LjX4m+XhzL1x6lua9c=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CE6AF75.1050205@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20101112165541.GA10339@xxxxxxxxxxxx> <EB4C61A1A2501842A04B573FE42B14D601374FBFD2@xxxxxxxxxxxxxxxxx> <20101112223333.GD26189@xxxxxxxxxxxx> <AANLkTi=H6r2=-zJE+6eCtP4VXacYhd_e47+KRW5vdwjS@xxxxxxxxxxxxxx> <20101116185748.GA11549@xxxxxxxxxxxx> <AANLkTikw8reKXwd9CcXc3qqHuXKjbMEatAVfn19uwzs3@xxxxxxxxxxxxxx> <20101116201349.GA18315@xxxxxxxxxxxx> <AANLkTin7SRKuT5qQQ_1NSis1asOG3eJ1SmmC3fppsGnv@xxxxxxxxxxxxxx> <20101118171936.GA29275@xxxxxxxxxxxx> <AANLkTimPJ4y+YOL2Ed78jmCeaKnxLZb93Kuowxutu_O1@xxxxxxxxxxxxxx> <AANLkTik7-J2tFwTAu6o8HHQSe3Cb0j9VGC+eRgJ0WBpD@xxxxxxxxxxxxxx> <4CE6AF75.1050205@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Nov 19, 2010 at 9:10 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> On 11/18/2010 11:35 AM, Dante Cinco wrote:
>> I mentioned earlier in an previous post to this thread that I'm able
>> to apply Dulloor's xenoprofile patch to the dom0 kernel but not the
>> domU kernel. So I can't do active-domain profiling but I'm able to do
>> passive-domain profiling but I don't know how reliable the results are
>> since it shows pvclock_clocksource_read as the top consumer of CPU
>> cycles at 28%.
>
> Is rdtsc emulation on?  (I forget what the incantation is for that now.)

How do I check if rdtsc emulation is on? Does 'xm debug-keys s' do it?

(XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch
input to DOM0)
(XEN) TSC marked as reliable, warp = 0 (count=2)
(XEN) dom1: mode=0,ofs=0xca6f68770,khz=2666017,inc=1
(XEN) No domains have emulated TSC

I'm using xen-unstable-4.1 (22388:87f248de5230).

- Dante

>
>    J
>
>> CPU: Intel Architectural Perfmon, speed 2665.98 MHz (estimated)
>> Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a
>> unit mask of 0x00 (No unit mask) count 100000
>> samples  %        image name               app name                 symbol 
>> name
>> 918089   27.9310
>> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>> domain1-kernel           pvclock_clocksource_read
>> 217811    6.6265  domain1-modules          domain1-modules
>> /domain1-modules
>> 188327    5.7295  vmlinux-2.6.32.25-pvops-stable-dom0-5.7.dcinco-debug
>> vmlinux-2.6.32.25-pvops-stable-dom0-5.7.dcinco-debug
>> mutex_spin_on_owner
>> 186684    5.6795
>> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>> domain1-kernel           __xen_spin_lock
>> 149514    4.5487
>> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>> domain1-kernel           __write_lock_failed
>> 123278    3.7505
>> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>> domain1-kernel           __kernel_text_address
>> 122906    3.7392
>> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>> domain1-kernel           xen_spin_unlock
>> 90903     2.7655
>> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>> domain1-kernel           __spin_time_accum
>> 85880     2.6127
>> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>> domain1-kernel           __module_address
>> 75223     2.2885
>> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>> domain1-kernel           print_context_stack
>> 66778     2.0316
>> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>> domain1-kernel           __module_text_address
>> 57389     1.7459
>> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>> domain1-kernel           is_module_text_address
>> 47282     1.4385  xen-syms-4.1-unstable    domain1-xen
>> syscall_enter
>> 47219     1.4365
>> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>> domain1-kernel           prio_tree_insert
>> 46495     1.4145  vmlinux-2.6.32.25-pvops-stable-dom0-5.7.dcinco-debug
>> vmlinux-2.6.32.25-pvops-stable-dom0-5.7.dcinco-debug
>> pvclock_clocksource_read
>> 44501     1.3539
>> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>> domain1-kernel           prio_tree_left
>> 32482     0.9882
>> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>> domain1-kernel           native_read_tsc
>>
>> I ran oprofile (0.9.5 with xenoprofile patch) for 20 seconds while the
>> I/Os were running. Here's the command I used:
>>
>> opcontrol --start --xen=/boot/xen-syms-4.1-unstable
>> --vmlinux=/boot/vmlinux-2.6.32.25-pvops-stable-dom0-5.7.dcinco-debug
>> --passive-domains=1
>> --passive-images=/boot/vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug
>>
>> I had to remove dom0_max_vcpus=1 (but kept dom0_vcpus_pin=true) in the
>> Xen command line. Otherwise, oprofile only gives the samples from
>> CPU0.
>>
>> I'm going to try perf next.
>>
>> - Dante
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>>
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>