From: Sean Christopherson <seanjc@google.com>
To: "Liu, Jing2" <jing2.liu@linux.intel.com>
Cc: Dave Hansen <dave.hansen@intel.com>,
pbonzini@redhat.com, Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] kvm: x86: Revise guest_fpu xcomp_bv field
Date: Wed, 24 Feb 2021 12:40:17 -0800 [thread overview]
Message-ID: <YDa5saYSU+Zrr8e+@google.com> (raw)
In-Reply-To: <9d23ae5b-9b85-88d7-a2d7-44fd75a068b9@linux.intel.com>
On Tue, Feb 23, 2021, Liu, Jing2 wrote:
> XCOMP_BV[63] field indicates that the save area is in the
> compacted format and XCOMP_BV[62:0] indicates the states that
> have space allocated in the save area, including both XCR0
> and XSS bits enable by the host kernel. Use xfeatures_mask_all
> for calculating xcomp_bv and reuse XCOMP_BV_COMPACTED_FORMAT
> defined by kernel.
Works for me, just please wrap at ~73-75 chars, not ~64.
Thanks!
next prev parent reply other threads:[~2021-02-24 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 16:16 [PATCH v1] kvm: x86: Revise guest_fpu xcomp_bv field Jing Liu
2021-02-08 15:23 ` Dave Hansen
2021-02-08 17:24 ` Sean Christopherson
2021-02-22 3:21 ` Liu, Jing2
2021-02-22 16:06 ` Sean Christopherson
2021-02-23 3:06 ` Liu, Jing2
2021-02-24 20:40 ` Sean Christopherson [this message]
2021-02-25 2:02 ` Liu, Jing2
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=YDa5saYSU+Zrr8e+@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=jing2.liu@linux.intel.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--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 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.