From: Gleb Natapov <gleb@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] KVM: Write protect the updated slot only when we start dirty logging
Date: Tue, 8 Jan 2013 13:50:26 +0200 [thread overview]
Message-ID: <20130108115026.GA700@redhat.com> (raw)
In-Reply-To: <20130107201146.GA19224@amt.cnet>
On Mon, Jan 07, 2013 at 06:11:46PM -0200, Marcelo Tosatti wrote:
> On Tue, Dec 18, 2012 at 04:26:47PM +0900, Takuya Yoshikawa wrote:
> > This is needed to make kvm_mmu_slot_remove_write_access() rmap based:
> > otherwise we may end up using invalid rmap's.
> >
> > Signed-off-by: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>
>
> Why? memslot->arch.rmap[] has been properly allocated at this point.
>
FWIW a long time ago in a galaxy far, far away there was a check for
KVM_MEM_LOG_DIRTY_PAGES before call to kvm_mmu_slot_remove_write_access(),
but it was removed by 90cb0529dd230548a7, as far as I can tell, accidentally.
> > ---
> > arch/x86/kvm/x86.c | 9 ++++++++-
> > virt/kvm/kvm_main.c | 1 -
> > 2 files changed, 8 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> > index 1c9c834..9451efa 100644
> > --- a/arch/x86/kvm/x86.c
> > +++ b/arch/x86/kvm/x86.c
> > @@ -6897,7 +6897,14 @@ void kvm_arch_commit_memory_region(struct kvm *kvm,
> > spin_lock(&kvm->mmu_lock);
> > if (nr_mmu_pages)
> > kvm_mmu_change_mmu_pages(kvm, nr_mmu_pages);
> > - kvm_mmu_slot_remove_write_access(kvm, mem->slot);
> > + /*
> > + * Write protect all pages for dirty logging.
> > + * Existing largepage mappings are destroyed here and new ones will
> > + * not be created until the end of the logging.
> > + */
> > + if ((mem->flags & KVM_MEM_LOG_DIRTY_PAGES) &&
> > + !(old.flags & KVM_MEM_LOG_DIRTY_PAGES))
> > + kvm_mmu_slot_remove_write_access(kvm, mem->slot);
> > spin_unlock(&kvm->mmu_lock);
> > /*
> > * If memory slot is created, or moved, we need to clear all
> > diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> > index bd31096..0ef5daa 100644
> > --- a/virt/kvm/kvm_main.c
> > +++ b/virt/kvm/kvm_main.c
> > @@ -805,7 +805,6 @@ int __kvm_set_memory_region(struct kvm *kvm,
> > if ((new.flags & KVM_MEM_LOG_DIRTY_PAGES) && !new.dirty_bitmap) {
> > if (kvm_create_dirty_bitmap(&new) < 0)
> > goto out_free;
> > - /* destroy any largepage mappings for dirty tracking */
> > }
> >
> > if (!npages || base_gfn != old.base_gfn) {
> > --
> > 1.7.5.4
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Gleb.
next prev parent reply other threads:[~2013-01-08 11:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 7:25 [PATCH 0/7] KVM: Alleviate mmu_lock hold time when we start dirty logging Takuya Yoshikawa
2012-12-18 7:26 ` [PATCH 1/7] KVM: Write protect the updated slot only " Takuya Yoshikawa
2012-12-24 13:27 ` Gleb Natapov
2012-12-25 4:08 ` Takuya Yoshikawa
2012-12-25 5:05 ` Gleb Natapov
2012-12-25 5:26 ` Takuya Yoshikawa
2013-01-07 20:11 ` Marcelo Tosatti
2013-01-08 11:50 ` Gleb Natapov [this message]
2012-12-18 7:27 ` [PATCH 2/7] KVM: MMU: Remove unused parameter level from __rmap_write_protect() Takuya Yoshikawa
2012-12-18 7:28 ` [PATCH 3/7] KVM: MMU: Make kvm_mmu_slot_remove_write_access() rmap based Takuya Yoshikawa
2012-12-18 7:28 ` [PATCH 4/7] KVM: x86: Remove unused slot_bitmap from kvm_mmu_page Takuya Yoshikawa
2012-12-18 7:29 ` [PATCH 5/7] KVM: Make kvm_mmu_change_mmu_pages() take mmu_lock by itself Takuya Yoshikawa
2012-12-18 7:30 ` [PATCH 6/7] KVM: Make kvm_mmu_slot_remove_write_access() " Takuya Yoshikawa
2012-12-18 7:30 ` [PATCH 7/7] KVM: Conditionally reschedule when kvm_mmu_slot_remove_write_access() takes a long time Takuya Yoshikawa
2012-12-19 12:30 ` [PATCH 0/7] KVM: Alleviate mmu_lock hold time when we start dirty logging Takuya Yoshikawa
2012-12-19 15:42 ` Alex Williamson
2012-12-20 5:02 ` Takuya Yoshikawa
2012-12-20 12:59 ` Marcelo Tosatti
2012-12-20 13:22 ` Gleb Natapov
2012-12-20 13:41 ` Alex Williamson
2012-12-20 14:35 ` Takuya Yoshikawa
2012-12-20 14:55 ` Alex Williamson
2012-12-21 8:02 ` Takuya Yoshikawa
2012-12-21 8:54 ` Gleb Natapov
2012-12-21 13:24 ` Alex Williamson
2012-12-21 8:05 ` Takuya Yoshikawa
2013-01-07 20:36 ` Marcelo Tosatti
2013-01-08 10:40 ` Takuya Yoshikawa
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=20130108115026.GA700@redhat.com \
--to=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=yoshikawa_takuya_b1@lab.ntt.co.jp \
/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).