From: Avi Kivity <avi@redhat.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Xen Devel <xen-devel@lists.xen.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
QEMU-devel <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V2 3/5] exec: Introduce helper to set dirty flags.
Date: Sun, 29 Jul 2012 15:58:17 +0300 [thread overview]
Message-ID: <50153369.3030005@redhat.com> (raw)
In-Reply-To: <1342794882-30648-4-git-send-email-anthony.perard@citrix.com>
On 07/20/2012 05:34 PM, Anthony PERARD wrote:
> This new helper/hook is used in the next patch to add an extra call in a single
> place.
>
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> ---
> exec.c | 42 ++++++++++++++----------------------------
> 1 files changed, 14 insertions(+), 28 deletions(-)
>
> diff --git a/exec.c b/exec.c
> index feb4795..b24a03a 100644
> --- a/exec.c
> +++ b/exec.c
> @@ -3386,6 +3386,16 @@ int cpu_memory_rw_debug(CPUArchState *env, target_ulong addr,
> }
>
> #else
<blank line>
> +static void set_dirty_helper(target_phys_addr_t addr, target_phys_addr_t length)
More meaningful name please. Practically every function can be name
something_helper().
> +{
> + if (!cpu_physical_memory_is_dirty(addr)) {
> + /* invalidate code */
> + tb_invalidate_phys_page_range(addr, addr + length, 0);
> + /* set dirty bit */
> + cpu_physical_memory_set_dirty_flags(addr, (0xff & ~CODE_DIRTY_FLAG));
> + }
> +}
> +
Otherwise looks good; a nice cleanup in its own right.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-07-29 12:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 14:34 [Qemu-devel] [PATCH V2 0/5] Xen, introducing dirty log for migration Anthony PERARD
2012-07-20 14:34 ` Anthony PERARD
2012-07-20 14:34 ` [PATCH V2 1/5] QMP, Introduce xen-set-global-dirty-log command Anthony PERARD
2012-07-20 14:34 ` [Qemu-devel] " Anthony PERARD
2012-07-27 16:30 ` Luiz Capitulino
2012-07-27 16:30 ` Luiz Capitulino
2012-07-20 14:34 ` [Qemu-devel] [PATCH V2 2/5] xen: Introduce xen_modified_memory Anthony PERARD
2012-07-20 14:34 ` Anthony PERARD
2012-07-20 14:34 ` [Qemu-devel] [PATCH V2 3/5] exec: Introduce helper to set dirty flags Anthony PERARD
2012-07-29 12:58 ` Avi Kivity [this message]
2012-07-29 12:58 ` Avi Kivity
2012-07-20 14:34 ` Anthony PERARD
2012-07-20 14:34 ` [Qemu-devel] [PATCH V2 4/5] exec, memory: Call to xen_modified_memory Anthony PERARD
2012-07-20 14:34 ` Anthony PERARD
2012-07-20 14:34 ` [PATCH V2 5/5] xen: Always set the vram dirty during migration Anthony PERARD
2012-07-20 14:34 ` [Qemu-devel] " Anthony PERARD
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=50153369.3030005@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=anthony.perard@citrix.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@citrix.com \
--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 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.