From: Richard Henderson <richard.henderson@linaro.org>
To: Michael Brown <mcb30@ipxe.org>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Eduardo Habkost <eduardo@habkost.net>
Subject: Re: [PATCH] target/i386: Fix physical address truncation when PAE is enabled
Date: Thu, 21 Dec 2023 08:51:26 +1100 [thread overview]
Message-ID: <bc0694ff-49a7-4fc0-9cd9-ac139f310bd8@linaro.org> (raw)
In-Reply-To: <0102018c86e4f17c-5e356421-08c8-4d3a-a149-5897437892ac-000000@eu-west-1.amazonses.com>
On 12/20/23 22:03, Michael Brown wrote:
> For the default case, I think it would make sense to unconditionally truncate the address
> to 32 bits if paging is disabled. (I am not sure why the original commit 33dfdb5 included
> a test for long mode, since I do not see how it is possible to get the CPU into long mode
> with paging disabled.)
You are correct that paging is mandatory for LMA -- indeed, setting CR0.PG is the final
step in 10.8.5 Initializing IA-32e Mode, which copies EFER.LME to EFER.LMA.
The commit 33dfdb5 that you reference is definitely wrong.
> I do not know what ought to be done in the MMU_NESTED_IDX case, and would appreciate your
> input on this.
It would be ideal if MMU_NESTED_IDX were only used when virtualization is enabled and
nested_ctl & SVM_NPT_ENABLED, i.e. when use_stage2 is true.
I can't remember why I added a check for use_stage2 for MMU_NESTED_IDX in 98281984a37. It
is possible that, as that patch introduced the feature, I was being cautious. It's also
possible that I did see something, but then it was cleaned up somewhere in the rest of
that rather large patch series.
In any case, current intended behaviour is that MMU_NESTED_IDX with !use_stage2 equates to
MMU_PHYS_IDX.
r~
next prev parent reply other threads:[~2023-12-20 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 12:56 [PATCH] target/i386: Fix physical address truncation when PAE is enabled Michael Brown
2023-12-20 4:22 ` Richard Henderson
2023-12-20 11:03 ` Michael Brown
2023-12-20 21:51 ` Richard Henderson [this message]
2023-12-21 15:20 ` Michael Brown
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=bc0694ff-49a7-4fc0-9cd9-ac139f310bd8@linaro.org \
--to=richard.henderson@linaro.org \
--cc=eduardo@habkost.net \
--cc=mcb30@ipxe.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).