From: Dave Hansen <dave.hansen@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>, Borislav Petkov <bp@alien8.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
andi@lisas.de, Pu Wen <puwen@hygon.cn>,
Mario Limonciello <mario.limonciello@amd.com>,
"Zhang, Rui" <rui.zhang@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
ananth.narayan@amd.com, gautham.shenoy@amd.com,
Calvin Ong <calvin.ong@amd.com>, Stable <stable@vger.kernel.org>,
regressions@lists.linux.dev
Subject: Re: [PATCH] ACPI: processor_idle: Skip dummy wait for processors based on the Zen microarchitecture
Date: Thu, 22 Sep 2022 09:36:05 -0700 [thread overview]
Message-ID: <f3916119-420b-bfd7-e148-e9dd422813c8@intel.com> (raw)
In-Reply-To: <CAJZ5v0i0NzJfRuqcuJQC3J5moaEikoRusquCybAz0T8dMy8gCw@mail.gmail.com>
On 9/22/22 08:53, Rafael J. Wysocki wrote:
> On Thu, Sep 22, 2022 at 5:36 PM Borislav Petkov <bp@alien8.de> wrote:
>> On Thu, Sep 22, 2022 at 05:21:21PM +0200, Rafael J. Wysocki wrote:
>>> Well, it can be forced to use ACPI idle instead.
>> Yeah, I did that earlier. The dummy IO read in question costs ~3K on
>> average on my Coffeelake box here.
> Well, that's the cost of forcing something non-default.
Just to be clear: The _original_ AMD Zen problem that this thread is
addressing is from a *default* configuration, right? It isn't that
someone overrode the idle defaults?
next prev parent reply other threads:[~2022-09-22 16:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 6:36 [PATCH] ACPI: processor_idle: Skip dummy wait for processors based on the Zen microarchitecture K Prateek Nayak
2022-09-21 8:47 ` Borislav Petkov
2022-09-21 10:39 ` K Prateek Nayak
2022-09-21 13:10 ` Borislav Petkov
2022-09-21 14:15 ` Dave Hansen
2022-09-21 19:51 ` Borislav Petkov
2022-09-21 19:55 ` Limonciello, Mario
2022-09-22 3:58 ` Ananth Narayan
2022-09-22 5:44 ` K Prateek Nayak
[not found] ` <20220923160106.9297-1-ermorton@ericmoronsm1mbp.amd.com>
2022-09-23 16:15 ` Ananth Narayan
2022-09-21 15:00 ` Peter Zijlstra
2022-09-21 19:48 ` Borislav Petkov
2022-09-22 8:17 ` Peter Zijlstra
2022-09-22 15:21 ` Rafael J. Wysocki
2022-09-22 15:36 ` Borislav Petkov
2022-09-22 15:53 ` Rafael J. Wysocki
2022-09-22 16:36 ` Dave Hansen [this message]
2022-09-22 16:44 ` Dave Hansen
2022-09-22 16:54 ` K Prateek Nayak
2022-09-22 17:01 ` Dave Hansen
2022-09-22 17:48 ` Limonciello, Mario
2022-09-22 18:17 ` Dave Hansen
2022-09-22 18:28 ` Limonciello, Mario
2022-09-23 11:47 ` Ananth Narayan
2022-09-22 19:42 ` Andreas Mohr
2022-09-22 20:10 ` Andreas Mohr
2022-09-22 21:21 ` Dave Hansen
2022-09-22 21:38 ` Limonciello, Mario
2022-09-23 7:42 ` Peter Zijlstra
2022-09-23 7:57 ` Peter Zijlstra
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=f3916119-420b-bfd7-e148-e9dd422813c8@intel.com \
--to=dave.hansen@intel.com \
--cc=ananth.narayan@amd.com \
--cc=andi@lisas.de \
--cc=bp@alien8.de \
--cc=calvin.ong@amd.com \
--cc=daniel.lezcano@linaro.org \
--cc=dave.hansen@linux.intel.com \
--cc=gautham.shenoy@amd.com \
--cc=gpiccoli@igalia.com \
--cc=kprateek.nayak@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=peterz@infradead.org \
--cc=puwen@hygon.cn \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=rui.zhang@intel.com \
--cc=stable@vger.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