From: Paolo Bonzini <pbonzini@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>, linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: dirty all pages in kvm_write_guest_cached()
Date: Wed, 08 Apr 2015 10:49:59 +0200 [thread overview]
Message-ID: <5524EBB7.3080906@redhat.com> (raw)
In-Reply-To: <1428438897-22206-1-git-send-email-rkrcmar@redhat.com>
On 07/04/2015 22:34, Radim Krčmář wrote:
> We dirtied only one page because writes originally couldn't span more.
> Use improved syntax for '>> PAGE_SHIFT' while at it.
>
> Fixes: 8f964525a121 ("KVM: Allow cross page reads and writes from cached translations.")
> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
Cross-page reads and writes should never get here; they have
ghc->memslot set to NULL and go through the slow path in kvm_write_guest.
What am I missing?
Paolo
> ---
> The function handles cross memslot writes in a different path.
>
> I think we should dirty pages after partial writes too (r < len),
> but it probably won't happen and I already started refactoring :)
>
> virt/kvm/kvm_main.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index aadef264bed1..863df9dcab6f 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -1665,6 +1665,7 @@ int kvm_write_guest_cached(struct kvm *kvm, struct gfn_to_hva_cache *ghc,
> {
> struct kvm_memslots *slots = kvm_memslots(kvm);
> int r;
> + gfn_t gfn;
>
> BUG_ON(len > ghc->len);
>
> @@ -1680,7 +1681,10 @@ int kvm_write_guest_cached(struct kvm *kvm, struct gfn_to_hva_cache *ghc,
> r = __copy_to_user((void __user *)ghc->hva, data, len);
> if (r)
> return -EFAULT;
> - mark_page_dirty_in_slot(kvm, ghc->memslot, ghc->gpa >> PAGE_SHIFT);
> +
> + for (gfn = gpa_to_gfn(ghc->gpa);
> + gfn <= gpa_to_gfn(ghc->gpa + len - 1); gfn++)
> + mark_page_dirty_in_slot(kvm, ghc->memslot, gfn);
>
> return 0;
> }
>
next prev parent reply other threads:[~2015-04-08 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 20:34 [PATCH] KVM: dirty all pages in kvm_write_guest_cached() Radim Krčmář
2015-04-08 8:49 ` Paolo Bonzini [this message]
2015-04-08 9:26 ` Radim Krčmář
2015-04-08 10:43 ` Paolo Bonzini
2015-04-08 12:16 ` [PATCH] KVM: use slowpath for cross page cached accesses Radim Krčmář
2015-04-08 12:23 ` Paolo Bonzini
2015-04-09 0:18 ` Wanpeng Li
2015-05-02 12:23 ` Patch "KVM: use slowpath for cross page cached accesses" has been added to the 4.0-stable tree gregkh
2015-05-02 12:25 ` Patch "KVM: use slowpath for cross page cached accesses" has been added to the 3.19-stable tree gregkh
2015-05-02 12:28 ` Patch "KVM: use slowpath for cross page cached accesses" has been added to the 3.10-stable tree gregkh
2015-05-02 12:29 ` Patch "KVM: use slowpath for cross page cached accesses" has been added to the 3.14-stable tree gregkh
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=5524EBB7.3080906@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@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.