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

Re: [Xen-devel] [PATCH v2 2/4] x86/e820: do not fixup memmap in copy_e820_map

To: Roger Pau Monne <roger.pau@xxxxxxxxxx>
From: Wei Liu <wei.liu2@xxxxxxxxxx>
Date: Wed, 2 Jan 2019 12:44:19 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx, Wei Liu <wei.liu2@xxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Delivery-date: Wed, 02 Jan 2019 12:45:02 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Fri, Dec 28, 2018 at 01:04:02PM +0100, Roger Pau Monne wrote:
> And instead use the newly introduced e820_remove_range helper to
> remove any RAM region from the low 1MB VGA/ROM region afterwards.
> 
> No functional change intended.
> 
> Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>

Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

Prev by Date: [Xen-devel] [PATCH] libxc/altp2m: clean up TABs
Next by Date: Re: [Xen-devel] [PATCH v2 3/4] x86/e820: assume memmap provided when booted virtualized is correct
Previous by thread: [Xen-devel] [PATCH] libxc/altp2m: clean up TABs
Next by thread: Re: [Xen-devel] [PATCH v2 2/4] x86/e820: do not fixup memmap in copy_e820_map
Index(es):
- Date
- Thread

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