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: Re: [PATCH] clocksource/drivers/riscv: Events are stopped during CPU suspend
Date: Fri, 28 Oct 2022 01:30:34 +0100 [thread overview]
Message-ID: <6354C70F-86C7-430D-AF0A-3483B772B02C@kernel.org> (raw)
In-Reply-To: <40abce35-b8de-cd5c-f544-fcf344e7057c@sholland.org>
On 28 October 2022 00:41:45 IST, Samuel Holland <samuel@sholland.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...)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-10-28 0:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 1:21 [PATCH] clocksource/drivers/riscv: Events are stopped during CPU suspend Samuel Holland
2022-05-09 2:56 ` Jessica Clarke
2022-05-09 3:51 ` Anup Patel
2022-05-09 11:44 ` Daniel Lezcano
2022-09-29 21:50 ` Conor Dooley
2022-10-09 23:45 ` Palmer Dabbelt
2022-10-24 5:01 ` Samuel Holland
2022-10-24 7:04 ` Conor Dooley
2022-10-24 8:04 ` Anup Patel
2022-10-27 23:07 ` Palmer Dabbelt
2022-10-27 23:41 ` Samuel Holland
2022-10-28 0:30 ` Conor Dooley [this message]
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=6354C70F-86C7-430D-AF0A-3483B772B02C@kernel.org \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=daniel.lezcano@linaro.org \
--cc=dmitriy@oss-tech.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel@sholland.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