[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3afdb885-d2d9-c099-bc72-c813521b6b39@intel.com>
Date: Wed, 22 Dec 2021 06:52:01 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: "Nakajima, Jun" <jun.nakajima@...el.com>,
Paolo Bonzini <pbonzini@...hat.com>
Cc: "Zhong, Yang" <yang.zhong@...el.com>,
"x86@...nel.org" <x86@...nel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"Christopherson,, Sean" <seanjc@...gle.com>,
"Tian, Kevin" <kevin.tian@...el.com>,
"jing2.liu@...ux.intel.com" <jing2.liu@...ux.intel.com>,
"Liu, Jing2" <jing2.liu@...el.com>
Subject: Re: State Component 18 and Palette 1 (Re: [PATCH 16/19] kvm: x86:
Introduce KVM_{G|S}ET_XSAVE2 ioctl)
On 12/20/21 9:54 AM, Nakajima, Jun wrote:
>> So, I hope that save state 18 will be frozen to 8k. In that case,
>> and if palette 1 is frozen to the same values as today,
>> implementing migration will not be a problem; it will be
>> essentially the same as SSE->AVX (horizontal extension of existing
>> registers) and/or AVX->AVX512 (both horizontal and vertical
>> extension).
>
> I would like to confirm that the state component 18 will remain 8KB
> and palette 1 will remain the same.
Is that an architectural statement that will soon be making its way into
the SDM?
Powered by blists - more mailing lists