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

Re: [Xen-devel] [RFC 2/3] xen/common: memory: Add support for direct mapped domain in XEMEM_exchange

To: "JulienGrall" <julien.grall@xxxxxxxxxx>
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Tue, 22 Dec 2015 09:18:25 -0700
Cc: Keir Fraser <keir@xxxxxxx>, ian.campbell@xxxxxxxxxx, stefano.stabellini@xxxxxxxxxxxxx, Ian Jackson <ian.jackson@xxxxxxxxxxxxx>, Tim Deegan <tim@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 22 Dec 2015 16:18:39 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

>>> On 17.12.15 at 17:31, <julien.grall@xxxxxxxxxx> wrote:
> Direct mapped domain needs to retrieve the exact same underlying
> physical page when the region is re-populated.

In which case - what sense does it make for such a domain to
exchange memory (the primary purpose of which is to get
_different_ memory populated at the given GFN (range))?

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [RFC 0/3] xen/arm: Support XENMEM_exchange
  - From: Julien Grall
- [Xen-devel] [RFC 2/3] xen/common: memory: Add support for direct mapped domain in XEMEM_exchange
  - From: Julien Grall

Prev by Date: Re: [Xen-devel] [RFC 0/3] xen/arm: Support XENMEM_exchange
Next by Date: Re: [Xen-devel] [RFC 3/3] xen/common: memory: Move steal_page in common code
Previous by thread: [Xen-devel] [RFC 2/3] xen/common: memory: Add support for direct mapped domain in XEMEM_exchange
Next by thread: [Xen-devel] [RFC 3/3] xen/common: memory: Move steal_page in common code
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.