On 01/25/2012 01:55 PM, Stefano Stabellini wrote:
> >
> > Match on just the MemoryRegion (and match on the object itself, not the
> > name; see xen_register_framebuffer()).
>
> I agree that would be ideal, but how can that work across save/restore?
> Unless we introduce some other kind of identifi
On Wed, 25 Jan 2012, Avi Kivity wrote:
> On 01/19/2012 04:16 PM, Stefano Stabellini wrote:
> > >
> > > If you are migrating to a newer qemu then the could in
> > > principal change, I think.
> >
> > Not unless the implementation of qemu_ram_alloc_from_ptr or
> > find_ram_offset change, but these
On 01/19/2012 04:16 PM, Stefano Stabellini wrote:
> >
> > If you are migrating to a newer qemu then the could in
> > principal change, I think.
>
> Not unless the implementation of qemu_ram_alloc_from_ptr or
> find_ram_offset change, but these are core qemu functions.
Both of these functions wil
On Thu, 19 Jan 2012, Ian Campbell wrote:
> On Thu, 2012-01-19 at 13:08 +, Stefano Stabellini wrote:
> > On Thu, 19 Jan 2012, Ian Campbell wrote:
> > > On Thu, 2012-01-19 at 11:56 +, Stefano Stabellini wrote:
> > > > Write to xenstore any physmap changes so that the hypervisor can be
> > > >
On Thu, 19 Jan 2012, Ian Campbell wrote:
> On Thu, 2012-01-19 at 11:56 +, 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
> /physmap//start_addr
> ?
Yep, t
On Thu, 2012-01-19 at 13:08 +, Stefano Stabellini wrote:
> On Thu, 19 Jan 2012, Ian Campbell wrote:
> > On Thu, 2012-01-19 at 11:56 +, Stefano Stabellini wrote:
> > > Write to xenstore any physmap changes so that the hypervisor can be
> > > aware of them.
> >
> > What is the structure of t
On Thu, 2012-01-19 at 11:56 +, 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
/physmap//start_addr
? Who defines the meaning of original-addr, in particular what
