All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: QEMU-devel <qemu-devel@nongnu.org>, Xen Devel <xen-devel@lists.xen.org>
Subject: Re: [Qemu-devel] [PATCH 3/4] exec, memory: Call to xen_modified_memory.
Date: Thu, 19 Jul 2012 16:41:51 +0100	[thread overview]
Message-ID: <CAJJyHjLRLTckfbEZ9KtGV0T=sPoiPefmwZRQeK1pQs4D2gUQuw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1207191624430.23783@kaball.uk.xensource.com>

On Thu, Jul 19, 2012 at 4:37 PM, Stefano Stabellini
<stefano.stabellini@eu.citrix.com> wrote:
>
> Anthony, can you write a patch to change the behavior in
> qemu-xen-traditional too?

Yes.

-- 
Anthony PERARD

  parent reply	other threads:[~2012-07-19 15:42 UTC|newest]

Thread overview: 49+ 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:57   ` Eric Blake
2012-07-17 13:58   ` Avi Kivity
2012-07-17 13:58   ` [Qemu-devel] " Avi Kivity
2012-07-17 17:58     ` Stefano Stabellini
2012-07-17 17:58     ` [Qemu-devel] " Stefano Stabellini
2012-07-18  8:30       ` Avi Kivity
2012-07-18  8:30       ` Avi Kivity
2012-07-17 13:30 ` Anthony PERARD
2012-07-17 13:30 ` [Qemu-devel] [PATCH 2/4] xen: Introduce xen_modified_memory Anthony PERARD
2012-07-17 13:30 ` 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 14:44       ` Avi Kivity
2012-07-17 18:36         ` Stefano Stabellini
2012-07-18  8:32           ` Avi Kivity
2012-07-18  8:32           ` Avi Kivity
2012-07-19 11:41           ` Anthony PERARD
2012-07-19 11:41           ` Anthony PERARD
2012-07-19 11:50             ` Avi Kivity
2012-07-19 14:27               ` Anthony PERARD
2012-07-19 14:27               ` Anthony PERARD
2012-07-19 11:50             ` Avi Kivity
2012-07-17 18:36         ` Stefano Stabellini
2012-07-17 13:59     ` Anthony PERARD
2012-07-17 13:37   ` Avi Kivity
2012-07-17 18:06   ` Stefano Stabellini
2012-07-17 18:06   ` [Qemu-devel] " Stefano Stabellini
2012-07-19 12:34     ` Paolo Bonzini
2012-07-19 12:34     ` [Qemu-devel] " Paolo Bonzini
2012-07-19 15:37       ` Stefano Stabellini
2012-07-19 15:41         ` Anthony PERARD
2012-07-19 15:41         ` Anthony PERARD [this message]
2012-07-19 15:37       ` Stefano Stabellini
2012-07-17 13:30 ` Anthony PERARD
2012-07-17 13:30 ` [PATCH 4/4] xen: Always set the vram dirty during migration Anthony PERARD
2012-07-17 13:30 ` [Qemu-devel] " Anthony PERARD
2012-07-17 18:25   ` Stefano Stabellini
2012-07-17 18:25   ` [Qemu-devel] " Stefano Stabellini
2012-07-17 18:30     ` Stefano Stabellini
2012-07-20 14:11       ` Anthony PERARD
2012-07-20 14:11       ` [Qemu-devel] " Anthony PERARD
2012-07-20 15:47         ` Stefano Stabellini
2012-07-20 15:47         ` [Qemu-devel] " Stefano Stabellini
2012-07-17 18:30     ` 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='CAJJyHjLRLTckfbEZ9KtGV0T=sPoiPefmwZRQeK1pQs4D2gUQuw@mail.gmail.com' \
    --to=anthony.perard@citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.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.