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

Re: [Xen-devel] [PATCH 10/13] xen: check pre-allocated page tables for conflict with memory map

To: Juergen Gross <jgross@xxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, konrad.wilk@xxxxxxxxxx, david.vrabel@xxxxxxxxxx, boris.ostrovsky@xxxxxxxxxx
From: David Vrabel <dvrabel@xxxxxxxxxx>
Date: Thu, 19 Feb 2015 17:37:26 +0000
Delivery-date: Thu, 19 Feb 2015 17:37:37 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>



On 18/02/2015 06:52, Juergen Gross wrote:

Check whether the page tables built by the domain builder are at
memory addresses which are in conflict with the target memory map.
If this is the case just panic instead of running into problems
later.


Again, what ensures this never actually happens?

David

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

Follow-Ups:
- Re: [Xen-devel] [PATCH 10/13] xen: check pre-allocated page tables for conflict with memory map
  - From: Juergen Gross

References:
- [Xen-devel] [PATCH 00/13] xen: support pv-domains larger than 512GB
  - From: Juergen Gross

Prev by Date: Re: [Xen-devel] [PATCH 09/13] xen: check for kernel memory conflicting with memory layout
Next by Date: Re: [Xen-devel] [PATCH v4 18/29] Ovmf/Xen: move XenBusDxe hypercall code to separate library
Previous by thread: Re: [Xen-devel] [PATCH 13/13] xen: allow more than 512 GB of RAM for 64 bit pv-domains
Next by thread: Re: [Xen-devel] [PATCH 10/13] xen: check pre-allocated page tables for conflict with memory map
Index(es):
- Date
- Thread

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