From: Paolo Bonzini <pbonzini@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>, "KVM list" <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: reuse memslot in kvm_write_guest_page
Date: Sat, 11 Apr 2015 15:09:59 +0200 [thread overview]
Message-ID: <55291D27.8070008@redhat.com> (raw)
In-Reply-To: <1428695247-27603-1-git-send-email-rkrcmar@redhat.com>
On 10/04/2015 21:47, Radim Krčmář wrote:
> Saves one O(log N) search.
>
> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
> ---
> I'm still not sure how to bridge the gap between the code we have and
> the code I want, but all routes so far contained this change. Notice
> that we use '_memslot' and '_in_slot' suffix for the same meaning ...
> (And the completely useless 'kvm' parameter for page dirtying.)
I have the same patch (plus exporting mark_dirty_page_in_slot and
removing the extra 'kvm' parameter :)) in my SMM queue. I'll replace it
with yours.
Paolo
prev parent reply other threads:[~2015-04-11 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 19:47 [PATCH] KVM: reuse memslot in kvm_write_guest_page Radim Krčmář
2015-04-11 13:09 ` Paolo Bonzini [this message]
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=55291D27.8070008@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox