From: Peter Zijlstra <peterz@infradead.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: x86@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Borislav Petkov <bp@alien8.de>,
Brendan Higgins <brendan.higgins@linux.dev>,
Daniel Gomez <da.gomez@samsung.com>,
Daniel Thompson <danielt@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Gow <davidgow@google.com>,
Douglas Anderson <dianders@chromium.org>,
Ingo Molnar <mingo@redhat.com>,
Jason Wessel <jason.wessel@windriver.com>,
Jiri Kosina <jikos@kernel.org>,
Joe Lawrence <joe.lawrence@redhat.com>,
Johannes Berg <johannes@sipsolutions.net>,
Josh Poimboeuf <jpoimboe@kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Miroslav Benes <mbenes@suse.cz>, "H. Peter Anvin" <hpa@zytor.com>,
Petr Mladek <pmladek@suse.com>, Petr Pavlu <petr.pavlu@suse.com>,
Rae Moar <rmoar@google.com>, Richard Weinberger <richard@nod.at>,
Sami Tolvanen <samitolvanen@google.com>,
Shuah Khan <shuah@kernel.org>, Song Liu <song@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
kgdb-bugreport@lists.sourceforge.net, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, linux-modules@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-um@lists.infradead.org,
live-patching@vger.kernel.org
Subject: Re: [PATCH v2 00/10] x86/module: rework ROX cache to avoid writable copy
Date: Tue, 21 Jan 2025 13:36:46 +0100 [thread overview]
Message-ID: <20250121123646.GC7145@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250121095739.986006-1-rppt@kernel.org>
On Tue, Jan 21, 2025 at 11:57:29AM +0200, Mike Rapoport wrote:
> Kirill A. Shutemov (1):
> x86/mm/pat: restore large ROX pages after fragmentation
The duplication between pmd and pud collapse is a bit annoying, but so
be it.
> Mike Rapoport (Microsoft) (9):
> x86/mm/pat: cpa-test: fix length for CPA_ARRAY test
> x86/mm/pat: drop duplicate variable in cpa_flush()
> execmem: don't remove ROX cache from the direct map
> execmem: add API for temporal remapping as RW and restoring ROX afterwards
> module: introduce MODULE_STATE_GONE
> module: switch to execmem API for remapping as RW and restoring ROX
> Revert "x86/module: prepare module loading for ROX allocations of text"
> module: drop unused module_writable_address()
> x86: re-enable EXECMEM_ROX support
All these look good on a first reading, let me go build and test the
various options.
next prev parent reply other threads:[~2025-01-21 12:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 9:57 Mike Rapoport
2025-01-21 9:57 ` [PATCH v2 01/10] x86/mm/pat: cpa-test: fix length for CPA_ARRAY test Mike Rapoport
2025-01-21 9:57 ` [PATCH v2 02/10] x86/mm/pat: drop duplicate variable in cpa_flush() Mike Rapoport
2025-01-21 9:57 ` [PATCH v2 03/10] x86/mm/pat: restore large ROX pages after fragmentation Mike Rapoport
2025-01-21 9:57 ` [PATCH v2 04/10] execmem: don't remove ROX cache from the direct map Mike Rapoport
2025-01-21 9:57 ` [PATCH v2 05/10] execmem: add API for temporal remapping as RW and restoring ROX afterwards Mike Rapoport
2025-01-21 9:57 ` [PATCH v2 06/10] module: introduce MODULE_STATE_GONE Mike Rapoport
2025-01-23 14:16 ` Petr Pavlu
2025-01-24 11:06 ` Mike Rapoport
2025-01-24 12:59 ` Petr Pavlu
2025-01-24 13:34 ` Petr Mladek
2025-01-21 9:57 ` [PATCH v2 07/10] module: switch to execmem API for remapping as RW and restoring ROX Mike Rapoport
2025-01-21 9:57 ` [PATCH v2 08/10] Revert "x86/module: prepare module loading for ROX allocations of text" Mike Rapoport
2025-01-21 9:57 ` [PATCH v2 09/10] module: drop unused module_writable_address() Mike Rapoport
2025-01-21 9:57 ` [PATCH v2 10/10] x86: re-enable EXECMEM_ROX support Mike Rapoport
2025-01-21 12:36 ` Peter Zijlstra [this message]
2025-01-22 9:51 ` [PATCH v2 00/10] x86/module: rework ROX cache to avoid writable copy Peter Zijlstra
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=20250121123646.GC7145@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=bp@alien8.de \
--cc=brendan.higgins@linux.dev \
--cc=da.gomez@samsung.com \
--cc=danielt@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=davidgow@google.com \
--cc=dianders@chromium.org \
--cc=hpa@zytor.com \
--cc=jason.wessel@windriver.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=jpoimboe@kernel.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=kirill.shutemov@linux.intel.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=live-patching@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=petr.pavlu@suse.com \
--cc=pmladek@suse.com \
--cc=richard@nod.at \
--cc=rmoar@google.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=samitolvanen@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--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