Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Alex Ghiti <alex@ghiti.fr>, Palmer Dabbelt <palmer@dabbelt.com>,
	<linux-riscv@lists.infradead.org>
Cc: <palmerdabbelt@google.com>, <paul.walmsley@sifive.com>,
	<aou@eecs.berkeley.edu>
Subject: Re: [PATCH] riscv: mm: Enable PMD split page table lock for RV64
Date: Fri, 6 Aug 2021 00:24:16 +0800	[thread overview]
Message-ID: <ef07bed0-8f7b-e1d7-69cb-62da120ee52f@huawei.com> (raw)
In-Reply-To: <8bb6c662-afbb-feea-dadb-9d2ea49ded5b@ghiti.fr>


On 2021/8/5 19:51, Alex Ghiti wrote:
> Hi Kefeng,
>
> On 30/07/2021 15:11, Kefeng Wang wrote:
>> After commit 1355c31eeb7e ("asm-generic: pgalloc: provide generic
>> pmd_alloc_one() and pmd_free_one()"), it is easy to enable
>> ARCH_ENABLE_SPLIT_PMD_PTLOCK for RV64.
>>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>>   arch/riscv/Kconfig   | 1 +
>>   arch/riscv/mm/init.c | 3 ++-
>>   2 files changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
>> index 8fcceb8eda07..c3e456fc7108 100644
>> --- a/arch/riscv/Kconfig
>> +++ b/arch/riscv/Kconfig
>> @@ -12,6 +12,7 @@ config 32BIT
>>     config RISCV
>>       def_bool y
>> +    select ARCH_ENABLE_SPLIT_PMD_PTLOCK if PGTABLE_LEVELS > 2
>>       select ARCH_CLOCKSOURCE_INIT
>>       select ARCH_SUPPORTS_ATOMIC_RMW
>>       select ARCH_SUPPORTS_DEBUG_PAGEALLOC if MMU
>> diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
>> index e547e53cddd2..ce12905a0224 100644
>> --- a/arch/riscv/mm/init.c
>> +++ b/arch/riscv/mm/init.c
>> @@ -361,7 +361,8 @@ static phys_addr_t __init 
>> alloc_pmd_late(uintptr_t va)
>>       unsigned long vaddr;
>>         vaddr = __get_free_page(GFP_KERNEL);
>> -    BUG_ON(!vaddr);
>> +    BUG_ON(!vaddr || !pgtable_pmd_page_ctor(virt_to_page(vaddr)));
>> +
>>       return __pa(vaddr);
>>   }
>>
>
> I took the time to check how the page table lock works, and indeed, 
> the commit you mention makes it easy to enable this feature since the 
> initialization of the lock for the general case is done there and your 
> patch seems correct as this is the only place we allocate a PMD page, 
> and the PTE page allocation already calls pgtable_pte_page_ctor.
>
> Maybe your commit message would need some of the explanation I gave 
> above, or something similar, but this is up to you.
There is a  Documentation/vm/split_page_table_lock.rst doc about this 
feature, we could learn more from changelog with the feature introduced.
>
> You can add:
>
> Reviewed-by: Alexandre Ghiti <alex@ghiti.fr>
Thanks, Alex ;)
>
> Thanks,
>
> Alex
> .
>

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2021-08-05 16:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 13:11 [PATCH] riscv: mm: Enable PMD split page table lock for RV64 Kefeng Wang
2021-08-05 11:51 ` Alex Ghiti
2021-08-05 16:24   ` Kefeng Wang [this message]
2021-08-27 15:18 ` Kefeng Wang

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=ef07bed0-8f7b-e1d7-69cb-62da120ee52f@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=palmerdabbelt@google.com \
    --cc=paul.walmsley@sifive.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