qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
To: qemu-devel@nongnu.org, anthony@codemonkey.ws,
	Anthony Liguori <aliguori@us.ibm.com>
Cc: ohmura.kei@lab.ntt.co.jp, mtosatti@redhat.com,
	Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: [PATCH 0/2] Introduce wrapper functions to access phys_ram_dirty, and replace existing direct accesses to it.
Date: Mon, 05 Apr 2010 19:52:25 +0900	[thread overview]
Message-ID: <4BB9C0E9.2080200@lab.ntt.co.jp> (raw)
In-Reply-To: <4BA88330.2000105@redhat.com>

Hi.

Could someone pick this patch set?
I have another patch set which is based on this.
If there are any issues, I'm happy to fix them.

Thanks,

Yoshi

Avi Kivity wrote:
> On 03/23/2010 09:39 AM, 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.
>>
>
> Reviewed-by: Avi Kivity <avi@redhat.com>
>

  reply	other threads:[~2010-04-05 10:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23  7:39 [Qemu-devel] [PATCH 0/2] Introduce wrapper functions to access phys_ram_dirty, and replace existing direct accesses to it Yoshiaki Tamura
2010-03-23  7:39 ` [Qemu-devel] [PATCH 1/2] Introduce wrapper functions to access phys_ram_dirty Yoshiaki Tamura
2010-03-23  7:39 ` [Qemu-devel] [PATCH 2/2] Replace direct phys_ram_dirty access with wrapper functions Yoshiaki Tamura
2010-03-23  9:00 ` [Qemu-devel] Re: [PATCH 0/2] Introduce wrapper functions to access phys_ram_dirty, and replace existing direct accesses to it Avi Kivity
2010-04-05 10:52   ` Yoshiaki Tamura [this message]
2010-04-08  9:59 ` [Qemu-devel] " Aurelien Jarno

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=4BB9C0E9.2080200@lab.ntt.co.jp \
    --to=tamura.yoshiaki@lab.ntt.co.jp \
    --cc=aliguori@us.ibm.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --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).