From: Peter Zijlstra <peterz@infradead.org>
To: Robert Richter <robert.richter@amd.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] perf, x86: Update event scheduling constraints for AMD family 15h models
Date: Fri, 18 May 2012 13:29:12 +0200 [thread overview]
Message-ID: <1337340552.573.33.camel@twins> (raw)
In-Reply-To: <1337337642-1621-1-git-send-email-robert.richter@amd.com>
On Fri, 2012-05-18 at 12:40 +0200, Robert Richter wrote:
> + case 0x031:
> + if (hweight_long(hwc->config & ARCH_PERFMON_EVENTSEL_UMASK) <= 1)
> + return &amd_f15_PMC20;
> + return &emptyconstraint;
> + case 0x1C0:
> + return &amd_f15_PMC53;
Oh man, that's just vile.. I hope you've given your hardware team a big
hug for this.. :-)
prev parent reply other threads:[~2012-05-18 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 10:40 [PATCH] perf, x86: Update event scheduling constraints for AMD family 15h models Robert Richter
2012-05-18 11:29 ` 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=1337340552.573.33.camel@twins \
--to=peterz@infradead.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=robert.richter@amd.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).