From: Avi Kivity <avi@redhat.com>
To: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
Cc: aliguori@us.ibm.com, mtosatti@redhat.com, qemu-devel@nongnu.org,
ohmura.kei@lab.ntt.co.jp
Subject: [Qemu-devel] Re: [PATCH v4 0/4] Introduce bit-based phys_ram_dirty, and bit-based dirty page checker.
Date: Wed, 21 Apr 2010 15:15:42 +0300 [thread overview]
Message-ID: <4BCEEC6E.6060103@redhat.com> (raw)
In-Reply-To: <1271734843-24231-1-git-send-email-tamura.yoshiaki@lab.ntt.co.jp>
On 04/20/2010 06:40 AM, Yoshiaki Tamura wrote:
> The dirty and non-dirty pages are checked one by one. When most of the memory
> is not dirty, checking the dirty and non-dirty pages by multiple page size
> should be much faster than checking them one by one. We introduced bit-based
> phys_ram_dirty for VGA, CODE, MIGRATION, MASTER, and
> cpu_physical_memory_get_dirty_range() for this purpose.
>
Looks good.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-04-21 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 3:40 [Qemu-devel] [PATCH v4 0/4] Introduce bit-based phys_ram_dirty, and bit-based dirty page checker Yoshiaki Tamura
2010-04-20 3:40 ` [Qemu-devel] [PATCH v4 1/4] Modify DIRTY_FLAG value and introduce DIRTY_IDX to use as indexes of bit-based phys_ram_dirty Yoshiaki Tamura
2010-05-03 20:03 ` Anthony Liguori
2010-05-04 8:31 ` Yoshiaki Tamura
2010-04-20 3:40 ` [Qemu-devel] [PATCH v4 2/4] Introduce cpu_physical_memory_get_dirty_range() Yoshiaki Tamura
2010-04-20 3:40 ` [Qemu-devel] [PATCH v4 3/4] Use cpu_physical_memory_set_dirty_range() to update phys_ram_dirty Yoshiaki Tamura
2010-04-20 3:40 ` [Qemu-devel] [PATCH v4 4/4] Use cpu_physical_memory_get_dirty_range() to check multiple dirty pages Yoshiaki Tamura
2010-04-21 12:15 ` Avi Kivity [this message]
2010-04-26 10:43 ` [Qemu-devel] Re: [PATCH v4 0/4] Introduce bit-based phys_ram_dirty, and bit-based dirty page checker Yoshiaki Tamura
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=4BCEEC6E.6060103@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.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.