Add fully support of HVM guest to xenoprofile on Intel p6 family CPU. Make it can fully breakdown HVM guest''s both kernel and user space function. Usage: 1: use opcontrol -e to set event your want to collect both in guest and dom0. 2: In dom0: opcontrol --passive-images= /guest/domain/kernel/image -passive-doamins=/guest/domain/ID -start; 3: In guest: opcontrol -s ; run your workload; opcontrol -h 4: In dom0: opcontrol -h 5:use opreport in dom0 to see Xen''s hot function for guest. And use opreport in guest to see guest''s kernel and user hot functions. Thanks Ronghui _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Fix a type error From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Duan, Ronghui Sent: Monday, October 27, 2008 9:02 PM To: xen-devel@lists.xensource.com Subject: [Xen-devel] Patch for xenoprofile Add fully support of HVM guest to xenoprofile on Intel p6 family CPU. Make it can fully breakdown HVM guest''s both kernel and user space function. Usage: 1: use opcontrol -e to set event your want to collect both in guest and dom0. 2: In dom0: opcontrol --passive-images= /guest/domain/kernel/image -passive-doamins=/guest/domain/ID -start; 3: In guest: opcontrol -s ; run your workload; opcontrol -h 4: In dom0: opcontrol -h 5:use opreport in dom0 to see Xen''s hot function for guest. And use opreport in guest to see guest''s kernel and user hot functions. Thanks Ronghui _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> diff -r 18eff064c628 xen/include/xen/xenoprof.h > --- a/xen/include/xen/xenoprof.h Fri Aug 22 10:45:19 2008 +0100 > +++ b/xen/include/xen/xenoprof.h Mon Oct 27 13:51:18 2008 +0800 > @@ -75,4 +75,7 @@ int acquire_pmu_ownship(int pmu_ownershi > int acquire_pmu_ownship(int pmu_ownership); > void release_pmu_ownship(int pmu_ownership); > > +int passive_domain_do_rdmsr(struct cpu_user_regs *regs); > +int passive_domain_do_wrmsr(struct cpu_user_regs *regs); > +void passive_domain_destroy(struct vcpu *v); > #endif /* __XEN__XENOPROF_H__ */Please do not put those x86 specific stuff into the common header file. xen/include/asm-x86/xenoprof.h is appropriate to put them. thanks, On Mon, Oct 27, 2008 at 09:06:37PM +0800, Duan, Ronghui wrote:> Fix a type error > > > > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Duan, Ronghui > Sent: Monday, October 27, 2008 9:02 PM > To: xen-devel@lists.xensource.com > Subject: [Xen-devel] Patch for xenoprofile > > > > Add fully support of HVM guest to xenoprofile on Intel p6 family CPU. Make it > can fully breakdown HVM guest-As both kernel and user space function.$)B > > > > Usage: > > 1: use opcontrol -Ae to set event your want to collect both in guest and dom0.$)B > > 2: In dom0: opcontrol --passive-images= /guest/domain/kernel/image > -Apassive-doamins=/guest/domain/ID start;$)B > > 3: In guest: opcontrol -s ; run your workload; opcontrol -Ah$)B > > 4: In dom0: opcontrol -Ah$)B > > 5:use opreport in dom0 to see Xen-As hot function for guest. And use opreport in$)B > guest to see guest-As kernel and user hot functions.$)B > > > > Thanks > > Ronghui > > >> _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel-- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Sorry for my carelessness, change it now. Thanks Ronghui -----Original Message----- From: Isaku Yamahata [mailto:yamahata@valinux.co.jp] Sent: Tuesday, October 28, 2008 2:22 PM To: Duan, Ronghui Cc: xen-devel@lists.xensource.com Subject: Re: [Xen-devel] RE: Patch for xenoprofile> diff -r 18eff064c628 xen/include/xen/xenoprof.h > --- a/xen/include/xen/xenoprof.h Fri Aug 22 10:45:19 2008 +0100 > +++ b/xen/include/xen/xenoprof.h Mon Oct 27 13:51:18 2008 +0800 > @@ -75,4 +75,7 @@ int acquire_pmu_ownship(int pmu_ownershi > int acquire_pmu_ownship(int pmu_ownership); > void release_pmu_ownship(int pmu_ownership); > > +int passive_domain_do_rdmsr(struct cpu_user_regs *regs); > +int passive_domain_do_wrmsr(struct cpu_user_regs *regs); > +void passive_domain_destroy(struct vcpu *v); > #endif /* __XEN__XENOPROF_H__ */Please do not put those x86 specific stuff into the common header file. xen/include/asm-x86/xenoprof.h is appropriate to put them. thanks, On Mon, Oct 27, 2008 at 09:06:37PM +0800, Duan, Ronghui wrote:> Fix a type error > > > > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Duan, Ronghui > Sent: Monday, October 27, 2008 9:02 PM > To: xen-devel@lists.xensource.com > Subject: [Xen-devel] Patch for xenoprofile > > > > Add fully support of HVM guest to xenoprofile on Intel p6 family CPU. Make it > can fully breakdown HVM guest-A’s both kernel and user space function.$)B > > > > Usage: > > 1: use opcontrol -A–e to set event your want to collect both in guest and dom0.$)B > > 2: In dom0: opcontrol --passive-images= /guest/domain/kernel/image > -A–passive-doamins=/guest/domain/ID –start;$)B > > 3: In guest: opcontrol -s ; run your workload; opcontrol -A–h$)B > > 4: In dom0: opcontrol -A–h$)B > > 5:use opreport in dom0 to see Xen-A’s hot function for guest. And use opreport in$)B > guest to see guest-A’s kernel and user hot functions.$)B > > > > Thanks > > Ronghui > > >> _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel-- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel