On 28/01/21 18:09, Sean Christopherson wrote:
On Thu, Jan 28, 2021, Paolo Bonzini wrote:
On 14/01/21 01:36, Sean Christopherson wrote:
Add a reverse-CPUID entry for the memory encryption word, 0x801F.EAX,
and use it to override the supported CPUID flags reported to userspace.
Masking the re
On Thu, Jan 28, 2021, Paolo Bonzini wrote:
> On 14/01/21 01:36, Sean Christopherson wrote:
> > Add a reverse-CPUID entry for the memory encryption word, 0x801F.EAX,
> > and use it to override the supported CPUID flags reported to userspace.
> > Masking the reported CPUID flags avoids over-repor
On 14/01/21 01:36, Sean Christopherson wrote:
Add a reverse-CPUID entry for the memory encryption word, 0x801F.EAX,
and use it to override the supported CPUID flags reported to userspace.
Masking the reported CPUID flags avoids over-reporting KVM support, e.g.
without the mask a SEV-SNP capab
On 1/13/21 6:36 PM, Sean Christopherson wrote:
> Add a reverse-CPUID entry for the memory encryption word, 0x801F.EAX,
> and use it to override the supported CPUID flags reported to userspace.
> Masking the reported CPUID flags avoids over-reporting KVM support, e.g.
> without the mask a SEV-
Add a reverse-CPUID entry for the memory encryption word, 0x801F.EAX,
and use it to override the supported CPUID flags reported to userspace.
Masking the reported CPUID flags avoids over-reporting KVM support, e.g.
without the mask a SEV-SNP capable CPU may incorrectly advertise SNP
support to
5 matches
Mail list logo