All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf, x86: Allow setting period 1
Date: Wed, 10 Apr 2013 06:31:57 -0700	[thread overview]
Message-ID: <20130410133157.GG22166@tassilo.jf.intel.com> (raw)
In-Reply-To: <20130410125808.GC12978@gmail.com>

On Wed, Apr 10, 2013 at 02:58:08PM +0200, Ingo Molnar wrote:
> 
> * Andi Kleen <andi@firstfloor.org> wrote:
> 
> > From: Andi Kleen <ak@linux.intel.com>
> > 
> > I had some requests for setting period 1, so that every event of something
> > is caught.  To my knowledge there is no limit to 1 on Intel hardware.
> > Just remove the check for minimum 2
> > 
> > If specific CPUs have problems we can black list them.
> 
> How have you tested this? The commit that added this quirk mentions very high perf 
> load triggering badness unless this quirk is added.

Profiling a couple of simple loads on Westmere and IvyBridge: mostly AIM7 and
kernel builds. You can get throttling of course, but no excessive load.

The original quirk was done long ago before the modern event throttling
infrastructure may have been completely in place, right?

-Andi

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

  reply	other threads:[~2013-04-10 13:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 23:24 [PATCH] perf, x86: Allow setting period 1 Andi Kleen
2013-03-28 15:44 ` Andi Kleen
2013-04-10 12:58 ` Ingo Molnar
2013-04-10 13:31   ` Andi Kleen [this message]
2013-04-15 11:26     ` 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=20130410133157.GG22166@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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 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.