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] RE: Patch for xenoprofile

To: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] RE: Patch for xenoprofile
From: "Duan, Ronghui" <ronghui.duan@xxxxxxxxx>
Date: Tue, 28 Oct 2008 15:45:54 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 28 Oct 2008 00:46:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20081028062134.GJ5853%yamahata@xxxxxxxxxxxxx>
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: <F36B5FC62413A04B9A2B9189DCD808AA29C46F6E58@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <F36B5FC62413A04B9A2B9189DCD808AA29C46F6E59@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20081028062134.GJ5853%yamahata@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ack4xXJiljrnkm3NQaG8wu0o+8HlhwAC5Ctg
Thread-topic: [Xen-devel] RE: Patch for xenoprofile
Sorry for my carelessness, change it now.

Thanks
Ronghui

-----Original Message-----
From: Isaku Yamahata [mailto:yamahata@xxxxxxxxxxxxx]
Sent: Tuesday, October 28, 2008 2:22 PM
To: Duan, Ronghui
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Duan, Ronghui
> Sent: Monday, October 27, 2008 9:02 PM
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


--
yamahata

Attachment: xenoprofile_enhance.patch
Description: xenoprofile_enhance.patch

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>