From: Paolo Bonzini <pbonzini@redhat.com>
To: David Matlack <dmatlack@google.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] kvm: x86: fix comment about {mmu,nested_mmu}.gva_to_gpa
Date: Thu, 7 Jan 2016 11:04:02 +0100 [thread overview]
Message-ID: <568E3812.6020804@redhat.com> (raw)
In-Reply-To: <1451492777-7454-1-git-send-email-dmatlack@google.com>
On 30/12/2015 17:26, David Matlack wrote:
> The comment had the meaning of mmu.gva_to_gpa and nested_mmu.gva_to_gpa
> swapped. Fix that, and also add some details describing how each translation
> works.
>
> Signed-off-by: David Matlack <dmatlack@google.com>
> ---
> arch/x86/kvm/mmu.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index e7c2c14..098a9c2 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -4058,10 +4058,12 @@ static void init_kvm_nested_mmu(struct kvm_vcpu *vcpu)
> g_context->inject_page_fault = kvm_inject_page_fault;
>
> /*
> - * Note that arch.mmu.gva_to_gpa translates l2_gva to l1_gpa. The
> - * translation of l2_gpa to l1_gpa addresses is done using the
> - * arch.nested_mmu.gva_to_gpa function. Basically the gva_to_gpa
> - * functions between mmu and nested_mmu are swapped.
> + * Note that arch.mmu.gva_to_gpa translates l2_gpa to l1_gpa using
> + * L1's nested page tables (e.g. EPT12). The nested translation
> + * of l2_gva to l1_gpa is done by arch.nested_mmu.gva_to_gpa using
> + * L2's page tables as the first level of translation and L1's
> + * nested page tables as the second level of translation. Basically
> + * the gva_to_gpa functions between mmu and nested_mmu are swapped.
> */
> if (!is_paging(vcpu)) {
> g_context->nx = false;
>
Applied, thanks.
Paolo
prev parent reply other threads:[~2016-01-07 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 16:26 [PATCH] kvm: x86: fix comment about {mmu,nested_mmu}.gva_to_gpa David Matlack
2016-01-07 10:04 ` Paolo Bonzini [this message]
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=568E3812.6020804@redhat.com \
--to=pbonzini@redhat.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.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).