qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: ohmura.kei@lab.ntt.co.jp, kvm@vger.kernel.org,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, avi@redhat.com
Subject: [Qemu-devel] Re: [PATCH 0/2] qemu-kvm: Introduce wrapper functions to access phys_ram_dirty, and replace existing direct accesses to it.
Date: Mon, 22 Mar 2010 14:33:35 +0900	[thread overview]
Message-ID: <4BA7012F.4020402@lab.ntt.co.jp> (raw)
In-Reply-To: <20100318195912.GA14091@amt.cnet>

Marcelo Tosatti wrote:
> On Wed, Mar 17, 2010 at 02:51:46PM +0900, Yoshiaki Tamura wrote:
>>
>> Before replacing byte-based dirty bitmap with bit-based dirty bitmap,
>> clearing direct accesses to the bitmap first seems to be good point to
>> start with.
>>
>> This patch set is based on the following discussion.
>>
>> http://www.mail-archive.com/kvm@vger.kernel.org/msg30724.html
>>
>> Thanks,
>>
>> Yoshi
>
> Looks fine to me.
>
> This is qemu upstream material, though.

Thanks for your comment.
I should have removed qemu-kvm from the title.

Should I rebase the patch to qemu.git and repost?

      reply	other threads:[~2010-03-22  5:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17  5:51 [Qemu-devel] [PATCH 0/2] qemu-kvm: Introduce wrapper functions to access phys_ram_dirty, and replace existing direct accesses to it Yoshiaki Tamura
2010-03-17  5:51 ` [Qemu-devel] [PATCH 1/2] qemu-kvm: Introduce wrapper functions to access phys_ram_dirty Yoshiaki Tamura
2010-03-17  5:51 ` [Qemu-devel] [PATCH 2/2] qemu-kvm: Replace direct phys_ram_dirty access with wrapper functions Yoshiaki Tamura
2010-03-18 19:59 ` [Qemu-devel] Re: [PATCH 0/2] qemu-kvm: Introduce wrapper functions to access phys_ram_dirty, and replace existing direct accesses to it Marcelo Tosatti
2010-03-22  5:33   ` Yoshiaki Tamura [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=4BA7012F.4020402@lab.ntt.co.jp \
    --to=tamura.yoshiaki@lab.ntt.co.jp \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=ohmura.kei@lab.ntt.co.jp \
    --cc=qemu-devel@nongnu.org \
    /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).