[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250624143458.GW1613200@noisy.programming.kicks-ass.net>
Date: Tue, 24 Jun 2025 16:34:58 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Clément Léger <cleger@...osinc.com>,
Nam Cao <namcao@...utronix.de>,
"Maciej W. Rozycki" <macro@...am.me.uk>,
Palmer Dabbelt <palmer@...belt.com>,
Paul Walmsley <paul.walmsley@...ive.com>, aou@...s.berkeley.edu,
Alexandre Ghiti <alex@...ti.fr>, clrkwllms@...nel.org,
rostedt@...dmis.org, linux-rt-devel@...ts.linux.dev,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] riscv: Enable interrupt during exception handling
On Tue, Jun 24, 2025 at 04:23:50PM +0200, Sebastian Andrzej Siewior wrote:
> On 2025-06-24 16:18:01 [+0200], Peter Zijlstra wrote:
> > I'm confused, sending signals is for exception from userspace. That has
> > nothing to do with exceptions from kernelspace being NMI like.
>
> Yes. See the original submission
> https://lore.kernel.org/linux-riscv/20250620114346.1740512-1-namcao@linutronix.de/
I'm still confused, that code is trying to enable IRQs in the
from-kernel part. That's insane.
Can some Risc-V person explain why a from-kernel exception would ever
result in a signal?!?!
Powered by blists - more mailing lists