public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, eranian@google.com,
	peterz@infradead.org, Andi Kleen <ak@linux.jf.intel.com>
Subject: Re: [PATCH] perf, x86: Support full width counting v3
Date: Tue, 25 Jun 2013 09:22:12 +0200	[thread overview]
Message-ID: <20130625072212.GA11420@gmail.com> (raw)
In-Reply-To: <1372121749-12164-1-git-send-email-andi@firstfloor.org>


* Andi Kleen <andi@firstfloor.org> wrote:

> From: Andi Kleen <ak@linux.intel.com>
> 
> Recent Intel CPUs like Haswell and IvyBridge have a new alternative MSR
> range for perfctrs that allows writing the full counter width. Enable this
> range if the hardware reports it using a new capability bit.
> 
> This lowers the overhead of perf stat slightly because it has to do less
> interrupts to accumulate the counter value. On Haswell it also avoids some
> problems with TSX aborting when the end of the counter range is reached.

Looks good - the changelog needs more work: please first outline the 
current behavior (how we can only write 32 bit values into the counter, 
even though the counter range is larger on most CPUs).

Then also outline the Haswell problems more precisely. What happens, why, 
with what probability and why do we care?

Thanks,

	Ingo

       reply	other threads:[~2013-06-25  7:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1372121749-12164-1-git-send-email-andi@firstfloor.org>
2013-06-25  7:22 ` Ingo Molnar [this message]
2013-06-25  7:23   ` [PATCH] perf, x86: Support full width counting v3 Ingo Molnar

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=20130625072212.GA11420@gmail.com \
    --to=mingo@kernel.org \
    --cc=ak@linux.jf.intel.com \
    --cc=andi@firstfloor.org \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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