From: Russell King (Oracle) <linux@armlinux.org.uk>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH V3 09/30] arm/mm: Enable ARCH_HAS_VM_GET_PAGE_PROT
Date: Mon, 28 Feb 2022 10:57:18 +0000 [thread overview]
Message-ID: <Yhyqjo/4bozJB6j5@shell.armlinux.org.uk> (raw)
In-Reply-To: <1646045273-9343-10-git-send-email-anshuman.khandual@arm.com>
On Mon, Feb 28, 2022 at 04:17:32PM +0530, Anshuman Khandual wrote:
> This defines and exports a platform specific custom vm_get_page_prot() via
> subscribing ARCH_HAS_VM_GET_PAGE_PROT. Subsequently all __SXXX and __PXXX
> macros can be dropped which are no longer needed.
What I would really like to know is why having to run _code_ to work out
what the page protections need to be is better than looking it up in a
table.
Not only is this more expensive in terms of CPU cycles, it also brings
additional code size with it.
I'm struggling to see what the benefit is.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2022-02-28 10:57 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 10:47 [OpenRISC] [PATCH V3 00/30] mm/mmap: Drop protection_map[] and platform's __SXXX/__PXXX requirements Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 01/30] mm/debug_vm_pgtable: Drop protection_map[] usage Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 02/30] mm/mmap: Clarify protection_map[] indices Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 03/30] mm/mmap: Add new config ARCH_HAS_VM_GET_PAGE_PROT Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 04/30] powerpc/mm: Enable ARCH_HAS_VM_GET_PAGE_PROT Anshuman Khandual
2022-03-02 5:23 ` Michael Ellerman
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 05/30] arm64/mm: " Anshuman Khandual
2022-03-03 15:28 ` Catalin Marinas
2022-03-09 11:31 ` Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 06/30] sparc/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 07/30] mips/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 08/30] m68k/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 09/30] arm/mm: " Anshuman Khandual
2022-02-28 10:57 ` Russell King [this message]
2022-02-28 13:49 ` Geert Uytterhoeven
2022-03-01 0:00 ` Anshuman Khandual
2022-03-01 0:31 ` Russell King
2022-03-01 8:16 ` Christophe Leroy
2022-03-02 3:22 ` Anshuman Khandual
2022-03-02 7:05 ` Christophe Leroy
2022-03-02 9:51 ` Anshuman Khandual
2022-03-02 10:05 ` Geert Uytterhoeven
2022-03-02 11:06 ` Anshuman Khandual
2022-03-02 11:14 ` Geert Uytterhoeven
2022-03-09 11:33 ` Anshuman Khandual
2022-03-02 11:19 ` Russell King
2022-03-02 3:15 ` Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 10/30] x86/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 11/30] mm/mmap: Drop protection_map[] Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 12/30] mm/mmap: Drop arch_filter_pgprot() Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 13/30] mm/mmap: Drop arch_vm_get_page_pgprot() Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 14/30] s390/mm: Enable ARCH_HAS_VM_GET_PAGE_PROT Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 15/30] riscv/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 16/30] alpha/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 17/30] sh/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 18/30] arc/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 19/30] csky/mm: " Anshuman Khandual
2022-03-01 14:00 ` Guo Ren
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 20/30] xtensa/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 21/30] parisc/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 22/30] openrisc/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 23/30] um/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 24/30] microblaze/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 25/30] nios2/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 26/30] hexagon/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 27/30] nds32/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 28/30] ia64/mm: " Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 29/30] mm/mmap: Drop generic vm_get_page_prot() Anshuman Khandual
2022-02-28 10:47 ` [OpenRISC] [PATCH V3 30/30] mm/mmap: Drop ARCH_HAS_VM_GET_PAGE_PROT 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=Yhyqjo/4bozJB6j5@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=openrisc@lists.librecores.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;
as well as URLs for NNTP newsgroup(s).