All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Stephane Eranian <eranian@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org, mingo@elte.hu, paulus@samba.org,
	davem@davemloft.net, perfmon2-devel@lists.sf.net
Subject: Re: [PATCH] perf_events: improve x86 event scheduling
Date: Sun, 17 Jan 2010 15:12:35 +0100	[thread overview]
Message-ID: <20100117141233.GF5035@nowhere> (raw)
In-Reply-To: <bd4cb8901001130922s7ad85af6w6c631d90de177ef9@mail.gmail.com>

On Wed, Jan 13, 2010 at 06:22:54PM +0100, Stephane Eranian wrote:
> Ok,
> 
> Something like that should problably do it:
> 
> static void event_sched_out(struct perf_event *event, int cpu)
> {
>         event->state = PERF_EVENT_STATE_INACTIVE;
>         event->oncpu = -1;
> }



You need to also call pmu->disable() if it is a software event,
because a breakpoint needs to be unregistered in hardware level
too.

And disable it in x86 level if it is an x86 event?


 
> hw_perf_group_sched_in()
> {
>        ....
>        n = 1;
>         list_for_each_entry(sub, &leader->sibling_list, group_entry) {
>                 if (sub->state > PERF_EVENT_STATE_OFF) {
>                         ret = event_sched_in(sub, cpu);
>                         if (ret)
>                                 goto undo;



Yeah we indeed really need to check that.

Thanks.


  reply	other threads:[~2010-01-17 14:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 10:50 [PATCH] perf_events: improve x86 event scheduling Stephane Eranian
2010-01-12 16:10 ` Peter Zijlstra
2010-01-13  9:54   ` Stephane Eranian
2010-01-13 16:29     ` Peter Zijlstra
2010-01-13 16:52       ` Stephane Eranian
2010-01-13 17:22         ` Stephane Eranian
2010-01-17 14:12           ` Frederic Weisbecker [this message]
2010-01-17 14:42             ` Stephane Eranian
2010-01-17 16:19               ` Frederic Weisbecker
2010-01-17 21:53                 ` Stephane Eranian
2010-01-18 11:13             ` Peter Zijlstra
2010-01-18 11:53               ` [PATCH] perf: fix the is_software_event() definition Peter Zijlstra
2010-01-18 12:07                 ` Frederic Weisbecker
2010-01-18 12:19                   ` Peter Zijlstra
2010-01-18 13:46                     ` [perfmon2] " stephane eranian
2010-01-18 12:57                   ` stephane eranian
2010-01-18 13:06                     ` Frederic Weisbecker
2010-01-18 12:53                 ` stephane eranian
2010-01-18 13:00                   ` Peter Zijlstra

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=20100117141233.GF5035@nowhere \
    --to=fweisbec@gmail.com \
    --cc=davem@davemloft.net \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=perfmon2-devel@lists.sf.net \
    --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 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.