From: "Yan, Zheng " <yanzheng@21cn.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: "Yan, Zheng" <zheng.z.yan@intel.com>,
eranian@google.com, mingo@elte.hu, andi@firstfloor.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] perf/x86: Add Intel Nehalem-EX uncore support
Date: Thu, 5 Jul 2012 01:46:50 +0800 [thread overview]
Message-ID: <CAAM7YA=UdSrNbaoidr+CKBUmth_Yxhvc5=WPxjeb-H9FchkRhg@mail.gmail.com> (raw)
In-Reply-To: <1341420818.19870.10.camel@laptop>
On Thu, Jul 5, 2012 at 12:53 AM, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Thu, 2012-07-05 at 00:00 +0800, Yan, Zheng wrote:
>>
>> > Also, how can a single extra register require 192 bits of config space?
>> >
>> Some events in the M-Box and R-Box require programming up to 3 extra
>> registers. For example, the event 0x5 in the R-Box requires programming
>> extra registers XBR_SET1_MM_CFG, XBR_SET1_MATCH and XBR_SET1_MATCH.
>
> But shouldn't you then use 3 extra_reg instead of blowing up the one?
>
These 3 registers are within a logical set, are always used at the same time.
I think it's natural to use a single data structure to track them.
Regards
Yan, Zheng
next prev parent reply other threads:[~2012-07-04 17:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 6:00 [PATCH 0/5] perf/x86: Uncore updates Yan, Zheng
2012-07-04 6:00 ` [PATCH 1/5] perf/x86: Use 0xff as pseudo code for fixed uncore event Yan, Zheng
2012-07-04 6:00 ` [PATCH 2/5] perf/x86: Fix event constraint for SandyBridge-EP CBox Yan, Zheng
2012-07-04 6:00 ` [PATCH 3/5] perf/x86: Detect number of instances of uncore CBox Yan, Zheng
2012-07-06 6:32 ` [tip:perf/core] " tip-bot for Yan, Zheng
2012-07-04 6:00 ` [PATCH 4/5] perf/x86: Uncore filter support for SandyBridge-EP Yan, Zheng
2012-07-06 6:33 ` [tip:perf/core] " tip-bot for Yan, Zheng
2012-07-22 19:25 ` [PATCH 4/5] " Stephane Eranian
2012-07-04 6:00 ` [PATCH 5/5] perf/x86: Add Intel Nehalem-EX uncore support Yan, Zheng
2012-07-04 10:04 ` Peter Zijlstra
2012-07-04 16:00 ` Yan, Zheng
2012-07-04 16:53 ` Peter Zijlstra
2012-07-04 17:46 ` Yan, Zheng [this message]
2012-07-05 6:32 ` [PATCH V2 " Yan, Zheng
2012-07-05 14:51 ` Andi Kleen
2012-07-05 15:46 ` Yan, Zheng
2012-07-10 12:17 ` Peter Zijlstra
2012-07-11 2:06 ` Yan, Zheng
2012-07-11 9:57 ` Peter Zijlstra
2012-07-11 12:02 ` Yan, Zheng
2012-07-26 15:11 ` [tip:perf/core] " 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='CAAM7YA=UdSrNbaoidr+CKBUmth_Yxhvc5=WPxjeb-H9FchkRhg@mail.gmail.com' \
--to=yanzheng@21cn.com \
--cc=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 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.