From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: MMU: Disassociate direct maps from guest levels
Date: Wed, 17 Mar 2010 15:16:25 -0300 [thread overview]
Message-ID: <20100317181625.GA10372@amt.cnet> (raw)
In-Reply-To: <1268554972-9827-1-git-send-email-avi@redhat.com>
On Sun, Mar 14, 2010 at 10:22:52AM +0200, Avi Kivity wrote:
> Direct maps are linear translations for a section of memory, used for
> real mode or with large pages. As such, they are independent of the guest
> levels.
>
> Teach the mmu about this by making page->role.glevels = 0 for direct maps.
> This allows direct maps to be shared among real mode and the various paging
> modes.
>
> Signed-off-by: Avi Kivity <avi@redhat.com>
> ---
> arch/x86/kvm/mmu.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index b137515..a984bc1 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -1328,6 +1328,8 @@ static struct kvm_mmu_page *kvm_mmu_get_page(struct kvm_vcpu *vcpu,
> role = vcpu->arch.mmu.base_role;
> role.level = level;
> role.direct = direct;
> + if (role.direct)
> + role.glevels = 0;
> role.access = access;
> if (vcpu->arch.mmu.root_level <= PT32_ROOT_LEVEL) {
> quadrant = gaddr >> (PAGE_SHIFT + (PT64_PT_BITS * level));
> --
> 1.7.0.2
Isnt this what happens already, since for tdp base_role.glevels is not
initialized?
next prev parent reply other threads:[~2010-03-17 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 8:22 [PATCH] KVM: MMU: Disassociate direct maps from guest levels Avi Kivity
2010-03-17 18:16 ` Marcelo Tosatti [this message]
2010-03-23 10:51 ` Avi Kivity
2010-03-23 11:01 ` Joerg Roedel
2010-03-23 11:02 ` Avi Kivity
2010-03-23 13:59 ` Marcelo Tosatti
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=20100317181625.GA10372@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.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 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.