From: Andi Kleen <ak@linux.intel.com>
To: Calvin Owens <calvin@wbinvd.org>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Thomas Gleixner <tglx@kernel.org>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 0/2] Two semi-related perf throttling fixes
Date: Wed, 01 Apr 2026 01:01:20 -0700 [thread overview]
Message-ID: <87y0j7w1m7.fsf@linux.intel.com> (raw)
In-Reply-To: <cover.1774969692.git.calvin@wbinvd.org> (Calvin Owens's message of "Tue, 31 Mar 2026 08:25:48 -0700")
Calvin Owens <calvin@wbinvd.org> writes:
> Hi all,
>
> In the course of investigating [1], I set out to understand why this
> sequence of messages is printed every boot, even when nobody is using
> perf at all:
I don't think i've ever seen that just from the NMI watchdog. I wonder
what is different on your machines. And of course the PMU based NMI
watchdog is on the way out.
But the fixes make sense to me.
Reviewed-by: Andi Kleen <ak@kernel.org>
prev parent reply other threads:[~2026-04-01 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 15:25 [PATCH 0/2] Two semi-related perf throttling fixes Calvin Owens
2026-03-31 15:25 ` [PATCH 1/2] perf/x86: Avoid double accounting of PMU NMI latencies Calvin Owens
2026-03-31 15:25 ` [PATCH 2/2] perf: Don't throttle based on NMI watchdog events Calvin Owens
2026-03-31 17:22 ` Calvin Owens
2026-03-31 17:43 ` Calvin Owens
2026-03-31 18:10 ` Calvin Owens
2026-03-31 21:07 ` Calvin Owens
2026-04-01 8:01 ` Andi Kleen [this message]
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=87y0j7w1m7.fsf@linux.intel.com \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=calvin@wbinvd.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=x86@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.