From: Sean Christopherson <seanjc@google.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Liu, Jing2" <jing2.liu@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Jing Liu <jing2.liu@linux.intel.com>,
"Cooper, Andrew" <andrew.cooper3@citrix.com>,
"Bae, Chang Seok" <chang.seok.bae@intel.com>
Subject: Re: Thoughts of AMX KVM support based on latest kernel
Date: Tue, 16 Nov 2021 20:12:41 +0000 [thread overview]
Message-ID: <YZQQuQDWPhcJG6pM@google.com> (raw)
In-Reply-To: <87ee7g53rp.ffs@tglx>
On Tue, Nov 16, 2021, Thomas Gleixner wrote:
> Now you could argue that the interrupt/softirq XSAVES should also read
> the XFD MSR and save it in guest_fpstate.xfd. Same in schedule()
> and kvm_put_guest_fpu(), i.e:
>
> XSAVES
> if (fpstate->is_guest) {
> rdmsrl(XFD, xfd);
> fpstate->xfd = xfd;
> __this_cpu_write(..., xfd);
> }
>
> We can do that, but I'm unhappy about this conditional in schedule(). So
> I was asking for doing a simple KVM only solution first:
Ah, the schedule() conditional is the part I was missing. Thanks!
next prev parent reply other threads:[~2021-11-16 20:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 13:01 Thoughts of AMX KVM support based on latest kernel Liu, Jing2
2021-11-16 12:18 ` Thomas Gleixner
2021-11-16 16:05 ` Sean Christopherson
2021-11-16 18:55 ` Thomas Gleixner
2021-11-16 19:49 ` Paolo Bonzini
2021-11-16 20:14 ` Sean Christopherson
2021-11-16 20:36 ` Thomas Gleixner
2021-11-16 22:11 ` Nakajima, Jun
2021-11-17 7:39 ` Paolo Bonzini
2021-11-16 20:12 ` Sean Christopherson [this message]
2021-11-16 23:35 ` Thomas Gleixner
2021-11-16 19:20 ` Thomas Gleixner
2021-11-17 4:52 ` Nakajima, Jun
2021-11-17 7:31 ` Paolo Bonzini
2021-11-17 10:15 ` Tian, Kevin
2021-11-17 12:24 ` Thomas Gleixner
2021-11-17 12:53 ` Paolo Bonzini
2021-11-18 23:17 ` Nakajima, Jun
2021-11-19 10:13 ` Thomas Gleixner
2021-11-19 15:41 ` Nakajima, Jun
2021-12-08 0:50 ` Rewording of Setting IA32_XFD[18] (Re: Thoughts of AMX KVM support based on latest kernel) Nakajima, Jun
2021-12-08 13:57 ` Paolo Bonzini
2021-12-10 21:53 ` Thomas Gleixner
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=YZQQuQDWPhcJG6pM@google.com \
--to=seanjc@google.com \
--cc=andrew.cooper3@citrix.com \
--cc=arjan@linux.intel.com \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=jing2.liu@intel.com \
--cc=jing2.liu@linux.intel.com \
--cc=jun.nakajima@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).