[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <SA1PR11MB67346BBAB5E81039FBCDB692A8712@SA1PR11MB6734.namprd11.prod.outlook.com>
Date: Thu, 18 Jan 2024 05:16:08 +0000
From: "Li, Xin3" <xin3.li@...el.com>
To: "Huang, Kai" <kai.huang@...el.com>, "kvm@...r.kernel.org"
<kvm@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
CC: "Yang, Weijiang" <weijiang.yang@...el.com>, "seanjc@...gle.com"
<seanjc@...gle.com>, "x86@...nel.org" <x86@...nel.org>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>, "hpa@...or.com"
<hpa@...or.com>, "mingo@...hat.com" <mingo@...hat.com>, "tglx@...utronix.de"
<tglx@...utronix.de>, "bp@...en8.de" <bp@...en8.de>, "pbonzini@...hat.com"
<pbonzini@...hat.com>
Subject: RE: [PATCH v4 1/2] KVM: VMX: Cleanup VMX basic information defines
and usages
> On Fri, 2024-01-12 at 01:34 -0800, Xin Li wrote:
> > Define VMX basic information fields with BIT_ULL()/GENMASK_ULL(), and
> > replace hardcoded VMX basic numbers with these field macros.
> >
> > Per Sean's ask, save the full/raw value of MSR_IA32_VMX_BASIC in the
> > global vmcs_config as type u64 to get rid of the hi/lo crud, and then
> > use VMX_BASIC helpers to extract info as needed.
> >
> > Tested-by: Shan Kang <shan.kang@...el.com>
> > Signed-off-by: Xin Li <xin3.li@...el.com>
> > ---
> >
>
> [...]
>
> > +/* x86 memory types, explicitly used in VMX only */
> > +#define MEM_TYPE_WB 0x6ULL
> > +#define MEM_TYPE_UC 0x0ULL
> > +
>
> [...]
>
> > -#define VMX_EPTP_MT_WB 0x6ull
> > -#define VMX_EPTP_MT_UC 0x0ull
>
> Could you also put some words to the changelog to justify your change around
> memory type macros?
NP.
Powered by blists - more mailing lists