From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Teddy Astie" <teddy.astie@vates.tech>,
"Roger Pau Monné" <roger@xenproject.org>,
"Andrew Mbugua" <andrewprecious388@gmail.com>
Subject: [PATCH 0/2] x86emul: XCR0 handling
Date: Thu, 20 Aug 2026 10:50:33 +0200 [thread overview]
Message-ID: <0c3cb1ae-4888-4319-a348-263f7913a7f2@suse.com> (raw)
Prompted by Andrew's report [1] I thought it may help if we accelerated two
of the patches I have pending as part of the (so far unposted) APX series.
We previously discussed latching some control register state once early, so
let's start with doing so for XCR0.
[1] https://lists.xen.org/archives/html/xen-devel/2026-08/msg01006.html
1: latch XCR0 early during decode
2: use latched XCR0 in x86emul_get_fpu()
Jan
next reply other threads:[~2026-08-20 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 8:50 Jan Beulich [this message]
2026-08-20 8:52 ` [PATCH 1/2] x86emul: latch XCR0 early during decode Jan Beulich
2026-08-20 8:52 ` [PATCH 2/2] x86emul: use latched XCR0 in x86emul_get_fpu() Jan Beulich
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=0c3cb1ae-4888-4319-a348-263f7913a7f2@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=andrewprecious388@gmail.com \
--cc=roger@xenproject.org \
--cc=teddy.astie@vates.tech \
--cc=xen-devel@lists.xenproject.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.