All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryan O'Sullivan" <bos@serpentine.com>
To: eranian@hpl.hp.com
Cc: perfctr-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	perfmon@napali.hpl.hp.com, "Eranian,
	Stephane" <stephane.eranian@hp.com>,
	Andrew Morton <akpm@osdl.org>, "Truong, Dan" <dan.truong@hp.com>
Subject: Re: [Perfctr-devel] RE: [perfmon] Re: quick overview of the
Date: Wed, 25 Jan 2006 22:46:43 +0000	[thread overview]
Message-ID: <1138229203.15295.65.camel@serpentine.pathscale.com> (raw)
In-Reply-To: <20060125222844.GB10451@frankl.hpl.hp.com>

On Wed, 2006-01-25 at 14:28 -0800, Stephane Eranian wrote:

> So it would help if you could
> name the extended features you referring to. 

I'm dubious about the hands-off buffer format in general.  Does this
mean that userspace needs to modprobe a specific set of modules in order
to do normal sampling?  If so, how do you work around the need for users
to be root in order to use these interfaces?

> And perfmon
> does allow it to continue working using almost all of its kernel code.
> This is leveraging the custom sampling buffer format support in perfmon.
> So you can say this is an extended feature that adds complexity.
> But OTOH, this is one elegant way of supporting an existing interface
> without breaking all the tools.

So are you saying that part of the existing oprofile code can be deleted
if perfmon is merged, and that userspace won't notice?

> We were able to proide this support
> with a few hundred lines of code without hacking the regular sampling
> format. Instead we simply created a dedicated PEBS format as a kernel module.

Does this mean I can't sample the PMCs on a P4 if I don't have the
special PEBS module loaded?  Do I need to be root to do that?

	<b


WARNING: multiple messages have this Message-ID (diff)
From: "Bryan O'Sullivan" <bos@serpentine.com>
To: eranian@hpl.hp.com
Cc: perfctr-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	perfmon@napali.hpl.hp.com, "Eranian,
	Stephane" <stephane.eranian@hp.com>,
	Andrew Morton <akpm@osdl.org>, "Truong, Dan" <dan.truong@hp.com>
Subject: Re: [Perfctr-devel] RE: [perfmon] Re: quick overview of the perfmon2 interface
Date: Wed, 25 Jan 2006 14:46:43 -0800	[thread overview]
Message-ID: <1138229203.15295.65.camel@serpentine.pathscale.com> (raw)
In-Reply-To: <20060125222844.GB10451@frankl.hpl.hp.com>

On Wed, 2006-01-25 at 14:28 -0800, Stephane Eranian wrote:

> So it would help if you could
> name the extended features you referring to. 

I'm dubious about the hands-off buffer format in general.  Does this
mean that userspace needs to modprobe a specific set of modules in order
to do normal sampling?  If so, how do you work around the need for users
to be root in order to use these interfaces?

> And perfmon
> does allow it to continue working using almost all of its kernel code.
> This is leveraging the custom sampling buffer format support in perfmon.
> So you can say this is an extended feature that adds complexity.
> But OTOH, this is one elegant way of supporting an existing interface
> without breaking all the tools.

So are you saying that part of the existing oprofile code can be deleted
if perfmon is merged, and that userspace won't notice?

> We were able to proide this support
> with a few hundred lines of code without hacking the regular sampling
> format. Instead we simply created a dedicated PEBS format as a kernel module.

Does this mean I can't sample the PMCs on a P4 if I don't have the
special PEBS module loaded?  Do I need to be root to do that?

	<b


  reply	other threads:[~2006-01-25 22:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20 18:37 [perfmon] Re: quick overview of the perfmon2 interface Truong, Dan
2006-01-20 18:37 ` Truong, Dan
2006-01-20 22:22 ` Andrew Morton
2006-01-20 22:22   ` Andrew Morton
2006-01-25 20:33 ` Bryan O'Sullivan
2006-01-25 20:33   ` Bryan O'Sullivan
2006-01-25 22:28   ` [Perfctr-devel] " Stephane Eranian
2006-01-25 22:28     ` Stephane Eranian
2006-01-25 22:46     ` Bryan O'Sullivan [this message]
2006-01-25 22:46       ` Bryan O'Sullivan
2006-01-26  7:48       ` Stephane Eranian
2006-01-26  7:48         ` Stephane Eranian
2006-01-26 18:26         ` [Perfctr-devel] RE: [perfmon] Re: quick overview of the Bryan O'Sullivan
2006-01-26 18:26           ` [Perfctr-devel] RE: [perfmon] Re: quick overview of the perfmon2 interface Bryan O'Sullivan
     [not found]     ` <1138649612.4077.50.camel@localhost.localdomain>
     [not found]       ` <1138651545.4487.13.camel@camp4.serpentine.com>
     [not found]         ` <1139155731.4279.0.camel@localhost.localdomain>
     [not found]           ` <1139245253.27739.8.camel@camp4.serpentine.com>
2006-02-10 15:36             ` perfmon2 code review: 32-bit ABI on 64-bit OS Stephane Eranian
2006-02-10 15:36               ` Stephane Eranian
2006-02-10 18:27               ` Bryan O'Sullivan
2006-02-10 18:27                 ` Bryan O'Sullivan
     [not found]                 ` <1139681785.4316.33.camel@localhost.localdomain>
2006-02-11 22:33                   ` [perfmon] " Stephane Eranian
2006-02-12 23:46                     ` [Perfctr-devel] " David Gibson
2006-02-13  0:03                       ` Eric Gouriou
2006-02-13 20:31                         ` Stephane Eranian
     [not found]                     ` <1139857076.4342.10.camel@localhost.localdomain>
2006-02-14 23:41                       ` [Perfctr-devel] " Stephane Eranian
2006-02-20 17:54                       ` Stephane Eranian
2006-02-13 20:34                 ` Stephane Eranian
2006-02-13 20:34                   ` Stephane Eranian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1138229203.15295.65.camel@serpentine.pathscale.com \
    --to=bos@serpentine.com \
    --cc=akpm@osdl.org \
    --cc=dan.truong@hp.com \
    --cc=eranian@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perfctr-devel@lists.sourceforge.net \
    --cc=perfmon@napali.hpl.hp.com \
    --cc=stephane.eranian@hp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.