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

Re: [Xen-devel] [PATCHv1 3/8] x86/xen: discard RAM regions above the maximum reservation

To: David Vrabel <david.vrabel@xxxxxxxxxx>
From: Daniel Kiper <daniel.kiper@xxxxxxxxxx>
Date: Thu, 25 Jun 2015 20:03:35 +0200
Cc: linux-mm@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx
Delivery-date: Thu, 25 Jun 2015 18:03:57 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On Thu, Jun 25, 2015 at 06:10:58PM +0100, David Vrabel wrote:
> During setup, discard RAM regions that are above the maximum
> reservation (instead of marking them as E820_UNUSABLE).  This allows
> hotplug memory to be placed at these addresses.
>
> Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx>

Reviewed-by: Daniel Kiper <daniel.kiper@xxxxxxxxxx>

Daniel

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

References:
- [Xen-devel] [PATCHv1 0/8] mm, xen/balloon: memory hotplug improvements
  - From: David Vrabel
- [Xen-devel] [PATCHv1 3/8] x86/xen: discard RAM regions above the maximum reservation
  - From: David Vrabel

Prev by Date: [Xen-devel] [PATCH v4 00/35] libxl ao abort request (cancellation)
Next by Date: [Xen-devel] [PATCH 02/35] libxl: suspend: switch_logdirty_done takes rc
Previous by thread: [Xen-devel] [PATCHv1 3/8] x86/xen: discard RAM regions above the maximum reservation
Next by thread: [Xen-devel] [PATCHv1 1/8] mm: memory hotplug with an existing resource
Index(es):
- Date
- Thread

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