From: Matt Fleming <matt@console-pimps.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Marc Titinger <mtittinge@hotmail.com>,
robert.richter@amd.com, linux-arch@vger.kernel.org,
linux@arm.linux.org.uk, linux-sh@vger.kernel.org,
peterz@infradead.org, fweisbec@gmail.com, will.deacon@arm.com,
acme@redhat.com, lethal@linux-sh.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3 0/6] Generalise ARM perf-events backend for oprofile
Date: Mon, 13 Sep 2010 12:04:44 +0100 [thread overview]
Message-ID: <20100913110444.GB14882@console-pimps.org> (raw)
In-Reply-To: <20100913085137.GE23741@elte.hu>
On Mon, Sep 13, 2010 at 10:51:37AM +0200, Ingo Molnar wrote:
>
> * Matt Fleming <matt@console-pimps.org> wrote:
>
> > On Mon, Sep 13, 2010 at 09:13:32AM +0200, Marc Titinger wrote:
> > >
> > > Hi,
> > >
> > > I'm just being curious : do these patches change the way those chips
> > > should be supported, that do not have a PMU-like IP, but implement
> > > PC-sampling thanks to a general purpose timer (not the system timer)
> > > ?
> >
> > CPUs that do not have a PMU are not required to use the perf-events
> > oprofile backend, it is entirely optional. The pc-sampling timer in
> > oprofile is not affected by this series.
>
> It should still work fine though: a generalized oprofile backend should
> simply use hrtimer based events. That also has a chance to be higher
> quality than the system time fallback, on PMU-less (but high-res-timer
> capable) systems.
Yeah, that's a good point. It would make a nice addition to this patch
series. I may get chance to take a look at it at some point.
WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt@console-pimps.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Marc Titinger <mtittinge@hotmail.com>,
robert.richter@amd.com, linux-arch@vger.kernel.org,
linux@arm.linux.org.uk, linux-sh@vger.kernel.org,
peterz@infradead.org, fweisbec@gmail.com, will.deacon@arm.com,
acme@redhat.com, lethal@linux-sh.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3 0/6] Generalise ARM perf-events backend for oprofile
Date: Mon, 13 Sep 2010 11:04:44 +0000 [thread overview]
Message-ID: <20100913110444.GB14882@console-pimps.org> (raw)
In-Reply-To: <20100913085137.GE23741@elte.hu>
On Mon, Sep 13, 2010 at 10:51:37AM +0200, Ingo Molnar wrote:
>
> * Matt Fleming <matt@console-pimps.org> wrote:
>
> > On Mon, Sep 13, 2010 at 09:13:32AM +0200, Marc Titinger wrote:
> > >
> > > Hi,
> > >
> > > I'm just being curious : do these patches change the way those chips
> > > should be supported, that do not have a PMU-like IP, but implement
> > > PC-sampling thanks to a general purpose timer (not the system timer)
> > > ?
> >
> > CPUs that do not have a PMU are not required to use the perf-events
> > oprofile backend, it is entirely optional. The pc-sampling timer in
> > oprofile is not affected by this series.
>
> It should still work fine though: a generalized oprofile backend should
> simply use hrtimer based events. That also has a chance to be higher
> quality than the system time fallback, on PMU-less (but high-res-timer
> capable) systems.
Yeah, that's a good point. It would make a nice addition to this patch
series. I may get chance to take a look at it at some point.
WARNING: multiple messages have this Message-ID (diff)
From: matt@console-pimps.org (Matt Fleming)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 0/6] Generalise ARM perf-events backend for oprofile
Date: Mon, 13 Sep 2010 12:04:44 +0100 [thread overview]
Message-ID: <20100913110444.GB14882@console-pimps.org> (raw)
In-Reply-To: <20100913085137.GE23741@elte.hu>
On Mon, Sep 13, 2010 at 10:51:37AM +0200, Ingo Molnar wrote:
>
> * Matt Fleming <matt@console-pimps.org> wrote:
>
> > On Mon, Sep 13, 2010 at 09:13:32AM +0200, Marc Titinger wrote:
> > >
> > > Hi,
> > >
> > > I'm just being curious : do these patches change the way those chips
> > > should be supported, that do not have a PMU-like IP, but implement
> > > PC-sampling thanks to a general purpose timer (not the system timer)
> > > ?
> >
> > CPUs that do not have a PMU are not required to use the perf-events
> > oprofile backend, it is entirely optional. The pc-sampling timer in
> > oprofile is not affected by this series.
>
> It should still work fine though: a generalized oprofile backend should
> simply use hrtimer based events. That also has a chance to be higher
> quality than the system time fallback, on PMU-less (but high-res-timer
> capable) systems.
Yeah, that's a good point. It would make a nice addition to this patch
series. I may get chance to take a look at it at some point.
next prev parent reply other threads:[~2010-09-13 11:04 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 6:07 [PATCH V3 0/6] Generalise ARM perf-events backend for oprofile Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-13 6:07 ` [PATCH 1/6] perf: Add helper function to return number of counters Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-16 12:32 ` Robert Richter
2010-09-16 12:32 ` Robert Richter
2010-09-16 12:32 ` [PATCH 1/6] perf: Add helper function to return number of Robert Richter
2010-09-13 6:07 ` [PATCH 2/6] ARM: oprofile: Rename op_arm to oprofile_perf Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-16 12:46 ` Robert Richter
2010-09-16 12:46 ` Robert Richter
2010-09-16 12:46 ` Robert Richter
2010-09-13 6:07 ` [PATCH 3/6] ARM: oprofile: Move non-ARM code into separate init/exit functions Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-16 12:55 ` Robert Richter
2010-09-16 12:55 ` Robert Richter
2010-09-16 12:55 ` [PATCH 3/6] ARM: oprofile: Move non-ARM code into separate Robert Richter
2010-09-13 6:07 ` [PATCH 4/6] oprofile: Abstract the perf-events backend Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-16 13:15 ` Robert Richter
2010-09-16 13:15 ` Robert Richter
2010-09-16 13:15 ` Robert Richter
2010-09-13 6:07 ` [PATCH 5/6] ARM: Make oprofile depend on CONFIG_HW_PERF_EVENTS Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-13 8:39 ` Will Deacon
2010-09-13 8:39 ` Will Deacon
2010-09-13 8:39 ` Will Deacon
2010-09-16 13:34 ` Robert Richter
2010-09-16 13:34 ` Robert Richter
2010-09-16 13:34 ` Robert Richter
2010-09-13 9:22 ` Sergei Shtylyov
2010-09-13 9:22 ` Sergei Shtylyov
2010-09-13 9:22 ` Sergei Shtylyov
2010-09-13 6:07 ` [PATCH 6/6] sh: oprofile: Use perf-events oprofile backend Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-13 6:07 ` Matt Fleming
2010-09-16 14:32 ` Robert Richter
2010-09-16 14:32 ` Robert Richter
2010-09-16 14:32 ` Robert Richter
2010-09-27 20:01 ` Matt Fleming
2010-09-27 20:01 ` Matt Fleming
2010-09-27 20:01 ` Matt Fleming
2010-09-27 22:07 ` Robert Richter
2010-09-27 22:07 ` Robert Richter
2010-09-27 22:07 ` Robert Richter
2010-09-27 22:26 ` Matt Fleming
2010-09-27 22:26 ` Matt Fleming
2010-09-27 22:26 ` Matt Fleming
2010-09-27 22:45 ` Robert Richter
2010-09-27 22:45 ` Robert Richter
2010-09-27 22:45 ` Robert Richter
2010-09-27 22:45 ` Robert Richter
2010-09-28 8:33 ` Matt Fleming
2010-09-28 8:33 ` Matt Fleming
2010-09-28 8:33 ` Matt Fleming
2010-09-30 1:04 ` Paul Mundt
2010-09-30 1:04 ` Paul Mundt
2010-09-30 1:04 ` Paul Mundt
2010-09-30 8:14 ` Will Deacon
2010-09-30 8:14 ` Will Deacon
2010-09-30 8:14 ` Will Deacon
2010-09-13 7:13 ` [PATCH V3 0/6] Generalise ARM perf-events backend for oprofile Marc Titinger
2010-09-13 7:13 ` Marc Titinger
2010-09-13 7:50 ` Matt Fleming
2010-09-13 7:50 ` Matt Fleming
2010-09-13 7:50 ` Matt Fleming
2010-09-13 8:51 ` Ingo Molnar
2010-09-13 8:51 ` Ingo Molnar
2010-09-13 8:51 ` Ingo Molnar
2010-09-13 11:04 ` Matt Fleming [this message]
2010-09-13 11:04 ` Matt Fleming
2010-09-13 11:04 ` Matt Fleming
2010-09-13 10:08 ` Will Deacon
2010-09-13 10:08 ` Will Deacon
2010-09-13 10:08 ` Will Deacon
2010-09-13 11:18 ` Matt Fleming
2010-09-13 11:18 ` Matt Fleming
2010-09-13 11:18 ` Matt Fleming
2010-09-16 14:48 ` Robert Richter
2010-09-16 14:48 ` Robert Richter
2010-09-16 14:48 ` Robert Richter
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=20100913110444.GB14882@console-pimps.org \
--to=matt@console-pimps.org \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@elte.hu \
--cc=mtittinge@hotmail.com \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.com \
--cc=will.deacon@arm.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.