Don't mount hardware performance counter using xenoprof

Don't mount hardware performance counter using xenoprof

[Yuto Nakai]

[-- Attachment #1.1: Type: text/plain, Size: 732 bytes --]

Hi,

I want to use xenoprof to profile the overhead of the hypervisor.
I patched the oprofile-0.9.5 using the patch from xenoprof.sourceforge.net

Debian GNU/Linux 5.0 (lenny)
Xen-4.0.1 + 2.6.32.27 (linux-2.6-pvops.git) Dom0
My platform is Intel(R) Core(TM) i7 CPU           960  @ 3.20GHz

My problems are:
In Dom0,  But hardware performance counters don't be mounted
after initialization (opcontrol --init)

# ls /dev/oprofile
backtrace_depth    cpu_buffer_size   pointer_size
buffer                    cpu_type            stats
buffer_size             dump                time_slice
buffer_watershed    enable

0(and 1,2,3) directories are not exist.

Is there any reason for this ?

 Any help is appreciated. Thanks, Yuto Nakai

[-- Attachment #1.2: Type: text/html, Size: 3377 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Don't mount hardware performance counter using xenoprof

[Yuto Nakai]

[-- Attachment #1.1: Type: text/plain, Size: 732 bytes --]

Hi,

I want to use xenoprof to profile the overhead of the hypervisor.
I patched the oprofile-0.9.5 using the patch from xenoprof.sourceforge.net

Debian GNU/Linux 5.0 (lenny)
Xen-4.0.1 + 2.6.32.27 (linux-2.6-pvops.git) Dom0
My platform is Intel(R) Core(TM) i7 CPU           960  @ 3.20GHz

My problems are:
In Dom0,  But hardware performance counters don't be mounted
after initialization (opcontrol --init)

# ls /dev/oprofile
backtrace_depth    cpu_buffer_size   pointer_size
buffer                    cpu_type            stats
buffer_size             dump                time_slice
buffer_watershed    enable

0(and 1,2,3) directories are not exist.

Is there any reason for this ?

 Any help is appreciated. Thanks, Yuto Nakai

[-- Attachment #1.2: Type: text/html, Size: 3168 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Don't mount hardware performance counter using xenoprof

[Konrad Rzeszutek Wilk]

On Sat, Jan 08, 2011 at 04:06:58PM +0900, Yuto Nakai wrote:
> Hi,
> 
> I want to use xenoprof to profile the overhead of the hypervisor.
> I patched the oprofile-0.9.5 using the patch from xenoprof.sourceforge.net
> 
> Debian GNU/Linux 5.0 (lenny)
> Xen-4.0.1 + 2.6.32.27 (linux-2.6-pvops.git) Dom0
> My platform is Intel(R) Core(TM) i7 CPU           960  @ 3.20GHz
> 
> My problems are:
> In Dom0,  But hardware performance counters don't be mounted
> after initialization (opcontrol --init)
> 
> # ls /dev/oprofile
> backtrace_depth    cpu_buffer_size   pointer_size
> buffer                    cpu_type            stats
> buffer_size             dump                time_slice
> buffer_watershed    enable
> 
> 0(and 1,2,3) directories are not exist.
> 
> Is there any reason for this ?

Do they exist when booting a baremetal kernel?

> 
>  Any help is appreciated. Thanks, Yuto Nakai

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

Re: Don't mount hardware performance counter using xenoprof

[Yuto Nakai]

[-- Attachment #1.1: Type: text/plain, Size: 1280 bytes --]

2011/1/10 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

> On Sat, Jan 08, 2011 at 04:06:58PM +0900, Yuto Nakai wrote:
> > Hi,
> >
> > I want to use xenoprof to profile the overhead of the hypervisor.
> > I patched the oprofile-0.9.5 using the patch from
> xenoprof.sourceforge.net
> >
> > Debian GNU/Linux 5.0 (lenny)
> > Xen-4.0.1 + 2.6.32.27 (linux-2.6-pvops.git) Dom0
> > My platform is Intel(R) Core(TM) i7 CPU           960  @ 3.20GHz
> >
> > My problems are:
> > In Dom0,  But hardware performance counters don't be mounted
> > after initialization (opcontrol --init)
> >
> > # ls /dev/oprofile
> > backtrace_depth    cpu_buffer_size   pointer_size
> > buffer                    cpu_type            stats
> > buffer_size             dump                time_slice
> > buffer_watershed    enable
> >
> > 0(and 1,2,3) directories are not exist.
> >
> > Is there any reason for this ?
>
> Do they exist when booting a baremetal kernel?
>
>
Thank you for your response.


Does booting a baremetal kernel means booting Dom0?
If it means so,  they don't exist.




> >
> >  Any help is appreciated. Thanks, Yuto Nakai
>
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
>

[-- Attachment #1.2: Type: text/html, Size: 2288 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Don't mount hardware performance counter using xenoprof

[Konrad Rzeszutek Wilk]

> > Do they exist when booting a baremetal kernel?
> >
> >
> Thank you for your response.
> 
> 
> Does booting a baremetal kernel means booting Dom0?

No. Baremetal means booting the same kernel but without the Xen hypervisor.

Re: Don't mount hardware performance counter using xenoprof

[Yuto Nakai]

[-- Attachment #1.1: Type: text/plain, Size: 362 bytes --]

2011/1/11 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

> > > Do they exist when booting a baremetal kernel?
> > >
> > >
> > Thank you for your response.
> >
> >
> > Does booting a baremetal kernel means booting Dom0?
>
> No. Baremetal means booting the same kernel but without the Xen hypervisor.
>

I understood.

They exist when booting a baremetal kernel.

[-- Attachment #1.2: Type: text/html, Size: 720 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Don't mount hardware performance counter using xenoprof

[Konrad Rzeszutek Wilk]

On Tue, Jan 11, 2011 at 12:34:58AM +0900, Yuto Nakai wrote:
> 2011/1/11 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> 
> > > > Do they exist when booting a baremetal kernel?
> > > >
> > > >
> > > Thank you for your response.
> > >
> > >
> > > Does booting a baremetal kernel means booting Dom0?
> >
> > No. Baremetal means booting the same kernel but without the Xen hypervisor.
> >
> 
> I understood.
> 
> They exist when booting a baremetal kernel.

Ok, then the answer is that nobody has looked in a long time (I think
since 2.6.18) to hook up the oprofile (or rather the code that
that gets invoked when a perf counter is triggered) to the Xen hypervisor.

It might make sense to look at how 2.6.18 did it (especially what were
the hypercalls and where) and see how to port it over to a pvops kernel.

Don't mount hardware performance counter using xenoprof

[Yuto Nakai]

[-- Attachment #1.1: Type: text/plain, Size: 732 bytes --]

Hi,

I want to use xenoprof to profile the overhead of the hypervisor.
I patched the oprofile-0.9.5 using the patch from xenoprof.sourceforge.net

Debian GNU/Linux 5.0 (lenny)
Xen-4.0.1 + 2.6.32.27 (linux-2.6-pvops.git) Dom0
My platform is Intel(R) Core(TM) i7 CPU           960  @ 3.20GHz

My problems are:
In Dom0,  But hardware performance counters don't be mounted
after initialization (opcontrol --init)

# ls /dev/oprofile
backtrace_depth    cpu_buffer_size   pointer_size
buffer                    cpu_type            stats
buffer_size             dump                time_slice
buffer_watershed    enable

0(and 1,2,3) directories are not exist.

Is there any reason for this ?

 Any help is appreciated. Thanks, Yuto Nakai

[-- Attachment #1.2: Type: text/html, Size: 4102 bytes --]

[-- Attachment #2: Type: text/plain, Size: 137 bytes --]

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