From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: disable on 32-bit unless CONFIG_BROKEN
Date: Tue, 27 Sep 2022 17:07:39 +0000 [thread overview]
Message-ID: <YzMt24/14n1BVdnI@google.com> (raw)
In-Reply-To: <20220926165112.603078-1-pbonzini@redhat.com>
On Mon, Sep 26, 2022, Paolo Bonzini wrote:
> 32-bit KVM has extra complications in the code due to:
>
> - different ways to write 64-bit values in VMCS
>
> - different handling of DS and ES selectors as well as FS/GS bases
>
> - lack of CR8 and EFER
>
> - lack of XFD
>
More for the list:
- SVM is effectively restricted to PAE kernels due to NX requirements
> - impossibility of writing 64-bit PTEs atomically
It's not impossible, just ugly. KVM could use CMPXCHG8B to do all of the accesses
for the TDP MMU, including the non-atomic reads and writes.
> The last is the big one, because it prevents from using the TDP MMU
> unconditionally.
As above, if the TDP MMU really is the sticking point, that's solvable.
The real justification for deprecating 32-bit KVM is that, outside of KVM developers,
literally no one uses 32-bit KVM. I.e. any amount of effort that is required to
continue supporting 32-bit kernels is a complete waste of resources.
next prev parent reply other threads:[~2022-09-27 17:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 16:51 [PATCH] KVM: x86: disable on 32-bit unless CONFIG_BROKEN Paolo Bonzini
2022-09-27 17:07 ` Sean Christopherson [this message]
2022-09-28 7:10 ` Maxim Levitsky
2022-09-28 9:55 ` Paolo Bonzini
2022-09-28 16:12 ` Sean Christopherson
2022-09-28 17:43 ` Maxim Levitsky
2022-09-28 17:44 ` Maxim Levitsky
2022-09-28 17:55 ` Sean Christopherson
2022-09-29 13:26 ` Paolo Bonzini
2022-09-29 13:52 ` Maxim Levitsky
2022-09-29 15:07 ` Paolo Bonzini
2023-02-17 19:36 ` Thomas Huth
2023-02-22 22:27 ` Sean Christopherson
2023-02-23 7:01 ` Thomas Huth
2023-02-23 8:33 ` Maxim Levitsky
2023-02-23 22:10 ` Sean Christopherson
2023-02-24 6:28 ` Thomas Huth
2022-09-28 10:04 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YzMt24/14n1BVdnI@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.