From: patchwork-bot+linux-riscv@kernel.org
To: Mike Rapoport <rppt@kernel.org>
Cc: linux-riscv@lists.infradead.org, akpm@linux-foundation.org,
abarnas@google.com, aou@eecs.berkeley.edu,
agordeev@linux.ibm.com, alex@ghiti.fr, luto@kernel.org,
bp@alien8.de, brendan.jackman@linux.dev, catalin.marinas@arm.com,
borntraeger@linux.ibm.com, dave.hansen@linux.intel.com,
david@kernel.org, gerald.schaefer@linux.ibm.com,
hca@linux.ibm.com, chenhuacai@kernel.org, mingo@redhat.com,
lenb@kernel.org, palmer@dabbelt.com, pjw@kernel.org,
pavel@kernel.org, peterz@infradead.org, hpa@zytor.com,
rafael@kernel.org, ryan.roberts@arm.com, svens@linux.ibm.com,
tglx@kernel.org, urezki@gmail.com, gor@linux.ibm.com,
kernel@xen0n.name, will@kernel.org, x86@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-pm@vger.kernel.org, linux-s390@vger.kernel.org,
loongarch@lists.linux.dev
Subject: Re: [PATCH v3 0/6] arch, mm/execmem: resolve confusion about set_direct_map_valid_noflush()
Date: Sun, 01 Nov 2026 22:16:12 +0000 [thread overview]
Message-ID: <179357137254.2624073.6914916059318534007.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260903-execmem-set-vm-perms-v0-2-v3-0-949b64a9f755@kernel.org>
Hello:
This series was applied to riscv/linux.git (fixes)
by Andrew Morton <akpm@linux-foundation.org>:
On Thu, 03 Sep 2026 12:28:26 +0300 you wrote:
> Recent discussion about implementation of execmem's ROX caches on arm64
> revealed a confusion about how set_direct_map_valid_noflush()
> implemented on different architectures.
>
> On arm64 it sets or clears the PTE_VALID bit marking a PTE as present or
> not present.
>
> [...]
Here is the summary with links:
- [v3,1/6] set_memory: add number of pages parameter to set_direct_map APIs
https://git.kernel.org/riscv/c/be7dacb9c1d4
- [v3,2/6] mm/vmalloc: set area's page_order after allocation succeeds
https://git.kernel.org/riscv/c/40702f168a9e
- [v3,3/6] mm/vmalloc: constify vm parameter of get_vm_area_page_order()
https://git.kernel.org/riscv/c/1f73dfdeb9c2
- [v3,4/6] mm/vmalloc: make set_area_direct_map HUGE_VMAP friendly
https://git.kernel.org/riscv/c/86dc0280b807
- [v3,5/6] mm/execmem: use VM_FLUSH_RESET_PERMS for ROX cache allocations
https://git.kernel.org/riscv/c/4c4b2ed5b783
- [v3,6/6] Revert "arch: introduce set_direct_map_valid_noflush()"
https://git.kernel.org/riscv/c/0e774fdb2ed6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-01 22:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 9:28 Mike Rapoport (Microsoft)
2026-09-03 9:28 ` [PATCH v3 1/6] set_memory: add number of pages parameter to set_direct_map APIs Mike Rapoport (Microsoft)
2026-09-08 10:38 ` David Hildenbrand (Arm)
2026-09-08 11:20 ` Mike Rapoport
2026-09-08 11:53 ` David Hildenbrand (Arm)
2026-09-08 11:55 ` David Hildenbrand (Arm)
2026-09-17 18:11 ` Kevin Brodsky
2026-09-18 7:06 ` Mike Rapoport
2026-09-21 12:51 ` Kevin Brodsky
2026-09-03 9:28 ` [PATCH v3 2/6] mm/vmalloc: set area's page_order after allocation succeeds Mike Rapoport (Microsoft)
2026-09-03 10:23 ` Dev Jain
2026-09-03 9:28 ` [PATCH v3 3/6] mm/vmalloc: constify vm parameter of get_vm_area_page_order() Mike Rapoport (Microsoft)
2026-09-03 10:45 ` Dev Jain
2026-09-08 10:39 ` David Hildenbrand (Arm)
2026-09-17 18:11 ` Kevin Brodsky
2026-09-03 9:28 ` [PATCH v3 4/6] mm/vmalloc: make set_area_direct_map HUGE_VMAP friendly Mike Rapoport (Microsoft)
2026-09-08 9:59 ` Dev Jain
2026-09-08 10:41 ` David Hildenbrand (Arm)
2026-09-08 11:12 ` Mike Rapoport
2026-09-08 11:48 ` David Hildenbrand (Arm)
2026-09-08 14:05 ` Mike Rapoport
2026-09-17 18:12 ` Kevin Brodsky
2026-09-03 9:28 ` [PATCH v3 5/6] mm/execmem: use VM_FLUSH_RESET_PERMS for ROX cache allocations Mike Rapoport (Microsoft)
2026-09-17 18:13 ` Kevin Brodsky
2026-09-03 9:28 ` [PATCH v3 6/6] Revert "arch: introduce set_direct_map_valid_noflush()" Mike Rapoport (Microsoft)
2026-09-08 10:43 ` David Hildenbrand (Arm)
2026-09-17 18:15 ` Kevin Brodsky
2026-09-06 2:00 ` [PATCH v3 0/6] arch, mm/execmem: resolve confusion about set_direct_map_valid_noflush() Andrew Morton
2026-11-01 22:16 ` patchwork-bot+linux-riscv [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=179357137254.2624073.6914916059318534007.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=abarnas@google.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=brendan.jackman@linux.dev \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=kernel@xen0n.name \
--cc=lenb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pavel@kernel.org \
--cc=peterz@infradead.org \
--cc=pjw@kernel.org \
--cc=rafael@kernel.org \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=svens@linux.ibm.com \
--cc=tglx@kernel.org \
--cc=urezki@gmail.com \
--cc=will@kernel.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®