From: "Arnd Bergmann" <arnd@arndb.de>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: "Stephen Boyd" <sboyd@kernel.org>,
"Tomasz Figa" <tomasz.figa@gmail.com>,
"Sylwester Nawrocki" <s.nawrocki@samsung.com>,
"Will Deacon" <will@kernel.org>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
"Dejin Zheng" <zhengdejin5@gmail.com>,
"Kai-Heng Feng" <kai.heng.feng@canonical.com>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Russell King" <linux@armlinux.org.uk>,
"John Stultz" <jstultz@google.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Tony Lindgren" <tony@atomide.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Tero Kristo" <tero.kristo@linux.intel.com>,
"Ulf Hansson" <ulf.hansson@linaro.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
linux-arm-kernel@lists.infradead.org,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] iopoll: Do not use timekeeping in read_poll_timeout_atomic()
Date: Wed, 10 May 2023 15:56:39 +0200 [thread overview]
Message-ID: <c6966111-cea0-4547-8463-46f9f767c20f@app.fastmail.com> (raw)
In-Reply-To: <CAMuHMdUg0gk3QUmC+OiBDQuZAWdJ2cbPpwaDX+TGoq1EPO1v-A@mail.gmail.com>
On Wed, May 10, 2023, at 15:46, Geert Uytterhoeven wrote:
> I first ran into it when converting open-coded loops to
> read*_poll_timeout_atomic().
> Later, I also saw the issue with the existing
> read*_poll_timeout_atomic() calls in the R-Car SYSC driver, but only
> after applying additional patches from the BSP that impact the moment
> PM Domains are powered during s2ram.
Ok
> The various pointers to existing mitigations in the cover letter should
> give you other suggestions for how to reproduce...
I see the cover letter now, I thought I had looked for it earlier but
didn't notice it.
Arnd
next prev parent reply other threads:[~2023-05-10 13:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 13:23 [PATCH v2 0/2] iopoll: Busy loop and timeout improvements Geert Uytterhoeven
2023-05-10 13:23 ` [PATCH v2 1/2] iopoll: Call cpu_relax() in busy loops Geert Uytterhoeven
2023-05-11 6:48 ` Tony Lindgren
2023-05-11 10:48 ` David Laight
2023-05-23 7:29 ` Geert Uytterhoeven
2023-05-23 8:55 ` David Laight
2023-05-11 9:48 ` Ulf Hansson
2023-05-10 13:23 ` [PATCH v2 2/2] iopoll: Do not use timekeeping in read_poll_timeout_atomic() Geert Uytterhoeven
2023-05-10 13:35 ` Arnd Bergmann
2023-05-10 13:46 ` Geert Uytterhoeven
2023-05-10 13:56 ` Arnd Bergmann [this message]
2023-05-11 6:48 ` Tony Lindgren
2023-05-11 10:26 ` Ulf Hansson
2023-05-11 12:44 ` Geert Uytterhoeven
2023-05-12 7:53 ` Ulf Hansson
2023-05-12 8:03 ` Geert Uytterhoeven
2023-05-15 9:26 ` Ulf Hansson
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=c6966111-cea0-4547-8463-46f9f767c20f@app.fastmail.com \
--to=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=hca@linux.ibm.com \
--cc=jstultz@google.com \
--cc=kai.heng.feng@canonical.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=tero.kristo@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tomasz.figa@gmail.com \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=will@kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=zhengdejin5@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