[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0a00ee34-965a-0ee1-1e2c-7fda8e21ec9e@redhat.com>
Date: Fri, 23 Apr 2021 09:08:55 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Wei Huang <wei.huang2@....com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, Borislav Petkov <bp@...e.de>,
Tom Lendacky <thomas.lendacky@....com>,
Brijesh Singh <brijesh.singh@....com>
Subject: Re: [PATCH v5 03/15] KVM: SVM: Disable SEV/SEV-ES if NPT is disabled
On 22/04/21 20:11, Sean Christopherson wrote:
>> Yes, you're right. NPT is easy but we would have to guess what the spec
>> would say about MAXPHYADDR, while nNPT would require the stacking of a PML5.
>> Either way, blocking KVM is the easiest thing todo.
> How about I fold that into the s/lm_root/pml4_root rename[*]? I.e. make the
> blocking of PML5 a functional change, and the rename an opportunistic change?
>
> [*]https://lkml.kernel.org/r/20210318201131.3242619-1-seanjc@google.com
>
Yes, that's a good plan. Thanks,
Paolo
Powered by blists - more mailing lists