From: Paolo Bonzini <pbonzini@redhat.com>
To: Maxim Levitsky <mlevitsk@redhat.com>, Li Qiang <liq3ea@gmail.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
Avi Kivity <avi.kivity@gmail.com>
Subject: Re: Questions about the real mode in kvm/qemu
Date: Thu, 26 Sep 2019 11:33:05 +0200 [thread overview]
Message-ID: <4ed0f9ca-6cd1-fd8e-9abd-4098f85c7f9d@redhat.com> (raw)
In-Reply-To: <7c019f3a5236daaa79e67467f64cde212ad05f35.camel@redhat.com>
On 26/09/19 11:24, Maxim Levitsky wrote:
> On Thu, 2019-09-26 at 11:18 +0200, Paolo Bonzini wrote:
>> On 26/09/19 10:59, Maxim Levitsky wrote:
>>> If you mean to ask if there is a way to let guest access use no
>>> paging at all, that is access host physical addresses directly, then
>>> indeed there is no way, since regular non 'unrestricted guest' mode
>>> required both protected mode and paging, and 'unrestricted guest'
>>> requires EPT. Academically speaking it is of course possible to
>>> create paging tables that are 1:1...
>>
>> Not so academically, it's exactly what KVM does.
> You mean KVM uses 1:1 EPT pages and no guest paging,
> to allow guest to access host physical address space?
No, it uses the usual HVA->GPA EPT pages and 1:1 GPA->GVA pages when EPT
is enabled and guest CR0.PG=0. This lets KVM work around the CR0.PG=1
requirement when unrestricted guest mode.
Thinking more about it, I suppose that saves memory (the same EPT page
tables can now be used independent of guest CR0.PG), at the cost of
making TLB misses a little slower.
Thanks,
Paolo
>> However, indeed it
>> would also be possible to switch out of EPT mode when CR0.PG=0. I'm not
>> sure why it was done this way, maybe when the code was written it was
>> simpler to use the identity map.
>>
>> Let's see if Avi is listening... :)
>>
>> Paolo
>
> Here a quote from the PRM:
>
> "The first processors to support VMX operation require CR0.PE and CR0.PG to be 1 in VMX operation (see Section
> 23.8). This restriction implies that guest software cannot be run in unpaged protected mode or in real-address
> mode. Later processors support a VM-execution control called “unrestricted guest”. 1 If this control is 1, CR0.PE and
> CR0.PG may be 0 in VMX non-root operation. Such processors allow guest software to run in unpaged protected
> mode or in real-address mode. The following items describe the behavior of such software:"
> ...
>
> "As noted in Section 26.2.1.1, the “enable EPT” VM-execution control must be 1 if the “unrestricted guest” VM-execution control is 1."
>
>
> Best regards,
> Maxim Levitsky
>
next prev parent reply other threads:[~2019-09-26 9:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 7:52 Questions about the real mode in kvm/qemu Li Qiang
2019-09-26 8:31 ` Maxim Levitsky
2019-09-26 8:52 ` Li Qiang
2019-09-26 8:59 ` Maxim Levitsky
2019-09-26 9:18 ` Paolo Bonzini
2019-09-26 9:24 ` Maxim Levitsky
2019-09-26 9:33 ` Paolo Bonzini [this message]
2019-09-26 9:41 ` Maxim Levitsky
2019-09-26 10:00 ` Paolo Bonzini
2019-09-26 10:03 ` Maxim Levitsky
2019-09-28 22:10 ` Avi Kivity
2019-09-29 7:39 ` Li Qiang
2019-09-26 9:15 ` Paolo Bonzini
2019-09-26 9:35 ` Maxim Levitsky
2019-09-26 9:35 ` Li Qiang
2019-09-26 9:53 ` Paolo Bonzini
2019-09-26 11:47 ` Li Qiang
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=4ed0f9ca-6cd1-fd8e-9abd-4098f85c7f9d@redhat.com \
--to=pbonzini@redhat.com \
--cc=avi.kivity@gmail.com \
--cc=liq3ea@gmail.com \
--cc=mlevitsk@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).