public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dylan Jhong <dylan@andestech.com>
To: Zong Li <zongbox@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
	<guoren@kernel.org>, <sergey.matyukevich@syntacore.com>,
	<aou@eecs.berkeley.edu>, <palmer@dabbelt.com>,
	<paul.walmsley@sifive.com>, <x5710999x@gmail.com>,
	<tim609@andestech.com>, <peterlin@andestech.com>,
	<ycliang@andestech.com>, <alistair.francis@wdc.com>
Subject: Re: [PATCH v2] riscv: mm: Fix incorrect ASID argument when flushing TLB
Date: Tue, 14 Mar 2023 15:27:28 +0800	[thread overview]
Message-ID: <ZBAh4EY2RNLryzEW@APC323> (raw)
In-Reply-To: <CA+ZOyahmpKXq2K-VqKkfN8t5aLDwU-OvL46oj9nNpdm6ZU3qNQ@mail.gmail.com>

On Tue, Mar 14, 2023 at 10:22:43AM +0800, Zong Li wrote:
> Dylan Jhong <dylan@andestech.com> 於 2023年3月13日 週一 下午12:29寫道:
> >
> > Currently, we pass the CONTEXTID instead of the ASID to the TLB flush
> > function. We should only take the ASID field to prevent from touching
> > the reserved bit field.
> >
> > Fixes: 3f1e782998cd ("riscv: add ASID-based tlbflushing methods")
> > Signed-off-by: Dylan Jhong <dylan@andestech.com>
> > ---
> 
> Hi Dylan,
> Thanks for your patch, if I remember correctly, there was a patch from
> Alistair Francis did the similar fix. Perhaps we should track that
> patch to see why it doesn't be merged. Thanks.
> 
> http://lists.infradead.org/pipermail/linux-riscv/2022-March/013558.html
>
Hi Zong,
Thanks for the reminder, I didn't notice that Alistair had sent the same patch before.

Hi Palmer, Alistair
http://lists.infradead.org/pipermail/linux-riscv/2022-March/013597.html
This patch does not seem to be cherry-picked back to the released linux kernel,
and I have not seen the v4 patch. May I ask how is the follow-up progress of this patch?

Best,
Dylan

> > Changes from v2:
> > - Remove unsued EXPORT_SYMBOL()
> > ---
> >  arch/riscv/include/asm/tlbflush.h | 2 ++
> >  arch/riscv/mm/context.c           | 2 +-
> >  arch/riscv/mm/tlbflush.c          | 2 +-
> >  3 files changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/riscv/include/asm/tlbflush.h b/arch/riscv/include/asm/tlbflush.h
> > index 907b9efd39a8..597d6d8aec28 100644
> > --- a/arch/riscv/include/asm/tlbflush.h
> > +++ b/arch/riscv/include/asm/tlbflush.h
> > @@ -12,6 +12,8 @@
> >  #include <asm/errata_list.h>
> >
> >  #ifdef CONFIG_MMU
> > +extern unsigned long asid_mask;
> > +
> >  static inline void local_flush_tlb_all(void)
> >  {
> >         __asm__ __volatile__ ("sfence.vma" : : : "memory");
> > diff --git a/arch/riscv/mm/context.c b/arch/riscv/mm/context.c
> > index 80ce9caba8d2..6d1aeb063e81 100644
> > --- a/arch/riscv/mm/context.c
> > +++ b/arch/riscv/mm/context.c
> > @@ -22,7 +22,7 @@ DEFINE_STATIC_KEY_FALSE(use_asid_allocator);
> >
> >  static unsigned long asid_bits;
> >  static unsigned long num_asids;
> > -static unsigned long asid_mask;
> > +unsigned long asid_mask;
> >
> >  static atomic_long_t current_version;
> >
> > diff --git a/arch/riscv/mm/tlbflush.c b/arch/riscv/mm/tlbflush.c
> > index ce7dfc81bb3f..ba4c27187c95 100644
> > --- a/arch/riscv/mm/tlbflush.c
> > +++ b/arch/riscv/mm/tlbflush.c
> > @@ -27,7 +27,7 @@ static void __sbi_tlb_flush_range(struct mm_struct *mm, unsigned long start,
> >         /* check if the tlbflush needs to be sent to other CPUs */
> >         broadcast = cpumask_any_but(cmask, cpuid) < nr_cpu_ids;
> >         if (static_branch_unlikely(&use_asid_allocator)) {
> > -               unsigned long asid = atomic_long_read(&mm->context.id);
> > +               unsigned long asid = atomic_long_read(&mm->context.id) & asid_mask;
> >
> >                 /*
> >                  * TLB will be immediately flushed on harts concurrently
> > --
> > 2.34.1
> >

  reply	other threads:[~2023-03-14  7:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13  3:49 [PATCH v2] riscv: mm: Fix incorrect ASID argument when flushing TLB Dylan Jhong
2023-03-13  5:58 ` Sergey Matyukevich
2023-03-14  2:22 ` Zong Li
2023-03-14  7:27   ` Dylan Jhong [this message]
2023-03-21  2:42     ` Dylan Jhong
2023-03-22  5:45       ` Palmer Dabbelt
2023-03-23 20:47         ` Palmer Dabbelt
2023-03-23 21:00 ` patchwork-bot+linux-riscv

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=ZBAh4EY2RNLryzEW@APC323 \
    --to=dylan@andestech.com \
    --cc=alistair.francis@wdc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=guoren@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=peterlin@andestech.com \
    --cc=sergey.matyukevich@syntacore.com \
    --cc=tim609@andestech.com \
    --cc=x5710999x@gmail.com \
    --cc=ycliang@andestech.com \
    --cc=zongbox@gmail.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