linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH 30/30] mm/mmap: Drop ARCH_HAS_VM_GET_PAGE_PROT
Date: Mon, 14 Feb 2022 15:29:01 +0530	[thread overview]
Message-ID: <b9308a0f-2877-8ef7-dcb8-301b91195d28@arm.com> (raw)
In-Reply-To: <CAMuHMdVqeyFhzJHLvE+erA4dO+eqpqzx8hVUj9LDk0iPwR1ByQ@mail.gmail.com>



On 2/14/22 3:18 PM, Geert Uytterhoeven wrote:
> Hi Anshuman,
> 
> On Mon, Feb 14, 2022 at 7:54 AM Anshuman Khandual
> <anshuman.khandual@arm.com> wrote:
>> All platforms now define their own vm_get_page_prot() and also there is no
>> generic version left to fallback on. Hence drop ARCH_HAS_GET_PAGE_PROT.
>>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: linux-mm@kvack.org
>> Cc: linux-kernel@vger.kernel.org
>> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
> 
> Thanks for your patch!
> 
>> -       select ARCH_HAS_VM_GET_PAGE_PROT
> 
> So before, all architectures selected ARCH_HAS_VM_GET_PAGE_PROT...

Right. ARCH_HAS_VM_GET_PAGE_PROT construct is required until all platforms
define their own vm_get_page_prot(). But once defined, this can be dropped
off, as a generic MM fallback is no longer available otherwise.

> 
>> --- a/mm/mmap.c
>> +++ b/mm/mmap.c
>> @@ -81,7 +81,6 @@ static void unmap_region(struct mm_struct *mm,
>>                 struct vm_area_struct *vma, struct vm_area_struct *prev,
>>                 unsigned long start, unsigned long end);
>>
>> -#ifndef CONFIG_ARCH_HAS_VM_GET_PAGE_PROT
> 
> ... hence the block below was not included.
> 
>>  /* description of effects of mapping type and prot in current implementation.
>>   * this is due to the limited x86 page protection hardware.  The expected
>>   * behavior is in parens:
>> @@ -102,8 +101,6 @@ static void unmap_region(struct mm_struct *mm,
>>   *                                                             w: (no) no
>>   *                                                             x: (yes) yes
>>   */
>> -#endif /* CONFIG_ARCH_HAS_VM_GET_PAGE_PROT */
>> -
> 
> So shouldn't the whole block be removed instead?

You are right, will remove the entire comment block here.

> Do I need more coffee??
> 
>>  static pgprot_t vm_pgprot_modify(pgprot_t oldprot, unsigned long vm_flags)
>>  {
>>         return pgprot_modify(oldprot, vm_get_page_prot(vm_flags));
> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                 -- Linus Torvalds
> 


  reply	other threads:[~2022-02-14  9:59 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14  2:30 [PATCH 00/30] mm/mmap: Drop protection_map[] and platform's __SXXX/__PXXX requirements Anshuman Khandual
2022-02-14  2:30 ` [PATCH 01/30] mm/debug_vm_pgtable: Drop protection_map[] usage Anshuman Khandual
2022-02-14  2:30 ` [PATCH 02/30] mm/mmap: Clarify protection_map[] indices Anshuman Khandual
2022-02-14  2:30 ` [PATCH 03/30] mm/mmap: Add new config ARCH_HAS_VM_GET_PAGE_PROT Anshuman Khandual
2022-02-14  2:30 ` [PATCH 04/30] powerpc/mm: Enable ARCH_HAS_VM_GET_PAGE_PROT Anshuman Khandual
2022-02-14  2:30 ` [PATCH 05/30] arm64/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 06/30] sparc/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 07/30] mips/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 08/30] m68k/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 09/30] arm/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 10/30] x86/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 11/30] mm/mmap: Drop protection_map[] Anshuman Khandual
2022-02-14  2:30 ` [PATCH 12/30] mm/mmap: Drop arch_filter_pgprot() Anshuman Khandual
2022-02-14  2:30 ` [PATCH 13/30] mm/mmap: Drop arch_vm_get_page_pgprot() Anshuman Khandual
2022-02-14  2:30 ` [PATCH 14/30] s390/mm: Enable ARCH_HAS_VM_GET_PAGE_PROT Anshuman Khandual
2022-02-14  2:30 ` [PATCH 15/30] riscv/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 16/30] alpha/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 17/30] sh/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 18/30] arc/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 19/30] csky/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 20/30] extensa/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 21/30] parisc/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 22/30] openrisc/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 23/30] um/mm: " Anshuman Khandual
2022-02-14  6:40   ` kernel test robot
2022-02-14 10:03     ` Anshuman Khandual
2022-02-14  2:30 ` [PATCH 24/30] microblaze/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 25/30] nios2/mm: " Anshuman Khandual
2022-02-25  1:31   ` Dinh Nguyen
2022-02-25  8:52     ` Anshuman Khandual
2022-02-25  8:54       ` Anshuman Khandual
2022-02-25 14:29       ` Dinh Nguyen
2022-02-25 14:38         ` Dinh Nguyen
2022-02-28  2:27           ` Anshuman Khandual
2022-02-14  2:30 ` [PATCH 26/30] hexagon/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 27/30] nds32/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 28/30] ia64/mm: " Anshuman Khandual
2022-02-14  2:30 ` [PATCH 29/30] mm/mmap: Drop generic vm_get_page_prot() Anshuman Khandual
2022-02-14  2:30 ` [PATCH 30/30] mm/mmap: Drop ARCH_HAS_VM_GET_PAGE_PROT Anshuman Khandual
2022-02-14  9:48   ` Geert Uytterhoeven
2022-02-14  9:59     ` Anshuman Khandual [this message]
2022-02-17  9:46 ` [PATCH 00/30] mm/mmap: Drop protection_map[] and platform's __SXXX/__PXXX requirements Anshuman Khandual

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=b9308a0f-2877-8ef7-dcb8-301b91195d28@arm.com \
    --to=anshuman.khandual@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=hch@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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