From: Thorsten Blum <blum@kernel.org>
To: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2] x86/fpu: Use vmemdup_user() in xstateregs_set()
Date: Tue, 6 Oct 2026 17:02:50 +0200 [thread overview]
Message-ID: <asUNmhyCFpNx5olr@kernel.org> (raw)
In-Reply-To: <20260917121441.214567-3-blum@kernel.org>
On Thu, Sep 17, 2026 at 02:14:41PM +0200, Thorsten Blum wrote:
> Replace the open-coded vmalloc() and copy_from_user() with
> vmemdup_user() to simplify xstateregs_set().
>
> vmemdup_user() returns an ERR_PTR() on failure, preserving the existing
> -ENOMEM and -EFAULT error codes. Since vmemdup_user() is backed by
> kvmalloc(), use kvfree() to free the buffer instead.
>
> Return early on error and drop the obsolete out label.
>
> Performance should be similar, and xstateregs_set() is not a hot path.
> Page alignment should not matter because the buffer is only used as a
> memcpy() source in copy_uabi_from_kernel_to_xstate().
>
> The allocation behavior differs because vmemdup_user() uses GFP_USER,
> which adds __GFP_HARDWALL and may affect cpuset allocations.
>
> tools/testing/selftests/x86/avx_64 passed on an Alder Lake CPU.
>
> Signed-off-by: Thorsten Blum <blum@kernel.org>
> ---
> Changes in v2:
> - Add performance analysis and selftest result to the changelog (Ingo)
> - v1: https://lore.kernel.org/r/20260720195534.70111-3-thorsten.blum@linux.dev/
> ---
> arch/x86/kernel/fpu/regset.c | 17 ++++++-----------
> 1 file changed, 6 insertions(+), 11 deletions(-)
Hi Ingo,
A gentle follow-up on this resend. The v2 changelog now includes the
analysis you asked for in the earlier thread, plus a successful x86
selftest result. Is anything else needed for this to be queued?
Thanks,
Thorsten
prev parent reply other threads:[~2026-10-06 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 12:14 Thorsten Blum
2026-10-06 15:02 ` Thorsten Blum [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=asUNmhyCFpNx5olr@kernel.org \
--to=blum@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@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®