[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <882d8bb4-8d40-1b4d-0742-4a4f2c307e5b@redhat.com>
Date: Thu, 22 Apr 2021 19:08:05 +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 18:15, Sean Christopherson wrote:
>> Support for 5-level page tables on NPT is not hard to fix and could be
>> tested by patching QEMU. However, the !NPT case would also have to be fixed
>> by extending the PDP and PML4 stacking trick to a PML5.
>
> Isn't that backwards? It's the nested NPT case that requires the stacking trick.
> When !NPT is disabled in L0 KVM, 32-bit guests are run with PAE paging. Maybe
> I'm misunderstanding what you're suggesting.
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.
Paolo
Powered by blists - more mailing lists