All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	QEMU-devel <qemu-devel@nongnu.org>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	Avi Kivity <avi@redhat.com>,
	Anthony Perard <anthony.perard@citrix.com>,
	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:37:06 +0100	[thread overview]
Message-ID: <alpine.DEB.2.02.1207191624430.23783@kaball.uk.xensource.com> (raw)
In-Reply-To: <5007FECE.9090305@redhat.com>

On Thu, 19 Jul 2012, Paolo Bonzini wrote:
> Il 17/07/2012 20:06, Stefano Stabellini ha scritto:
> > On Tue, 17 Jul 2012, Anthony PERARD wrote:
> >> This patch add some calls to xen_modified_memory to notify Xen about dirtybits
> >> during migration.
> >>
> >> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> >> ---
> >>  exec.c   |    4 ++++
> >>  memory.c |    2 ++
> >>  2 files changed, 6 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/exec.c b/exec.c
> >> index c9fa17d..9f7a4f7 100644
> >> --- a/exec.c
> >> +++ b/exec.c
> >> @@ -3438,6 +3438,7 @@ void cpu_physical_memory_rw(target_phys_addr_t addr, uint8_t *buf,
> >>                      cpu_physical_memory_set_dirty_flags(
> >>                          addr1, (0xff & ~CODE_DIRTY_FLAG));
> >>                  }
> >> +                xen_modified_memory(addr1, TARGET_PAGE_SIZE);
> >>                  qemu_put_ram_ptr(ptr);
> >>              }
> >>          } else {
> >> @@ -3623,6 +3624,7 @@ void cpu_physical_memory_unmap(void *buffer, target_phys_addr_t len,
> >>      if (buffer != bounce.buffer) {
> >>          if (is_write) {
> >>              ram_addr_t addr1 = qemu_ram_addr_from_host_nofail(buffer);
> >> +            xen_modified_memory(addr1, access_len);
> >>              while (access_len) {
> >>                  unsigned l;
> >>                  l = TARGET_PAGE_SIZE;
> > 
> > You need to add xen_modified_memory in cpu_physical_memory_map, rather
> > than cpu_physical_memory_unmap.
> 
> No, adding it to map is wrong, because the RAM save routine can migrate
> (and mark as non-dirty) the read buffers _before_ the device models have
> written to them.

You are correct, in fact this looks like a bug in the current qemu-xen
(non-upstream) codebase too!

What I think that we should do is only mark the memory as dirty
if(is_write) in cpu_physical_memory_unmap, like you are doing in this
patch.

Anthony, can you write a patch to change the behavior in
qemu-xen-traditional too?

  reply	other threads:[~2012-07-19 15:39 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 [this message]
2012-07-19 15:41         ` Anthony PERARD
2012-07-19 15:41         ` Anthony PERARD
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=alpine.DEB.2.02.1207191624430.23783@kaball.uk.xensource.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=aliguori@us.ibm.com \
    --cc=anthony.perard@citrix.com \
    --cc=avi@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=pbonzini@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 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.