Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 28 Oct 2022 01:30:34 +0100
From:   Conor Dooley <conor@kernel.org>
To:     Samuel Holland <samuel@sholland.org>,
        Palmer Dabbelt <palmer@dabbelt.com>, apatel@ventanamicro.com
CC:     daniel.lezcano@linaro.org, tglx@linutronix.de,
        aou@eecs.berkeley.edu, atishp@atishpatra.org, dmitriy@oss-tech.org,
        Paul Walmsley <paul.walmsley@sifive.com>,
        linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: =?US-ASCII?Q?Re=3A_=5BPATCH=5D_clocksource/drivers/riscv=3A?= =?US-ASCII?Q?_Events_are_stopped_during_CPU_suspend?=
User-Agent: K-9 Mail for Android
In-Reply-To: <40abce35-b8de-cd5c-f544-fcf344e7057c@sholland.org>
References: <mhng-298aa3f7-7054-4695-bcb6-89be226a786b@palmer-ri-x1c9a> <40abce35-b8de-cd5c-f544-fcf344e7057c@sholland.org>
Message-ID: <6354C70F-86C7-430D-AF0A-3483B772B02C@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk


On 28 October 2022 00:41:45 IST, Samuel Holland <samuel@sholland=2Eorg> wr=
ote:
>
>I still don't see why you consider this patch to have broken anything=2E
>Can anyone explain why getting an RCU stall is better than not getting on=
e?

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 ar=
e stalls=2E With the patch, the system completely locks up during boot and =
never makes progress=2E I think I've done a bad job of getting across that =
the system just dies during boot=2E

(Apologies for formatting, mobile=2E=2E=2E)