mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: "Yan, Zheng" <zheng.z.yan@intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	eranian@google.com, mingo@elte.hu, andi@firstfloor.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 5/5] perf/x86: Add Intel Nehalem-EX uncore support
Date: Thu, 5 Jul 2012 16:51:24 +0200	[thread overview]
Message-ID: <20120705145124.GS11413@one.firstfloor.org> (raw)
In-Reply-To: <4FF534F1.3030307@intel.com>

On Thu, Jul 05, 2012 at 02:32:17PM +0800, Yan, Zheng wrote:
> The uncore subsystem in Nehalem-EX consists of 7 components
> (U-Box, C-Box, B-Box, S-Box, R-Box, M-Box and W-Box). This
> patch is large because the way to program these boxes is
> diverse.

Thanks for doing the driver. Lots of work.

May be worth adding a CONFIG for the uncore code now?
Maybe even a module, so that not every distro kernel has it always
in memory. I don't think perf has support for tracking
module counts, but I guess it would be ok to have the module be not
unloadable once loaded by setting the count to -1.

Also did you do some random testing by putting randomized values into
all the exported registers and see if anything is crashable for 
unpriv. userspace?

> +		 * events are functional identical, but use different
> +		 * extra registers. If we failed to take an extra
> +		 * register, try the alternative.
> +		 */
> +		if (idx % 2)
> +			idx--;
> +		else
> +			idx++;
> +		if (idx != reg1->idx % 6) {
> +			if (idx == 2)
> +				config1 >>= 8;
> +			else if (idx == 3)
> +				config1 <<= 8;
> +			goto again;

Does this limit the retries?

> @@ -1767,6 +2821,9 @@ static int __init uncore_cpu_init(void)
>  			snbep_uncore_cbox.num_boxes = max_cores;
>  		msr_uncores = snbep_msr_uncores;
>  		break;
> +	case 46:
> +		msr_uncores = nhmex_msr_uncores;
> +		break;

Ok need Westmere-EX too. I think that is quite similar.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2012-07-05 14:51 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 
2012-07-05  6:32     ` [PATCH V2 " Yan, Zheng
2012-07-05 14:51       ` Andi Kleen [this message]
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=20120705145124.GS11413@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=a.p.zijlstra@chello.nl \
    --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

Powered by JetHome