linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Josh Hunt <johunt@akamai.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
	mingo@redhat.com, acme@kernel.org,
	alexander.shishkin@linux.intel.com, jolsa@redhat.com,
	namhyung@kernel.org, bpuranda@akamai.com
Subject: Re: [PATCH] perf/x86/intel: restrict period on Nehalem
Date: Fri, 23 Aug 2019 10:07:06 +0200	[thread overview]
Message-ID: <20190823080706.GA2369@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1566256411-18820-1-git-send-email-johunt@akamai.com>

On Mon, Aug 19, 2019 at 07:13:31PM -0400, Josh Hunt wrote:
> We see our Nehalem machines reporting 'perfevents: irq loop stuck!' in
> some cases when using perf:
> 
> perfevents: irq loop stuck!

> I found that a period limit of 32 was the lowest I could set it to without
> the problem reoccurring. The idea for the patch and approach to find the
> target value were suggested by Ingo and Thomas.
> 
> Signed-off-by: Josh Hunt <johunt@akamai.com>
> Reported-by: Bhupesh Purandare <bpuranda@akamai.com>
> Suggested-by: Thomas Gleixner <tglx@linutronix.de>
> Suggested-by: Ingo Molnar <mingo@redhat.com>
> Link: https://lore.kernel.org/lkml/20150501070226.GB18957@gmail.com/
> Link: https://lore.kernel.org/lkml/alpine.DEB.2.21.1908122133310.7324@nanos.tec.linutronix.de/

Thanks!

  reply	other threads:[~2019-08-23  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 23:13 [PATCH] perf/x86/intel: restrict period on Nehalem Josh Hunt
2019-08-23  8:07 ` Peter Zijlstra [this message]
2019-08-31  9:06 ` [tip: perf/urgent] perf/x86/intel: Restrict " tip-bot2 for Josh Hunt

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=20190823080706.GA2369@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bpuranda@akamai.com \
    --cc=johunt@akamai.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).