Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

[Xen-devel] [PATCH] x86-64 linux: unmap temporary mappings established f

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] x86-64 linux: unmap temporary mappings established for setup of 1:1 mappings
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Wed, 31 May 2006 15:17:40 +0200
Delivery-date: Wed, 31 May 2006 06:17:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
The temporary mappings needed to set up the 1:1 mappings must be torn down 
after use; otherwise they may trigger the
WARN_ON() in vmap_pte_range() (namely if the chunk allocated to hold kernel and 
initial page tables gets close to or
exceeds 128Mb, or if a sufficiently high mem= argument causes the static 
allocations to grow beyond 128Mb, which in
either case means these mappings extend into the modules area).

Also some minor cleanup.

Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>

Attachment: xenlinux-x86_64-unmap-early.patch
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] x86-64 linux: unmap temporary mappings established for setup of 1:1 mappings, Jan Beulich <=