[Top][All Lists]
[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: |
Ian Campbell |
Subject: |
Re: [Qemu-devel] [Xen-devel] [PATCH v3 5/6] xen: record physmap changes to xenstore |
Date: |
Thu, 19 Jan 2012 14:04:19 +0000 |
On Thu, 2012-01-19 at 13:08 +0000, Stefano Stabellini wrote:
> 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.
If you are migrating to a newer qemu then the <original-addr> could in
principal change, I think.
> We could add some additional info to better identify the physmap entry,
> probably the best we could use is the memory_region name.
And/Or the PCI BDF + BAR?
Ian.
- [Qemu-devel] [PATCH v3 0/6] save/restore on Xen, Stefano Stabellini, 2012/01/19
- [Qemu-devel] [PATCH v3 5/6] xen: record physmap changes to xenstore, Stefano Stabellini, 2012/01/19
- Re: [Qemu-devel] [Xen-devel] [PATCH v3 5/6] xen: record physmap changes to xenstore, Ian Campbell, 2012/01/19
- Re: [Qemu-devel] [Xen-devel] [PATCH v3 5/6] xen: record physmap changes to xenstore, Stefano Stabellini, 2012/01/19
- Re: [Qemu-devel] [Xen-devel] [PATCH v3 5/6] xen: record physmap changes to xenstore,
Ian Campbell <=
- Re: [Qemu-devel] [Xen-devel] [PATCH v3 5/6] xen: record physmap changes to xenstore, Stefano Stabellini, 2012/01/19
- Re: [Qemu-devel] [Xen-devel] [PATCH v3 5/6] xen: record physmap changes to xenstore, Avi Kivity, 2012/01/25
- Re: [Qemu-devel] [Xen-devel] [PATCH v3 5/6] xen: record physmap changes to xenstore, Stefano Stabellini, 2012/01/25
- Re: [Qemu-devel] [Xen-devel] [PATCH v3 5/6] xen: record physmap changes to xenstore, Avi Kivity, 2012/01/25
[Qemu-devel] [PATCH v3 1/6] vl.c: do not save the RAM state when Xen is enabled, Stefano Stabellini, 2012/01/19
[Qemu-devel] [PATCH v3 2/6] xen mapcache: check if memory region has moved., Stefano Stabellini, 2012/01/19
[Qemu-devel] [PATCH v3 6/6] xen: change memory access behavior during migration., Stefano Stabellini, 2012/01/19
[Qemu-devel] [PATCH v3 3/6] Set runstate to INMIGRATE earlier, Stefano Stabellini, 2012/01/19
[Qemu-devel] [PATCH v3 4/6] cirrus_vga: do not reset videoram on resume, Stefano Stabellini, 2012/01/19