From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
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: [BUG] perf_events: ctx_flexible_sched_in()
Date: Mon, 01 Feb 2010 13:27:03 +0100 [thread overview]
Message-ID: <1265027223.24455.145.camel@laptop> (raw)
In-Reply-To: <bd4cb8901002010420o2ea7dbafnba84f78b6a2f38f5@mail.gmail.com>
On Mon, 2010-02-01 at 13:20 +0100, Stephane Eranian wrote:
> The function does not allow maximizing PMU usage because of
> the way can_add_hw is managed. Basically, as soon as a group
> fail to be scheduled in, then no other group can. I believe this
> is not optimum. You need to skip the group that fails and keep
> scanning the list. There may be other groups which can be
> scheduled.
Yeah, I saw that too, we need a new hw_ callback for that, or more
structured error values out of ->enable that distinguish between this
event won't fit and pmu full.
prev parent reply other threads:[~2010-02-01 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 12:20 [BUG] perf_events: ctx_flexible_sched_in() Stephane Eranian
2010-02-01 12:27 ` Peter Zijlstra [this message]
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=1265027223.24455.145.camel@laptop \
--to=peterz@infradead.org \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=eranian@google.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 \
/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