qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [Xen-devel] [PATCH v3 5/6] xen: record physmap changes


From: Stefano Stabellini
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH v3 5/6] xen: record physmap changes to xenstore
Date: Thu, 19 Jan 2012 13:08:00 +0000
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)

On Thu, 19 Jan 2012, Ian Campbell wrote:
> On Thu, 2012-01-19 at 11:56 +0000, Stefano Stabellini wrote:
> > Write to xenstore any physmap changes so that the hypervisor can be
> > aware of them.
> 
> What is the structure of the xenstore values? Looks like 
>       <domid>/physmap/<original-addr>/start_addr <new-addr>
> ?

Yep, that is the structure


> Who defines the meaning of original-addr, in particular what happens
> if it the original-addr for a device changes in a N->N+1 migration? What
> happens if things overlap or if a subsequent call only updates part of a
> previously moved mapping?

In practice it cannot happen because on restore Qemu is going to emulate
the same set of devices it was emulating before.
The original address is not going to change if the devices and the
amount of guest memory stay the same.

We could add some additional info to better identify the physmap entry,
probably the best we could use is the memory_region name.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]