From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org, "David S. Ahern" <daahern@cisco.com>
Subject: Re: [patch 09/10] KVM: MMU: out of sync shadow core v2
Date: Mon, 22 Sep 2008 23:41:14 +0300 [thread overview]
Message-ID: <48D802EA.9070807@redhat.com> (raw)
In-Reply-To: <20080921004515.GC10120@dmt.cnet>
Marcelo Tosatti wrote:
>>> + while (parent->unsync_children) {
>>> + for (i = 0; i < PT64_ENT_PER_PAGE; ++i) {
>>> + u64 ent = sp->spt[i];
>>> +
>>> + if (is_shadow_present_pte(ent)) {
>>> + struct kvm_mmu_page *child;
>>> + child = page_header(ent & PT64_BASE_ADDR_MASK);
>>>
>> What does this do?
>>
>
> Walks all children of given page with no efficiency. Its replaced later
> by the bitmap version.
>
>
I don't understand how the variables sp, child, and parent interact. You
either need recursion or an explicit stack?
>>> +static int kvm_sync_page(struct kvm_vcpu *vcpu, struct kvm_mmu_page *sp)
>>> +{
>>> + if (sp->role.glevels != vcpu->arch.mmu.root_level) {
>>> + kvm_mmu_zap_page(vcpu->kvm, sp);
>>> + return 1;
>>> + }
>>>
>>>
>> Suppose we switch to real mode, touch a pte, switch back. Is this handled?
>>
>
> The shadow page will go unsync on pte touch and resynced as soon as its
> visible (after return to paging).
>
> Or, while still in real mode, it might be zapped by
> kvm_mmu_get_page->kvm_sync_page.
>
> Am I missing something?
>
>
I guess I was. Ok.
>
>>> static int kvm_mmu_zap_page(struct kvm *kvm, struct kvm_mmu_page *sp)
>>> - return 0;
>>> + return ret;
>>> }
>>>
>>>
>> Why does the caller care if zap also zapped some other random pages? To
>> restart walking the list?
>>
>
> Yes. The next element for_each_entry_safe saved could have been zapped.
>
>
Ouch. Ouch.
I hate doing this. Can see no alternative though.
>>> + /* don't unsync if pagetable is shadowed with multiple roles */
>>> + hlist_for_each_entry_safe(s, node, n, bucket, hash_link) {
>>> + if (s->gfn != sp->gfn || s->role.metaphysical)
>>> + continue;
>>> + if (s->role.word != sp->role.word)
>>> + return 1;
>>> + }
>>>
>>>
>> This will happen for nonpae paging. But why not allow it? Zap all
>> unsynced pages on mode switch.
>>
>> Oh, if a page is both a page directory and page table, yes.
>>
>
> Yes.
>
>
>> So to allow nonpae oos, check the level instead.
>>
>
> Windows 2008 64-bit has all sorts of sharing a pagetable at multiple
> levels too.
>
>
We still want to allow oos for the two quadrants of a nonpae shadow page.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-09-22 20:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 21:27 [patch 00/10] out of sync shadow v2 Marcelo Tosatti
2008-09-18 21:27 ` [patch 01/10] KVM: MMU: split mmu_set_spte Marcelo Tosatti
2008-09-18 21:27 ` [patch 02/10] KVM: MMU: move local TLB flush to mmu_set_spte Marcelo Tosatti
2008-09-20 0:21 ` Avi Kivity
2008-09-18 21:27 ` [patch 03/10] KVM: MMU: do not write-protect large mappings Marcelo Tosatti
2008-09-20 0:29 ` Avi Kivity
2008-09-21 0:41 ` Marcelo Tosatti
2008-09-18 21:27 ` [patch 04/10] KVM: MMU: mode specific sync_page Marcelo Tosatti
2008-09-20 0:44 ` Avi Kivity
2008-09-18 21:27 ` [patch 05/10] KVM: MMU: sync roots on mmu reload Marcelo Tosatti
2008-09-18 21:27 ` [patch 06/10] KVM: x86: trap invlpg Marcelo Tosatti
2008-09-20 0:53 ` Avi Kivity
2008-09-21 0:43 ` Marcelo Tosatti
2008-09-18 21:27 ` [patch 07/10] KVM: MMU: mmu_parent_walk Marcelo Tosatti
2008-09-20 0:56 ` Avi Kivity
2008-09-21 0:44 ` Marcelo Tosatti
2008-09-22 20:30 ` Avi Kivity
2008-09-22 22:04 ` Marcelo Tosatti
2008-09-18 21:27 ` [patch 08/10] KVM: MMU: awareness of new kvm_mmu_zap_page behaviour Marcelo Tosatti
2008-09-18 21:27 ` [patch 09/10] KVM: MMU: out of sync shadow core v2 Marcelo Tosatti
2008-09-20 1:22 ` Avi Kivity
2008-09-21 0:45 ` Marcelo Tosatti
2008-09-22 20:41 ` Avi Kivity [this message]
2008-09-22 21:55 ` Marcelo Tosatti
2008-09-22 22:51 ` Marcelo Tosatti
2008-09-23 10:46 ` Avi Kivity
2008-09-23 10:46 ` Avi Kivity
2008-09-23 13:17 ` Marcelo Tosatti
2008-09-18 21:27 ` [patch 10/10] KVM: MMU: speed up mmu_unsync_walk Marcelo Tosatti
2008-09-20 1:26 ` Avi Kivity
2008-09-21 0:45 ` Marcelo Tosatti
2008-09-22 20:43 ` Avi Kivity
2008-09-18 22:36 ` [patch 00/10] out of sync shadow v2 Marcelo Tosatti
2008-09-20 1:28 ` Avi Kivity
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=48D802EA.9070807@redhat.com \
--to=avi@redhat.com \
--cc=daahern@cisco.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 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.