From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH 3 of 4] KEXEC: Allocate crash structures in low memory Date: Fri, 09 Mar 2012 16:30:25 +0000 Message-ID: References: <4F5A2EBA.6090702@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F5A2EBA.6090702@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 09/03/2012 16:24, "Andrew Cooper" wrote: > On 09/03/12 15:52, Keir Fraser wrote: >> On 09/03/2012 14:42, "Andrew Cooper" wrote: >> >>> On 64bit Xen with 32bit dom0 and crashkernel, xmalloc'ing items such >>> as the CPU crash notes will go into the xenheap, which tends to be in >>> upper memory. This causes problems on machines with more than 64GB >>> (or 4GB if no PAE support) of ram as the crashkernel physically cant >>> access the crash notes. >> Why wouldn't you run a 64-bit crashkernel? >> >> -- Keir > > There is certainly an argument to be made along those lines, and I > personally lean to that side of the argument. However, as our dom0 > kernel is 32bits, there is no substantial testing of the drivers built > for 64bit. Yes, I suppose this sounds pretty reasonable. -- Keir