[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6354C70F-86C7-430D-AF0A-3483B772B02C@kernel.org>
Date: Fri, 28 Oct 2022 01:30:34 +0100
From: Conor Dooley <conor@...nel.org>
To: Samuel Holland <samuel@...lland.org>,
Palmer Dabbelt <palmer@...belt.com>, apatel@...tanamicro.com
CC: daniel.lezcano@...aro.org, tglx@...utronix.de,
aou@...s.berkeley.edu, atishp@...shpatra.org, dmitriy@...-tech.org,
Paul Walmsley <paul.walmsley@...ive.com>,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject: Re: [PATCH] clocksource/drivers/riscv: Events are stopped during CPU suspend
On 28 October 2022 00:41:45 IST, Samuel Holland <samuel@...lland.org> wrote:
>
>I still don't see why you consider this patch to have broken anything.
>Can anyone explain why getting an RCU stall is better than not getting one?
Taking that to the extreme, why even have RCU stall detection at all? It's not a case of with the patch the system works fine and without it there are stalls. With the patch, the system completely locks up during boot and never makes progress. I think I've done a bad job of getting across that the system just dies during boot.
(Apologies for formatting, mobile...)
Powered by blists - more mailing lists