From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dante Cinco Subject: Re: swiotlb=force in Konrad's xen-pcifront-0.8.2 pvops domU kernel with PCI passthrough Date: Fri, 19 Nov 2010 09:52:46 -0800 Message-ID: References: <20101112165541.GA10339@dumpdata.com> <20101112223333.GD26189@dumpdata.com> <20101116185748.GA11549@dumpdata.com> <20101116201349.GA18315@dumpdata.com> <20101118171936.GA29275@dumpdata.com> <4CE6AF75.1050205@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4CE6AF75.1050205@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: Xen-devel , mathieu.desnoyers@polymtl.ca, andrew.thomas@oracle.com, Konrad Rzeszutek Wilk , keir.fraser@eu.citrix.com, chris.mason@oracle.com List-Id: xen-devel@lists.xenproject.org On Fri, Nov 19, 2010 at 9:10 AM, Jeremy Fitzhardinge wrot= e: > 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? =A0(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 =3D 0 (count=3D2) (XEN) dom1: mode=3D0,ofs=3D0xca6f68770,khz=3D2666017,inc=3D1 (XEN) No domains have emulated TSC I'm using xen-unstable-4.1 (22388:87f248de5230). - Dante > > =A0 =A0J > >> 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 =A0% =A0 =A0 =A0 =A0image name =A0 =A0 =A0 =A0 =A0 =A0 =A0 app n= ame =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 symbol name >> 918089 =A0 27.9310 >> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug >> domain1-kernel =A0 =A0 =A0 =A0 =A0 pvclock_clocksource_read >> 217811 =A0 =A06.6265 =A0domain1-modules =A0 =A0 =A0 =A0 =A0domain1-modul= es >> /domain1-modules >> 188327 =A0 =A05.7295 =A0vmlinux-2.6.32.25-pvops-stable-dom0-5.7.dcinco-d= ebug >> vmlinux-2.6.32.25-pvops-stable-dom0-5.7.dcinco-debug >> mutex_spin_on_owner >> 186684 =A0 =A05.6795 >> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug >> domain1-kernel =A0 =A0 =A0 =A0 =A0 __xen_spin_lock >> 149514 =A0 =A04.5487 >> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug >> domain1-kernel =A0 =A0 =A0 =A0 =A0 __write_lock_failed >> 123278 =A0 =A03.7505 >> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug >> domain1-kernel =A0 =A0 =A0 =A0 =A0 __kernel_text_address >> 122906 =A0 =A03.7392 >> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug >> domain1-kernel =A0 =A0 =A0 =A0 =A0 xen_spin_unlock >> 90903 =A0 =A0 2.7655 >> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug >> domain1-kernel =A0 =A0 =A0 =A0 =A0 __spin_time_accum >> 85880 =A0 =A0 2.6127 >> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug >> domain1-kernel =A0 =A0 =A0 =A0 =A0 __module_address >> 75223 =A0 =A0 2.2885 >> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug >> domain1-kernel =A0 =A0 =A0 =A0 =A0 print_context_stack >> 66778 =A0 =A0 2.0316 >> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug >> domain1-kernel =A0 =A0 =A0 =A0 =A0 __module_text_address >> 57389 =A0 =A0 1.7459 >> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug >> domain1-kernel =A0 =A0 =A0 =A0 =A0 is_module_text_address >> 47282 =A0 =A0 1.4385 =A0xen-syms-4.1-unstable =A0 =A0domain1-xen >> syscall_enter >> 47219 =A0 =A0 1.4365 >> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug >> domain1-kernel =A0 =A0 =A0 =A0 =A0 prio_tree_insert >> 46495 =A0 =A0 1.4145 =A0vmlinux-2.6.32.25-pvops-stable-dom0-5.7.dcinco-d= ebug >> vmlinux-2.6.32.25-pvops-stable-dom0-5.7.dcinco-debug >> pvclock_clocksource_read >> 44501 =A0 =A0 1.3539 >> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug >> domain1-kernel =A0 =A0 =A0 =A0 =A0 prio_tree_left >> 32482 =A0 =A0 0.9882 >> vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.dcinco-debug >> domain1-kernel =A0 =A0 =A0 =A0 =A0 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=3D/boot/xen-syms-4.1-unstable >> --vmlinux=3D/boot/vmlinux-2.6.32.25-pvops-stable-dom0-5.7.dcinco-debug >> --passive-domains=3D1 >> --passive-images=3D/boot/vmlinux-2.6.36-rc7-pvops-kpcif-08-2-domu-5.11.d= cinco-debug >> >> I had to remove dom0_max_vcpus=3D1 (but kept dom0_vcpus_pin=3Dtrue) in t= he >> 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@lists.xensource.com >> http://lists.xensource.com/xen-devel >> > >