From: "Clément Léger" <cleger@rivosinc.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>,
Palmer Dabbelt <palmer@dabbelt.com>
Cc: namcao@linutronix.de, Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, Alexandre Ghiti <alex@ghiti.fr>,
bigeasy@linutronix.de, clrkwllms@kernel.org, rostedt@goodmis.org,
linux-rt-devel@lists.linux.dev, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Enable interrupt during exception handling
Date: Tue, 24 Jun 2025 13:37:13 +0200 [thread overview]
Message-ID: <19cf2371-7293-4e71-a17d-669db4c8270a@rivosinc.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2506240303170.61655@angie.orcam.me.uk>
On 24/06/2025 04:09, Maciej W. Rozycki wrote:
> On Mon, 23 Jun 2025, Palmer Dabbelt wrote:
>
>> I'm kind of split on a Fixes tag here. One could argue it's a regression, as
>> having interrupts disabled during exceptions is going to cause all sorts of
>> performance issues for users. Seems a bit risk to just backport, though...
>>
>> That said, if nobody noticed then it's probably a good sign nobody is really
>> paying attention and we should just backport it before anyone notices...
>
> Oh, someone did notice and it's not only performance, cf.
> <https://lore.kernel.org/r/alpine.DEB.2.21.2501070143250.18889@angie.orcam.me.uk/>.
I also had a series which was doing so for misaligned accesses handling,
but after discussion, it was not ok to do so.:
https://lore.kernel.org/linux-riscv/20250422094419.GC14170@noisy.programming.kicks-ass.net/
So this series should probably be modified to only reenable interrupts
when explicitly needed, ie page faults and for force_sig_fault().
Thanks,
Clément
>
> Maciej
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-06-24 11:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 11:43 Nam Cao
2025-06-23 22:17 ` Palmer Dabbelt
2025-06-24 2:09 ` Maciej W. Rozycki
2025-06-24 11:37 ` Clément Léger [this message]
2025-06-24 13:17 ` Nam Cao
2025-06-24 13:48 ` Clément Léger
2025-06-24 14:08 ` Peter Zijlstra
2025-06-24 14:11 ` Sebastian Andrzej Siewior
2025-06-24 14:18 ` Peter Zijlstra
2025-06-24 14:23 ` Sebastian Andrzej Siewior
2025-06-24 14:34 ` Peter Zijlstra
2025-06-24 15:33 ` Nam Cao
2025-06-24 18:51 ` Peter Zijlstra
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=19cf2371-7293-4e71-a17d-669db4c8270a@rivosinc.com \
--to=cleger@rivosinc.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=macro@orcam.me.uk \
--cc=namcao@linutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rostedt@goodmis.org \
/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
all inboxes | Powered by JetHome®