From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-edac@vger.kernel.org, X86 ML <x86@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
bberg@redhat.com, bp@suse.de
Subject: Re: [PATCH 3/3] x86/mce/therm_throt: allow disabling the thermal vector altogether
Date: Mon, 13 Apr 2020 22:21:08 -0600 [thread overview]
Message-ID: <CAHmME9pigvAgK3Bje6DkFEcdyWwi7-C7D6QEo4YiH_cbJvxqhQ@mail.gmail.com> (raw)
In-Reply-To: <0e189a4fe1e69b08afc859ce83623a0e5ea0c08b.camel@linux.intel.com>
On Mon, Apr 13, 2020 at 9:38 PM Srinivas Pandruvada
<srinivas.pandruvada@linux.intel.com> wrote:
>
> On Tue, 2020-04-07 at 00:33 -0600, Jason A. Donenfeld wrote:
> > The thermal IRQ handler uses 1.21% CPU on my system when it's hot
> > from
> > compiling things. Indeed looking at /proc/interrupts reveals quite a
> > lot
> I am curious why you are hitting threshold frequently?
> What is rdmsr 0x1a2
5640000
> > of events coming in. Beyond logging them, the existing drivers on the
> > system don't appear to do very much that I'm interested in. So, add a
> > way to disable this entirely so that I can regain precious CPU
> > cycles.
> It is showing amount of time system is running in a constrained
> environment. Lots of real time and HPC folks really care about this.
Which is why this patch adds an option, not a full removal or
something. Real time and HPC people can keep their expensive
interrupt. Other people with different varieties of system can disable
it.
next prev parent reply other threads:[~2020-04-14 4:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 6:33 [PATCH 1/3] x86/mce/therm_throt: remove unused platform_thermal_notify function pointer Jason A. Donenfeld
2020-04-07 6:33 ` [PATCH 2/3] x86/mce/therm_throt: allow disabling verbose logging Jason A. Donenfeld
2020-04-07 6:33 ` [PATCH 3/3] x86/mce/therm_throt: allow disabling the thermal vector altogether Jason A. Donenfeld
2020-04-14 3:38 ` Srinivas Pandruvada
2020-04-14 4:21 ` Jason A. Donenfeld [this message]
2020-04-14 14:45 ` Srinivas Pandruvada
2020-04-14 19:41 ` Jason A. Donenfeld
2020-04-14 19:58 ` Srinivas Pandruvada
2020-04-14 20:09 ` Jason A. Donenfeld
2020-04-14 20:23 ` Borislav Petkov
2020-04-14 20:49 ` Srinivas Pandruvada
2020-04-14 21:07 ` Jason A. Donenfeld
2020-04-14 21:51 ` Srinivas Pandruvada
2020-04-14 21:40 ` Peter Zijlstra
2020-04-14 21:44 ` Srinivas Pandruvada
2020-04-13 21:09 ` [PATCH 1/3] x86/mce/therm_throt: remove unused platform_thermal_notify function pointer Jason A. Donenfeld
2020-04-14 3:55 ` Srinivas Pandruvada
2020-04-14 4:21 ` Jason A. Donenfeld
2020-04-14 14:49 ` Srinivas Pandruvada
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=CAHmME9pigvAgK3Bje6DkFEcdyWwi7-C7D6QEo4YiH_cbJvxqhQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=arnd@arndb.de \
--cc=bberg@redhat.com \
--cc=bp@suse.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--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 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).