All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	QEMU-devel <qemu-devel@nongnu.org>,
	Xen Devel <xen-devel@lists.xen.org>
Subject: Re: [Qemu-devel] [PATCH V4 4/5] exec, memory: Call to xen_modified_memory.
Date: Tue, 02 Oct 2012 12:25:35 +0200	[thread overview]
Message-ID: <506AC11F.1030402@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1210011134020.29232@kaball.uk.xensource.com>

On 10/01/2012 12:36 PM, Stefano Stabellini wrote:
> On Thu, 27 Sep 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>
> 
> If I am not mistaken, this is the last patch that needs reviewing.
> Avi, are you OK with it?
> 
> 
> 
>>  exec.c   | 1 +
>>  memory.c | 2 ++
>>  2 files changed, 3 insertions(+)
>> 
>> diff --git a/exec.c b/exec.c
>> index 366684c..1114a09 100644
>> --- a/exec.c
>> +++ b/exec.c
>> @@ -3427,6 +3427,7 @@ static void invalidate_and_set_dirty(target_phys_addr_t addr,
>>          /* set dirty bit */
>>          cpu_physical_memory_set_dirty_flags(addr, (0xff & ~CODE_DIRTY_FLAG));
>>      }
>> +    xen_modified_memory(addr, length);
>>  }
>>  
>>  void cpu_physical_memory_rw(target_phys_addr_t addr, uint8_t *buf,
>> diff --git a/memory.c b/memory.c
>> index 4f3ade0..015c544 100644
>> --- a/memory.c
>> +++ b/memory.c
>> @@ -19,6 +19,7 @@
>>  #include "bitops.h"
>>  #include "kvm.h"
>>  #include <assert.h>
>> +#include "hw/xen.h"
>>  
>>  #define WANT_EXEC_OBSOLETE
>>  #include "exec-obsolete.h"
>> @@ -1077,6 +1078,7 @@ void memory_region_set_dirty(MemoryRegion *mr, target_phys_addr_t addr,
>>                               target_phys_addr_t size)
>>  {
>>      assert(mr->terminates);
>> +    xen_modified_memory(mr->ram_addr + addr, size);
>>      return cpu_physical_memory_set_dirty_range(mr->ram_addr + addr, size, -1);
>>  }

I would prefer this bit pushed into cpu_physical_set_dirty_range().
Possibly the first bit too?



-- 
error compiling committee.c: too many arguments to function

  parent reply	other threads:[~2012-10-02 10:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27 11:12 [Qemu-devel] [PATCH V4 0/5] Xen, introducing dirty log for migration Anthony PERARD
2012-09-27 11:12 ` [PATCH V4 1/5] QMP, Introduce xen-set-global-dirty-log command Anthony PERARD
2012-09-27 11:12 ` [Qemu-devel] " Anthony PERARD
2012-09-27 11:12 ` [Qemu-devel] [PATCH V4 2/5] xen: Introduce xen_modified_memory Anthony PERARD
2012-09-27 11:12   ` Anthony PERARD
2012-10-01 10:32   ` [Qemu-devel] " Stefano Stabellini
2012-10-01 10:32   ` Stefano Stabellini
2012-09-27 11:12 ` [Qemu-devel] [PATCH V4 3/5] exec: Introduce helper to set dirty flags Anthony PERARD
2012-09-27 11:12 ` Anthony PERARD
2012-09-27 11:12 ` [Qemu-devel] [PATCH V4 4/5] exec, memory: Call to xen_modified_memory Anthony PERARD
2012-09-27 11:12   ` Anthony PERARD
2012-10-01 10:36   ` Stefano Stabellini
2012-10-01 10:36   ` [Qemu-devel] " Stefano Stabellini
2012-10-02 10:25     ` Avi Kivity
2012-10-02 10:25     ` Avi Kivity [this message]
2012-10-02 16:16       ` Anthony PERARD
2012-10-02 16:16       ` [Qemu-devel] " Anthony PERARD
2012-10-02 16:20         ` Avi Kivity
2012-10-02 16:20         ` [Qemu-devel] " Avi Kivity
2012-09-27 11:12 ` [Qemu-devel] [PATCH V4 5/5] xen: Set the vram dirty when an error occur Anthony PERARD
2012-10-01 10:33   ` Stefano Stabellini
2012-10-01 10:33   ` [Qemu-devel] " Stefano Stabellini
2012-09-27 11:12 ` 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=506AC11F.1030402@redhat.com \
    --to=avi@redhat.com \
    --cc=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.