Re: [Xen-devel] memory_reservation bug?: memory holes

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 11/03/2009 19:50, "Mick Jordan" <Mick.Jordan@xxxxxxx> wrote:

> A related question. I assume it is ok to have holes in the physical
> memory, i.e. call decrease_reservation with a range << max_pfn. In this
> case, what are the rules for the value in the P2M table? Does Xen zero
> out the slot or is it the guest's responsibility?  save/restore must be
> able to determine that a hole exists.

The P2M is completely in your control. Xen doesn't care about it. The
toolstack cares about it only for save/restore -- there I think any invalid
value stuffed in an empty slot would work just fine.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel