From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>,
Joerg Roedel <joerg.roedel@amd.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: MMU: Disassociate direct maps from guest levels
Date: Tue, 23 Mar 2010 12:51:15 +0200 [thread overview]
Message-ID: <4BA89D23.1090005@redhat.com> (raw)
In-Reply-To: <20100317181625.GA10372@amt.cnet>
On 03/17/2010 08:16 PM, Marcelo Tosatti wrote:
> 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.
>>
>> @@ -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?
>
Correct. I was thinking about the nested npt case, which will use
role.glevels. Joerg, please incorporate this into your nnpt patchset.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-03-23 10:51 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
2010-03-23 10:51 ` Avi Kivity [this message]
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=4BA89D23.1090005@redhat.com \
--to=avi@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox