From: Andi Kleen <ak@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
"Liang, Kan" <kan.liang@intel.com>,
jolsa@redhat.com, bigeasy@linutronix.de,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>, x86 <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Long standing kernel warning: perfevents: irq loop stuck!
Date: Mon, 26 Feb 2018 12:39:37 -0800 [thread overview]
Message-ID: <20180226203937.GA21543@tassilo.jf.intel.com> (raw)
In-Reply-To: <20180223121456.GZ25201@hirez.programming.kicks-ass.net>
> Given the HSD143 errata and its possible relevance, have you tried
> changing the magic number to 32, does it then still fix things?
>
> No real objection to the patch as such, it just needs a coherent comment
> and a tested-by tag I think.
128 min period will affect a lot of valid use cases with slower ticking
events. I often use smaller periods there.
It would be better to debug this properly.
Or at a minimum only do the limitation for the events that tick really
fast (like cycles, uops retired etc.)
-Andi
next prev parent reply other threads:[~2018-02-26 20:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 4:59 Cong Wang
2018-02-23 12:14 ` Peter Zijlstra
2018-02-26 20:32 ` Cong Wang
2018-02-26 20:39 ` Andi Kleen [this message]
2019-08-12 17:24 ` Josh Hunt
2019-08-12 17:54 ` Thomas Gleixner
2019-08-12 18:57 ` Josh Hunt
2019-08-12 19:34 ` Thomas Gleixner
2019-08-12 19:42 ` Josh Hunt
2019-08-19 21:17 ` Josh Hunt
2019-08-19 23:16 ` Josh Hunt
2019-08-22 14:31 ` 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=20180226203937.GA21543@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xiyou.wangcong@gmail.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