From: Anthony PERARD <anthony.perard@citrix.com>
To: Avi Kivity <avi@redhat.com>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Xen Devel <xen-devel@lists.xen.org>,
QEMU-devel <qemu-devel@nongnu.org>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH 3/4] exec, memory: Call to xen_modified_memory.
Date: Thu, 19 Jul 2012 15:27:30 +0100 [thread overview]
Message-ID: <50081952.2080706@citrix.com> (raw)
In-Reply-To: <5007F473.8070301@redhat.com>
On 19/07/12 12:50, Avi Kivity wrote:
> On 07/19/2012 02:41 PM, Anthony PERARD wrote:
>> On 17/07/12 19:36, Stefano Stabellini wrote:
>>> On Tue, 17 Jul 2012, Avi Kivity wrote:
>>>> How about pushing the call into cpu_physical_memory_set_dirty_flags()?
>>>> Would that reduce the number of call sites?
>>>
>>> Pushing the calls to cpu_physical_memory_set_dirty_flags and
>>> cpu_physical_memory_set_dirty_range would make the code much nicer.
>>> However being these functions in exec-obsolete.h, are they at risk of
>>> removal?
>>
>> I thought about it, but when I saw that set_dirty were called only when
>> it was not already set as dirty where the call seams to be necessary.
>>
>> I just try to call xen_modified_mem only within
>> cpu_phy_mem_set_dirty_flags but it does not work, even when I tried to
>> clear the dirtybits. But I maybe don't do the right thing yet to clear
>> the dirty bits
>
> You can wrap the if (not dirty) make_it_dirty() sequence in a helper,
> and insert your hypercall in the helper, unconditionally.
Ok, I'll do that.
Thanks,
--
Anthony PERARD
next prev parent reply other threads:[~2012-07-19 14:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 13:30 [Qemu-devel] [PATCH 0/4] Xen, introducing dirty log for migration Anthony PERARD
2012-07-17 13:30 ` [Qemu-devel] [PATCH 1/4] QMP, Introduce set-global-dirty-log command Anthony PERARD
2012-07-17 13:57 ` Eric Blake
2012-07-17 13:58 ` Avi Kivity
2012-07-17 17:58 ` Stefano Stabellini
2012-07-18 8:30 ` Avi Kivity
2012-07-17 13:30 ` [Qemu-devel] [PATCH 2/4] xen: Introduce xen_modified_memory Anthony PERARD
2012-07-17 13:30 ` [Qemu-devel] [PATCH 3/4] exec, memory: Call to xen_modified_memory Anthony PERARD
2012-07-17 13:37 ` Avi Kivity
2012-07-17 13:59 ` Anthony PERARD
2012-07-17 14:44 ` Avi Kivity
2012-07-17 18:36 ` Stefano Stabellini
2012-07-18 8:32 ` Avi Kivity
2012-07-19 11:41 ` Anthony PERARD
2012-07-19 11:50 ` Avi Kivity
2012-07-19 14:27 ` Anthony PERARD [this message]
2012-07-17 18:06 ` Stefano Stabellini
2012-07-19 12:34 ` Paolo Bonzini
2012-07-19 15:37 ` Stefano Stabellini
2012-07-19 15:41 ` Anthony PERARD
2012-07-17 13:30 ` [Qemu-devel] [PATCH 4/4] xen: Always set the vram dirty during migration Anthony PERARD
2012-07-17 18:25 ` Stefano Stabellini
2012-07-17 18:30 ` Stefano Stabellini
2012-07-20 14:11 ` Anthony PERARD
2012-07-20 15:47 ` Stefano Stabellini
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=50081952.2080706@citrix.com \
--to=anthony.perard@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xen.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).