From: Stephane Eranian <eranian@google.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: eranian@gmail.com, linux-kernel@vger.kernel.org, mingo@elte.hu,
paulus@samba.org, davem@davemloft.net, fweisbec@gmail.com,
perfmon2-devel@lists.sf.net
Subject: Re: [PATCH] perf_events: improve x86 event scheduling (v6 incremental)
Date: Tue, 26 Jan 2010 10:17:45 +0100 [thread overview]
Message-ID: <bd4cb8901001260117wf128e13kf188a4b0267fc153@mail.gmail.com> (raw)
In-Reply-To: <1264442381.4283.1944.camel@laptop>
On Mon, Jan 25, 2010 at 6:59 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, 2010-01-25 at 18:48 +0100, stephane eranian wrote:
>> So we have to modify hw_perf_enable() to first disable all events
>> which are moving,
>> then reprogram them. I suspect it may be possible to optimize this if
>> we detect that
>> those events had already been stopped individually (as opposed to
>> perf_disable()), i.e.,
>> already had their counts saved.
>
> Right, I see no fundamentally impossible things at all, we just need to
> be careful here.
>
> Anyway, I poked at the stack I've got now and it seems to hold up when I
> poke at it with various combinations of constraint events, so I'll push
> that off to Ingo and then we can go from there.
>
> Thanks for working on this!
Ok, so I think the best way to proceed here is to first wait until all of this
is checked in. Then I'll see what is missing based on what we discussed
here.
next prev parent reply other threads:[~2010-01-26 9:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 15:39 Stephane Eranian
2010-01-22 20:27 ` Peter Zijlstra
2010-01-25 15:01 ` Peter Zijlstra
2010-01-25 17:12 ` stephane eranian
2010-01-25 17:25 ` Peter Zijlstra
2010-01-25 17:48 ` stephane eranian
2010-01-25 17:59 ` Peter Zijlstra
2010-01-26 9:17 ` Stephane Eranian [this message]
2010-01-29 23:08 ` Stephane Eranian
2010-01-30 8:56 ` Peter Zijlstra
2010-01-30 18:21 ` Stephane Eranian
2010-01-29 9:26 ` [tip:perf/core] perf_events: Add fast-path to the rescheduling code tip-bot for 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=bd4cb8901001260117wf128e13kf188a4b0267fc153@mail.gmail.com \
--to=eranian@google.com \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=fweisbec@gmail.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 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®