From: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
ohmura.kei@lab.ntt.co.jp
Subject: Re: [PATCH 2/6] qemu-kvm: Modify and introduce wrapper functions to access phys_ram_dirty.
Date: Wed, 17 Mar 2010 07:50:48 +0900 [thread overview]
Message-ID: <4BA00B48.5040108@lab.ntt.co.jp> (raw)
In-Reply-To: <4B9F8904.2040704@codemonkey.ws>
Anthony Liguori wrote:
> On 03/16/2010 07:45 AM, Avi Kivity wrote:
>> On 03/16/2010 12:53 PM, Yoshiaki Tamura wrote:
>>> Modifies wrapper functions for byte-based phys_ram_dirty bitmap to
>>> bit-based phys_ram_dirty bitmap, and adds more wrapper functions to
>>> prevent
>>> direct access to the phys_ram_dirty bitmap.
>>
>>> +
>>> +static inline int cpu_physical_memory_get_dirty_flags(ram_addr_t addr)
>>> +{
>>> + unsigned long mask;
>>> + int index = (addr>> TARGET_PAGE_BITS) / HOST_LONG_BITS;
>>> + int offset = (addr>> TARGET_PAGE_BITS)& (HOST_LONG_BITS - 1);
>>> + int ret = 0;
>>> +
>>> + mask = 1UL<< offset;
>>> + if (phys_ram_vga_dirty[index]& mask)
>>> + ret |= VGA_DIRTY_FLAG;
>>> + if (phys_ram_code_dirty[index]& mask)
>>> + ret |= CODE_DIRTY_FLAG;
>>> + if (phys_ram_migration_dirty[index]& mask)
>>> + ret |= MIGRATION_DIRTY_FLAG;
>>> +
>>> + return ret;
>>> }
>>>
>>> static inline int cpu_physical_memory_get_dirty(ram_addr_t addr,
>>> int dirty_flags)
>>> {
>>> - return phys_ram_dirty[addr>> TARGET_PAGE_BITS]& dirty_flags;
>>> + return cpu_physical_memory_get_dirty_flags(addr)& dirty_flags;
>>> }
>>
>> This turns one cacheline access into three. If the dirty bitmaps were
>> in an array, you could do
>>
>> return dirty_bitmaps[dirty_index][addr >> (TARGET_PAGE_BITS +
>> BITS_IN_LONG)] & mask;
>>
>> with one cacheline access.
>
> As far as I can tell, we only ever call with a single flag so your
> suggestion makes sense.
>
> I'd suggest introducing these functions before splitting the bitmap up.
> It makes review a bit easier.
Thanks for your advise.
I'll post the wrapper functions for existing byte-based phys_ram_dirty first.
Yoshi
WARNING: multiple messages have this Message-ID (diff)
From: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: ohmura.kei@lab.ntt.co.jp, Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 2/6] qemu-kvm: Modify and introduce wrapper functions to access phys_ram_dirty.
Date: Wed, 17 Mar 2010 07:50:48 +0900 [thread overview]
Message-ID: <4BA00B48.5040108@lab.ntt.co.jp> (raw)
In-Reply-To: <4B9F8904.2040704@codemonkey.ws>
Anthony Liguori wrote:
> On 03/16/2010 07:45 AM, Avi Kivity wrote:
>> On 03/16/2010 12:53 PM, Yoshiaki Tamura wrote:
>>> Modifies wrapper functions for byte-based phys_ram_dirty bitmap to
>>> bit-based phys_ram_dirty bitmap, and adds more wrapper functions to
>>> prevent
>>> direct access to the phys_ram_dirty bitmap.
>>
>>> +
>>> +static inline int cpu_physical_memory_get_dirty_flags(ram_addr_t addr)
>>> +{
>>> + unsigned long mask;
>>> + int index = (addr>> TARGET_PAGE_BITS) / HOST_LONG_BITS;
>>> + int offset = (addr>> TARGET_PAGE_BITS)& (HOST_LONG_BITS - 1);
>>> + int ret = 0;
>>> +
>>> + mask = 1UL<< offset;
>>> + if (phys_ram_vga_dirty[index]& mask)
>>> + ret |= VGA_DIRTY_FLAG;
>>> + if (phys_ram_code_dirty[index]& mask)
>>> + ret |= CODE_DIRTY_FLAG;
>>> + if (phys_ram_migration_dirty[index]& mask)
>>> + ret |= MIGRATION_DIRTY_FLAG;
>>> +
>>> + return ret;
>>> }
>>>
>>> static inline int cpu_physical_memory_get_dirty(ram_addr_t addr,
>>> int dirty_flags)
>>> {
>>> - return phys_ram_dirty[addr>> TARGET_PAGE_BITS]& dirty_flags;
>>> + return cpu_physical_memory_get_dirty_flags(addr)& dirty_flags;
>>> }
>>
>> This turns one cacheline access into three. If the dirty bitmaps were
>> in an array, you could do
>>
>> return dirty_bitmaps[dirty_index][addr >> (TARGET_PAGE_BITS +
>> BITS_IN_LONG)] & mask;
>>
>> with one cacheline access.
>
> As far as I can tell, we only ever call with a single flag so your
> suggestion makes sense.
>
> I'd suggest introducing these functions before splitting the bitmap up.
> It makes review a bit easier.
Thanks for your advise.
I'll post the wrapper functions for existing byte-based phys_ram_dirty first.
Yoshi
next prev parent reply other threads:[~2010-03-16 22:51 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 10:53 [PATCH 0/6] qemu-kvm: Introduce bit-based phys_ram_dirty, and bit-based dirty page checker Yoshiaki Tamura
2010-03-16 10:53 ` [Qemu-devel] " Yoshiaki Tamura
2010-03-16 10:53 ` [PATCH 1/6] qemu-kvm: Introduce bit-based phys_ram_dirty for VGA, CODE and MIGRATION Yoshiaki Tamura
2010-03-16 10:53 ` [Qemu-devel] " Yoshiaki Tamura
2010-03-16 12:26 ` Avi Kivity
2010-03-16 12:26 ` [Qemu-devel] " Avi Kivity
2010-03-16 13:01 ` Yoshiaki Tamura
2010-03-16 13:01 ` [Qemu-devel] " Yoshiaki Tamura
2010-03-16 13:04 ` Avi Kivity
2010-03-16 13:04 ` [Qemu-devel] " Avi Kivity
2010-03-16 10:53 ` [PATCH 2/6] qemu-kvm: Modify and introduce wrapper functions to access phys_ram_dirty Yoshiaki Tamura
2010-03-16 10:53 ` [Qemu-devel] " Yoshiaki Tamura
2010-03-16 12:45 ` Avi Kivity
2010-03-16 12:45 ` [Qemu-devel] " Avi Kivity
2010-03-16 13:17 ` Yoshiaki Tamura
2010-03-16 13:17 ` [Qemu-devel] " Yoshiaki Tamura
2010-03-16 13:29 ` Avi Kivity
2010-03-16 13:29 ` [Qemu-devel] " Avi Kivity
2010-03-16 13:49 ` Yoshiaki Tamura
2010-03-16 13:49 ` [Qemu-devel] " Yoshiaki Tamura
2010-03-16 13:51 ` Anthony Liguori
2010-03-16 13:51 ` [Qemu-devel] " Anthony Liguori
2010-03-16 13:57 ` Avi Kivity
2010-03-16 13:57 ` [Qemu-devel] " Avi Kivity
2010-03-16 14:50 ` Anthony Liguori
2010-03-16 14:50 ` [Qemu-devel] " Anthony Liguori
2010-03-16 20:10 ` Blue Swirl
2010-03-16 20:10 ` Blue Swirl
2010-03-16 22:31 ` Richard Henderson
2010-03-16 22:31 ` [Qemu-devel] " Richard Henderson
2010-03-17 0:05 ` Paul Brook
2010-03-17 0:05 ` Paul Brook
2010-03-17 4:07 ` Avi Kivity
2010-03-17 4:07 ` Avi Kivity
2010-03-17 16:06 ` Paul Brook
2010-03-17 16:06 ` Paul Brook
2010-03-17 16:28 ` Avi Kivity
2010-03-17 16:28 ` Avi Kivity
2010-03-16 13:35 ` Anthony Liguori
2010-03-16 13:35 ` [Qemu-devel] " Anthony Liguori
2010-03-16 22:50 ` Yoshiaki Tamura [this message]
2010-03-16 22:50 ` Yoshiaki Tamura
2010-03-16 10:53 ` [PATCH 3/6] qemu-kvm: Replace direct phys_ram_dirty access with wrapper functions Yoshiaki Tamura
2010-03-16 10:53 ` [Qemu-devel] " Yoshiaki Tamura
2010-03-16 10:53 ` [PATCH 4/6] qemu-kvm: Introduce cpu_physical_memory_get_dirty_range() Yoshiaki Tamura
2010-03-16 10:53 ` [Qemu-devel] " Yoshiaki Tamura
2010-03-16 12:47 ` Avi Kivity
2010-03-16 12:47 ` [Qemu-devel] " Avi Kivity
2010-03-16 10:53 ` [PATCH 5/6] qemu-kvm: Use cpu_physical_memory_set_dirty_range() to update phys_ram_dirty Yoshiaki Tamura
2010-03-16 10:53 ` [Qemu-devel] " Yoshiaki Tamura
2010-03-16 10:53 ` [PATCH 6/6] qemu-kvm: Use cpu_physical_memory_get_dirty_range() to check multiple dirty pages Yoshiaki Tamura
2010-03-16 10:53 ` [Qemu-devel] " Yoshiaki Tamura
2010-03-16 13:11 ` [PATCH 0/6] qemu-kvm: Introduce bit-based phys_ram_dirty, and bit-based dirty page checker Avi Kivity
2010-03-16 13:11 ` [Qemu-devel] " Avi Kivity
2010-03-16 13:41 ` Yoshiaki Tamura
2010-03-16 13:41 ` [Qemu-devel] " 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=4BA00B48.5040108@lab.ntt.co.jp \
--to=tamura.yoshiaki@lab.ntt.co.jp \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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 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.