From: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>,
Andrea Arcangeli <aarcange@redhat.com>,
avi@redhat.com, agraf@suse.de, paulus@samba.org,
kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] KVM: Optimize MMU notifier's THP page invalidation -v4
Date: Tue, 17 Jul 2012 23:06:30 +0900 [thread overview]
Message-ID: <20120717230630.a06c72bc2a4b913dd9277be0@gmail.com> (raw)
In-Reply-To: <20120705130807.GA30235@amt.cnet>
On Thu, 5 Jul 2012 10:08:07 -0300
Marcelo Tosatti <mtosatti@redhat.com> wrote:
> Neat.
>
> Andrea can you please ACK?
>
ping
next prev parent reply other threads:[~2012-07-17 14:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 8:52 [PATCH 0/8] KVM: Optimize MMU notifier's THP page invalidation -v4 Takuya Yoshikawa
2012-07-02 8:53 ` [PATCH 1/8] KVM: MMU: Use __gfn_to_rmap() to clean up kvm_handle_hva() Takuya Yoshikawa
2012-07-02 8:54 ` [PATCH 2/8] KVM: Introduce hva_to_gfn_memslot() for kvm_handle_hva() Takuya Yoshikawa
2012-07-02 8:55 ` [PATCH 3/8] KVM: MMU: Make kvm_handle_hva() handle range of addresses Takuya Yoshikawa
2012-07-02 8:56 ` [PATCH 4/8] KVM: Introduce kvm_unmap_hva_range() for kvm_mmu_notifier_invalidate_range_start() Takuya Yoshikawa
2012-07-02 8:57 ` [PATCH 5/8] KVM: Separate rmap_pde from kvm_lpage_info->write_count Takuya Yoshikawa
2012-07-02 8:57 ` [PATCH 6/8] KVM: MMU: Add memslot parameter to hva handlers Takuya Yoshikawa
2012-07-02 8:58 ` [PATCH 7/8] KVM: MMU: Push trace_kvm_age_page() into kvm_age_rmapp() Takuya Yoshikawa
2012-07-02 8:59 ` [PATCH 8/8] KVM: MMU: Avoid handling same rmap_pde in kvm_handle_hva_range() Takuya Yoshikawa
2012-07-02 9:10 ` [PATCH 0/8] KVM: Optimize MMU notifier's THP page invalidation -v4 Avi Kivity
2012-07-05 13:08 ` Marcelo Tosatti
2012-07-17 14:06 ` Takuya Yoshikawa [this message]
2012-07-18 19:56 ` 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=20120717230630.a06c72bc2a4b913dd9277be0@gmail.com \
--to=takuya.yoshikawa@gmail.com \
--cc=aarcange@redhat.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=paulus@samba.org \
--cc=yoshikawa.takuya@oss.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).