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: Tue, 29 Jan 2019 09:47:04 -0800 From: Jim Mattson <jmattson@...gle.com> To: Yang Weijiang <weijiang.yang@...el.com> Cc: Paolo Bonzini <pbonzini@...hat.com>, Radim Krčmář <rkrcmar@...hat.com>, Sean Christopherson <sean.j.christopherson@...el.com>, LKML <linux-kernel@...r.kernel.org>, kvm list <kvm@...r.kernel.org>, "Michael S. Tsirkin" <mst@...hat.com>, yu-cheng.yu@...el.com, yi.z.zhang@...el.com, hjl.tools@...il.com, Zhang Yi Z <yi.z.zhang@...ux.intel.com> Subject: Re: [PATCH v2 1/7] KVM:VMX: Define CET VMCS fields and bits On Wed, Jan 23, 2019 at 6:06 AM Yang Weijiang <weijiang.yang@...el.com> wrote: > Note: Although these VMCS fields are 64-bit, they don't have high fields. This statement directly contradicts the SDM, volume 3, appendix B.2: "A value of 1 in bits 14:13 of an encoding indicates a 64-bit field. There are 64-bit fields only for controls and for guest state. As noted in Section 24.11.2, every 64-bit field has two encodings, which differ on bit 0, the access type. Thus, each such field has an even encoding for full access and an odd encoding for high access."
Powered by blists - more mailing lists