From: Steven Rostedt <rostedt@goodmis.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH -tip] x86,perf: P4 PMU -- protect sensible procedures from preemption
Date: Thu, 06 May 2010 14:32:33 -0400 [thread overview]
Message-ID: <1273170753.22438.45.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20100506152646.GC5583@lenovo>
On Thu, 2010-05-06 at 19:26 +0400, Cyrill Gorcunov wrote:
> On Thu, May 06, 2010 at 06:48:54PM +0400, Cyrill Gorcunov wrote:
> > On Thu, May 06, 2010 at 09:45:24AM -0400, Steven Rostedt wrote:
> > ...
> > > > > We want the one with the least runtime overhead. These are instrumentation
> > > > > routines, so we want to optimize them as much as possible.
> > >
> > >
> > > Yeah, my point was either disable preemption or keep the checks. In
> > > other words, if you don't disable preemption, do not use
> > > raw_smp_procesor_id(), because then we will not catch it if it changes
> > > in the future.
> > >
> > > > ok, Ingo, dont apply this patch then for a while.
> > >
> > > Send another patch, I'll test it again ;-)
> > >
> > > -- Steve
> > >
> > >
> >
> > Ingo, Steven, it seems we have potential preemtion available
> > in perf_event.c:validate_group:x86_pmu.schedule_events() which
> > is reached via syscall from userspace perf_event_open() call,
> > so get_cpu is still needed. But I'm a bit messed with call
> > graph at the moment :(
> >
> > -- Cyrill
>
> Steve, while I'm diving through call graph could you give this
> patch a shot? If preemtion happens -- it'll trigger it fast.
This one works too.
Tested-by: Steven Rostedt <rostedt@goodmis.org>
-- Steve
>
> -- Cyrill
> ---
> arch/x86/kernel/cpu/perf_event_p4.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> Index: linux-2.6.git/arch/x86/kernel/cpu/perf_event_p4.c
> =====================================================================
> --- linux-2.6.git.orig/arch/x86/kernel/cpu/perf_event_p4.c
> +++ linux-2.6.git/arch/x86/kernel/cpu/perf_event_p4.c
> @@ -421,7 +421,7 @@ static u64 p4_pmu_event_map(int hw_event
>
> static int p4_hw_config(struct perf_event *event)
> {
> - int cpu = raw_smp_processor_id();
> + int cpu = get_cpu();
> u32 escr, cccr;
>
> /*
> @@ -440,7 +440,7 @@ static int p4_hw_config(struct perf_even
> event->hw.config = p4_set_ht_bit(event->hw.config);
>
> if (event->attr.type != PERF_TYPE_RAW)
> - return 0;
> + goto out;
>
> /*
> * We don't control raw events so it's up to the caller
> @@ -455,6 +455,8 @@ static int p4_hw_config(struct perf_even
> (p4_config_pack_escr(P4_ESCR_MASK_HT) |
> p4_config_pack_cccr(P4_CCCR_MASK_HT));
>
> +out:
> + put_cpu();
> return 0;
> }
>
> @@ -741,7 +743,7 @@ static int p4_pmu_schedule_events(struct
> {
> unsigned long used_mask[BITS_TO_LONGS(X86_PMC_IDX_MAX)];
> unsigned long escr_mask[BITS_TO_LONGS(ARCH_P4_TOTAL_ESCR)];
> - int cpu = raw_smp_processor_id();
> + int cpu = smp_processor_id();
> struct hw_perf_event *hwc;
> struct p4_event_bind *bind;
> unsigned int i, thread, num;
next prev parent reply other threads:[~2010-05-06 18:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 15:07 Cyrill Gorcunov
2010-05-05 16:57 ` Frederic Weisbecker
2010-05-05 17:42 ` Cyrill Gorcunov
2010-05-05 17:58 ` Frederic Weisbecker
2010-05-06 6:44 ` Ingo Molnar
2010-05-06 7:39 ` Cyrill Gorcunov
2010-05-06 7:42 ` Ingo Molnar
2010-05-06 7:45 ` Cyrill Gorcunov
2010-05-06 13:45 ` Steven Rostedt
2010-05-06 14:48 ` Cyrill Gorcunov
2010-05-06 15:26 ` Cyrill Gorcunov
2010-05-06 18:32 ` Steven Rostedt [this message]
2010-05-06 18:36 ` Cyrill Gorcunov
2010-05-07 15:05 Cyrill Gorcunov
2010-05-08 8:06 ` Ingo Molnar
2010-05-08 8:09 ` Cyrill Gorcunov
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=1273170753.22438.45.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®