From: Borislav Petkov <bp@alien8.de>
To: K Prateek Nayak <kprateek.nayak@amd.com>
Cc: linux-kernel@vger.kernel.org, rafael@kernel.org, lenb@kernel.org,
linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org,
dave.hansen@linux.intel.com, tglx@linutronix.de, andi@lisas.de,
puwen@hygon.cn, mario.limonciello@amd.com, peterz@infradead.org,
rui.zhang@intel.com, gpiccoli@igalia.com,
daniel.lezcano@linaro.org, ananth.narayan@amd.com,
gautham.shenoy@amd.com, Calvin Ong <calvin.ong@amd.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] x86,acpi: Limit "Dummy wait" workaround to older AMD and Intel processors
Date: Fri, 23 Sep 2022 18:30:13 +0200 [thread overview]
Message-ID: <Yy3fFciusHZ2h1GW@zn.tnic> (raw)
In-Reply-To: <f020defb-df73-35ff-5d97-c07773bafb67@amd.com>
On Fri, Sep 23, 2022 at 09:55:02PM +0530, K Prateek Nayak wrote:
> Yes, I did see the patch, but Andreas replied to Dave's patch attached
> in v1 saying that he had seen this issue with AMD Athlon on a VIA
> chipset back in 2006. (https://lore.kernel.org/lkml/Yyy6l94G0O2B7Yh1@rhlx01.hs-esslingen.de/)
> Therefore, Dave's patch is not sufficient.
Well, AFAICT, that box is old and dead. And I'm being told that the AMD
machines which we care for and which are still alive should not need the
dummy read.
Which means, we could try the simple fix first and see who complains.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-09-23 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 15:38 [PATCH v2] x86,acpi: Limit "Dummy wait" workaround to older AMD and Intel processors K Prateek Nayak
2022-09-23 15:46 ` Borislav Petkov
2022-09-23 16:25 ` K Prateek Nayak
2022-09-23 16:30 ` Borislav Petkov [this message]
2022-09-23 16:52 ` K Prateek Nayak
2022-09-26 8:19 ` David Laight
2022-09-26 12:07 ` Peter Zijlstra
2022-09-26 16:32 ` K Prateek Nayak
2022-09-26 19:55 ` Andreas Mohr
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=Yy3fFciusHZ2h1GW@zn.tnic \
--to=bp@alien8.de \
--cc=ananth.narayan@amd.com \
--cc=andi@lisas.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.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--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