[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <acf225f2-5783-8a2d-a060-e58aad28e8de@linux.intel.com>
Date: Thu, 25 Feb 2021 10:02:26 +0800
From: "Liu, Jing2" <jing2.liu@...ux.intel.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Dave Hansen <dave.hansen@...el.com>, pbonzini@...hat.com,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] kvm: x86: Revise guest_fpu xcomp_bv field
On 2/25/2021 4:40 AM, Sean Christopherson wrote:
> 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!
Sure, let me update v2.
BRs,
Jing
Powered by blists - more mailing lists