From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Stephane Eranian <eranian@google.com>
Cc: "Yan, Zheng" <zheng.z.yan@intel.com>,
mingo@elte.hu, andi@firstfloor.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] perf/x86: Fix format definition of SNB-EP uncore QPI box
Date: Mon, 23 Jul 2012 18:36:22 +0200 [thread overview]
Message-ID: <1343061382.26034.1.camel@twins> (raw)
In-Reply-To: <CABPqkBSLk_fCBEbVgNVc3iGsOFaSiKpPYF5krj_wymDP=SA6Cg@mail.gmail.com>
On Mon, 2012-07-23 at 18:33 +0200, Stephane Eranian wrote:
>
> DEFINE_UNCORE_FORMAT_ATTR(event, event, "config:0-7,21");
>
> Assuming the event parser supports disjoint bits.
It does. Userspace should provide a 9bit value in this case and the 9th
bit will be stored in bit 21.
next prev parent reply other threads:[~2012-07-23 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 6:23 [PATCH 1/4] perf/x86: Fix typo in format definition of uncore PCU filter Yan, Zheng
2012-07-23 6:23 ` [PATCH 2/4] perf/x86: Fix format definition of SNB-EP uncore QPI box Yan, Zheng
2012-07-23 16:33 ` Stephane Eranian
2012-07-23 16:36 ` Peter Zijlstra [this message]
2012-07-26 15:11 ` [tip:perf/core] perf/x86: Fix typo in format definition of uncore PCU filter tip-bot for Yan, Zheng
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=1343061382.26034.1.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zheng.z.yan@intel.com \
/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