lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 17 Nov 2022 10:02:20 -0800 From: Isaku Yamahata <isaku.yamahata@...il.com> To: "Huang, Kai" <kai.huang@...el.com> Cc: "kvm@...r.kernel.org" <kvm@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Yamahata, Isaku" <isaku.yamahata@...el.com>, "pbonzini@...hat.com" <pbonzini@...hat.com>, "Shahar, Sagi" <sagis@...gle.com>, "Aktas, Erdem" <erdemaktas@...gle.com>, "isaku.yamahata@...il.com" <isaku.yamahata@...il.com>, "dmatlack@...gle.com" <dmatlack@...gle.com>, "Christopherson,, Sean" <seanjc@...gle.com> Subject: Re: [PATCH v10 034/108] KVM: x86/mmu: Add Suppress VE bit to shadow_mmio_{value, mask} On Wed, Nov 09, 2022 at 11:48:30AM +0000, "Huang, Kai" <kai.huang@...el.com> wrote: > On Sat, 2022-10-29 at 23:22 -0700, isaku.yamahata@...el.com wrote: > > From: Isaku Yamahata <isaku.yamahata@...el.com> > > > > Because TDX will need shadow_mmio_mask to be VMX_SUPPRESS_VE | RWX > > shadow_mmio_value to be 0, make VMX EPT case use same value for TDX > > shadow_mmio_mask. > > > > TDX need to use different mmio_mask/value doesn't mean they need to be changed > for VMX guest. I think the true purpose here is to still be able to use a > global shadow_mmio_mask for both TDX and VMX guests. So please explicitly call > out. That's right. With this change, per-VM shadow_mmio_{value, mask} can be avoided. The common value can be used for both VMX and TDX. -- Isaku Yamahata <isaku.yamahata@...il.com>
Powered by blists - more mailing lists