[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YxC3Ra5iZDdYX7sW@xhacker>
Date: Thu, 1 Sep 2022 21:44:37 +0800
From: Jisheng Zhang <jszhang@...nel.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Anup Patel <anup@...infault.org>,
Atish Patra <atishp@...shpatra.org>,
Thomas Gleixner <tglx@...utronix.de>,
Steven Rostedt <rostedt@...dmis.org>,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, kvm-riscv@...ts.infradead.org
Subject: Re: [PATCH v2 0/5] riscv: add PREEMPT_RT support
On Thu, Sep 01, 2022 at 09:04:05AM +0200, Sebastian Andrzej Siewior wrote:
> On 2022-09-01 01:59:15 [+0800], Jisheng Zhang wrote:
> > I assume patch1, patch2 and patch3 can be reviewed and merged for
> > riscv-next, patch4 and patch5 can be reviewed and maintained in rt tree,
> > and finally merged once the remaining patches in rt tree are all
> > mainlined.
>
> I would say so, yes.
>
> What about JUMP_LABEL support? Do you halt all CPUs while patching the
> code?
>
FWICT, riscv JUMP_LABEL implementation doesn't rely on stop all cpus while
patching text.
Thanks
Powered by blists - more mailing lists