From: Conor Dooley <conor@kernel.org>
To: Jinyu Tang <tjytimi@163.com>
Cc: paul.walmsley@sifive.com, ajones@ventanamicro.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
conor.dooley@microchip.com, anup@brainfault.org,
alexandre.ghiti@canonical.com, guoren@kernel.org,
akpm@linux-foundation.org, heiko@sntech.de,
tongtiangen@huawei.com, sunnanyong@huawei.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
falcon@tinylab.org
Subject: Re: [PATCH v2] riscv: support update_mmu_tlb() for riscv
Date: Fri, 23 Sep 2022 22:45:40 +0100 [thread overview]
Message-ID: <Yy4pBHm1fZ3oM/m5@spud> (raw)
In-Reply-To: <20220918055940.24726-1-tjytimi@163.com>
Hey Jinyu,
Firstly, the "for riscv" in the title is redundant and can be dropped.
On Sun, Sep 18, 2022 at 01:59:40PM +0800, Jinyu Tang wrote:
> Add macro definition to support updata_mmu_tlb() for riscv,
^
s/updata/update/
> this function is from commit:7df676974359 ("mm/memory.c:Update
> local TLB if PTE entry exists").
So, and this just may be may lack of knowledge showing, but I don't
really understand _why_ we need this change. Your commit message should
explain why you are making the change rather than just repeating what
you are doing since that is obvious from the diff.
Only MIPS seems to have this define, so your commit message needs to
explain what it is about RISC-V that means we need it when all bar one
arch does not.
Thanks,
Conor.
>
> Signed-off-by: Jinyu Tang <tjytimi@163.com>
> Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
> ---
> v1 -> v2:
>
> Change the format with the help from Andrew Jones and Conor Dooley.
>
> arch/riscv/include/asm/pgtable.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/riscv/include/asm/pgtable.h b/arch/riscv/include/asm/pgtable.h
> index 7ec936910a96..c61ae83aadee 100644
> --- a/arch/riscv/include/asm/pgtable.h
> +++ b/arch/riscv/include/asm/pgtable.h
> @@ -418,6 +418,9 @@ static inline void update_mmu_cache(struct vm_area_struct *vma,
> local_flush_tlb_page(address);
> }
>
> +#define __HAVE_ARCH_UPDATE_MMU_TLB
> +#define update_mmu_tlb update_mmu_cache
> +
> static inline void update_mmu_cache_pmd(struct vm_area_struct *vma,
> unsigned long address, pmd_t *pmdp)
> {
> --
> 2.30.2
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-09-23 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 5:59 [PATCH v2] riscv: support update_mmu_tlb() for riscv Jinyu Tang
2022-09-23 21:45 ` Conor Dooley [this message]
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=Yy4pBHm1fZ3oM/m5@spud \
--to=conor@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=akpm@linux-foundation.org \
--cc=alexandre.ghiti@canonical.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=falcon@tinylab.org \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=sunnanyong@huawei.com \
--cc=tjytimi@163.com \
--cc=tongtiangen@huawei.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