[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y3O7UYWfOLfJkwM/@zn.tnic>
Date: Tue, 15 Nov 2022 17:16:17 +0100
From: Borislav Petkov <bp@...en8.de>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Xiaoyao Li <xiaoyao.li@...el.com>,
Jiaxi Chen <jiaxi.chen@...ux.intel.com>, kvm@...r.kernel.org,
tglx@...utronix.de, mingo@...hat.com, dave.hansen@...ux.intel.com,
x86@...nel.org, hpa@...or.com, pbonzini@...hat.com,
ndesaulniers@...gle.com, alexandre.belloni@...tlin.com,
peterz@...radead.org, jpoimboe@...nel.org,
chang.seok.bae@...el.com, pawan.kumar.gupta@...ux.intel.com,
babu.moger@....com, jmattson@...gle.com, sandipan.das@....com,
tony.luck@...el.com, sathyanarayanan.kuppuswamy@...ux.intel.com,
fenghua.yu@...el.com, keescook@...omium.org, nathan@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/7] x86: KVM: Move existing x86 CPUID leaf
[CPUID_7_1_EAX] to kvm-only leaf
On Tue, Nov 15, 2022 at 03:29:45PM +0000, Sean Christopherson wrote:
> Heh, are any of the bits you believe Intel will add publicly documented? :-)
>
> LAM could be scattered, but if more bits are expected that's probably a waste of
> time and effort.
I'm being told the bigger part of that word is going to be used for
either kernel or KVM bits so we might as well use it the "normal" way
instead of doing KVM-only or scattered bits after all.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists