From: SeongJae Park <sj@kernel.org>
To: Benjamin Berg <benjamin@sipsolutions.net>
Cc: SeongJae Park <sj@kernel.org>,
linux-um@lists.infradead.org,
Benjamin Berg <benjamin.berg@intel.com>
Subject: Re: [PATCH] um: add back support for FXSAVE registers
Date: Tue, 7 Jan 2025 13:07:58 -0800 [thread overview]
Message-ID: <20250107210758.80762-1-sj@kernel.org> (raw)
In-Reply-To: <20241204074827.1582917-1-benjamin@sipsolutions.net>
Hello,
On Wed, 4 Dec 2024 08:48:27 +0100 Benjamin Berg <benjamin@sipsolutions.net> wrote:
> From: Benjamin Berg <benjamin.berg@intel.com>
>
> It was reported that qemu may not enable the XSTATE CPU extension, which
> is a requirement after commit 3f17fed21491 ("um: switch to regset API
> and depend on XSTATE"). Add a fallback to use FXSAVE (FP registers on
> x86_64 and XFP on i386) which is just a shorter version of the same
> data. The only difference is that the XSTATE magic should not be set in
> the signal frame.
>
> Note that this still drops support for the older i386 FP register layout
> as supporting this would require more backward compatibility to build a
> correct signal frame.
>
> Fixes: 3f17fed21491 ("um: switch to regset API and depend on XSTATE")
> Reported-by: SeongJae Park <sj@kernel.org>
> Closes: https://lore.kernel.org/r/20241203070218.240797-1-sj@kernel.org
> Tested-by: SeongJae Park <sj@kernel.org>
> Signed-off-by: Benjamin Berg <benjamin.berg@intel.com>
Seems this patch is not yet merged into uml/next or uml/fixes. May I ask the
timeline or blockers for this patch?
Thanks,
SJ
[...]
next prev parent reply other threads:[~2025-01-07 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 7:48 [PATCH] um: add back support for FXSAVE registers Benjamin Berg
2025-01-07 21:07 ` SeongJae Park [this message]
2025-02-11 7:04 ` SeongJae Park
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=20250107210758.80762-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=benjamin.berg@intel.com \
--cc=benjamin@sipsolutions.net \
--cc=linux-um@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.