From: Xu Lu <luxu.kernel@bytedance.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Anup Patel <anup@brainfault.org>,
Charlie Jenkins <charlie@rivosinc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
lihangjing@bytedance.com, Xie Yongji <xieyongji@bytedance.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [External] Re: [PATCH RESEND] irqchip: riscv: Order normal writes and IPI writes
Date: Tue, 28 Jan 2025 00:37:49 +0800 [thread overview]
Message-ID: <CAPYmKFtx6GNE5r-R33aiHeF-qgFESH0sbsorttjJ88wTL8yr9w@mail.gmail.com> (raw)
In-Reply-To: <a7d9b0e5-7ef6-457e-ace6-c56e745c3150@app.fastmail.com>
On Tue, Jan 28, 2025 at 12:23 AM Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Mon, Jan 27, 2025, at 10:38, Xu Lu wrote:
> > RISC-V distinguishes between normal memory accesses and device I/O and
> > uses FENCE instruction to order them as viewed by othe RISC-V harts and
> > external devices or coprocessors. The FENCE instruction can order any
> > combination of device input(I), device output(O), memory reads(R) and
> > memory writes(W). For example, 'fence w, o' can be used to ensure all
> > memory writes from instructions preceding the FENCE instruction appear
> > earlier in the global memory order than device output writes from
> > instructions after the FENCE instruction.
>
> There is nothing risc-v specific in here really, it's just a bug
> in the driver: writel() means access the mmio register with appropriate
> barriers, while writel_relaxed() is a special case that should
> only ever be used if a particular function is sensitive to
> performance and never needs to be serialized.
>
> > diff --git a/drivers/irqchip/irq-thead-c900-aclint-sswi.c
> > b/drivers/irqchip/irq-thead-c900-aclint-sswi.c
> > index b0e366ade427..8ff6e7a1363b 100644
> > --- a/drivers/irqchip/irq-thead-c900-aclint-sswi.c
> > +++ b/drivers/irqchip/irq-thead-c900-aclint-sswi.c
> > @@ -31,7 +31,7 @@ static DEFINE_PER_CPU(void __iomem *, sswi_cpu_regs);
> >
> > static void thead_aclint_sswi_ipi_send(unsigned int cpu)
> > {
> > - writel_relaxed(0x1, per_cpu(sswi_cpu_regs, cpu));
> > + writel(0x1, per_cpu(sswi_cpu_regs, cpu));
> > }
> >
> > static void thead_aclint_sswi_ipi_clear(void)
> > --
>
> thead_aclint_sswi_ipi_clear() seems to have the same bug,
> it also uses the _relaxed() version for no apparent reason.
Hi Arnd,
There seems no need to modify thead_aclint_sswi_ipi_clear() as it only
clears pending IPI on current hart. No other harts require to see
strict order between preceding memory writes and this ACLINT MMIO
write. Please correct me if I missed anything.
Thanks,
Xu Lu
>
> Arnd
next prev parent reply other threads:[~2025-01-27 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 9:38 Xu Lu
2025-01-27 10:13 ` [tip: irq/urgent] irqchip/riscv: Ensure ordering of memory " tip-bot2 for Xu Lu
2025-01-27 10:33 ` [PATCH RESEND] irqchip: riscv: Order normal " Thomas Gleixner
2025-01-27 14:26 ` [External] " Xu Lu
2025-01-27 16:21 ` Arnd Bergmann
2025-01-27 16:37 ` Xu Lu [this message]
2025-01-27 19:07 ` [External] " Arnd Bergmann
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=CAPYmKFtx6GNE5r-R33aiHeF-qgFESH0sbsorttjJ88wTL8yr9w@mail.gmail.com \
--to=luxu.kernel@bytedance.com \
--cc=anup@brainfault.org \
--cc=arnd@arndb.de \
--cc=charlie@rivosinc.com \
--cc=lihangjing@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=tglx@linutronix.de \
--cc=xieyongji@bytedance.com \
/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®