From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: Andrei Vagin <avagin@google.com>,
Thomas Gleixner <tglx@kernel.org>,
"Ingo Molnar" <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>
Cc: <linux-kernel@vger.kernel.org>, <criu@lists.linux.dev>,
Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
Alexander Mikhalitsyn <alexander@mihalicyn.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v5 0/7] x86/fpu: Restore and reinforce signal frame portability
Date: Mon, 14 Sep 2026 10:05:20 -0700 [thread overview]
Message-ID: <ac6c35ff-79fa-4ac8-bf7d-b665424360d0@intel.com> (raw)
In-Reply-To: <20260908043427.1842515-1-avagin@google.com>
On 9/7/2026 9:34 PM, Andrei Vagin wrote:
>
> v5: Address Chang's comments:
> - Documentation:
> - Expanded Documentation/arch/x86/xstate.rst with a dedicated
> section describing struct _fpx_sw_bytes, 32-bit vs 64-bit frame
> layout differences, and architectural portability constraints.
> - Trimmed the comment in <uapi/asm/sigcontext.h> and added a
> reference to xstate.rst.
> - x86/fpu core:
> - Renamed the 32-bit helper to restore_from_ia32_fxstate() and
> inlined the remaining native path directly into
> fpu__restore_sig().
> - Selftests:
> - Consolidated the shrunk-frame and insufficient-size test cases.
Thanks for the update! I've provided my tags for the remaining patches
in this series. Hopefully, this can move forward (perhaps with some
further shaping) toward integration.
Chang
prev parent reply other threads:[~2026-09-14 17:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 4:34 Andrei Vagin
2026-09-08 4:34 ` [PATCH 1/7] x86/fpu: Document signal frame layout and portability Andrei Vagin
2026-09-16 4:53 ` Borislav Petkov
2026-09-08 4:34 ` [PATCH 2/7] x86/fpu: Clean up and rename variables in signal frame handling Andrei Vagin
2026-09-08 4:34 ` [PATCH 3/7] x86/fpu: Extract restore_from_ia32_fxstate() and clean up fpu__restore_sig() Andrei Vagin
2026-09-14 17:00 ` Chang S. Bae
2026-09-08 4:34 ` [PATCH 4/7] x86/fpu: Document reasoning of FX-only fallback Andrei Vagin
2026-09-08 4:34 ` [PATCH 5/7] x86/fpu: Fix potential underflow in xstate_calculate_size() Andrei Vagin
2026-09-08 4:34 ` [PATCH 6/7] x86/fpu: Pre-fault only required size of xstate buffer Andrei Vagin
2026-09-08 4:34 ` [PATCH 7/7] selftests/x86: Add tests for signal frame FPU portability Andrei Vagin
2026-09-14 17:03 ` Chang S. Bae
2026-09-14 17:05 ` Chang S. Bae [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=ac6c35ff-79fa-4ac8-bf7d-b665424360d0@intel.com \
--to=chang.seok.bae@intel.com \
--cc=alexander@mihalicyn.com \
--cc=avagin@google.com \
--cc=bp@alien8.de \
--cc=criu@lists.linux.dev \
--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®