All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
Cc: ohmura.kei@lab.ntt.co.jp, mtosatti@redhat.com,
	qemu-devel@nongnu.org, avi@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] Introduce wrapper functions to access phys_ram_dirty, and replace existing direct accesses to it.
Date: Thu, 8 Apr 2010 11:59:27 +0200	[thread overview]
Message-ID: <20100408095926.GE5700@volta.aurel32.net> (raw)
In-Reply-To: <1269329993-10854-1-git-send-email-tamura.yoshiaki@lab.ntt.co.jp>

On Tue, Mar 23, 2010 at 04:39:51PM +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
> 
> Also rebased to qemu.git aa28b9bf9ba0904766b15e7ab8d62a76cb3225da.
> 

Thanks, applied.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

      parent reply	other threads:[~2010-04-08 11:16 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
2010-04-08  9:59 ` Aurelien Jarno [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=20100408095926.GE5700@volta.aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=avi@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=ohmura.kei@lab.ntt.co.jp \
    --cc=qemu-devel@nongnu.org \
    --cc=tamura.yoshiaki@lab.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 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.