From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Harper Subject: Re: Re: [PATCH 1/6][RESEND] xen: Add NUMA support to Xen Date: Thu, 18 May 2006 10:30:36 -0500 Message-ID: <20060518153036.GP16876@us.ibm.com> References: <20060501215648.GU16776@us.ibm.com> <25076f74e546e868c489e384ee838e2e@cl.cam.ac.uk> <20060517172124.GO16876@us.ibm.com> <200605172007.49968.ak@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <200605172007.49968.ak@suse.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com, Andi Kleen , Ryan Grimm List-Id: xen-devel@lists.xenproject.org * Andi Kleen [2006-05-17 14:34]: > a hacky halfway house between Linux and Xen, etc). > > > > Is there an equivalent function in Xen for > > linux/arch/x86_64/kernel/e820.c:find_e820_area() ? > > If not it should be easy to port. Most likely you can just use > the x86-64 one after a few s/long/u64/ Yep. Working bad_addr() and needing some help. Where should I be looking to find the bad areas that we need to avoid? Linux's bad_add() avoids < 8000 but I don't if that holds true for Xen. Also initial_images_start to end looks like that should be avoided, as does the frame table. Anything else? -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx (512) 838-9253 T/L: 678-9253 ryanh@us.ibm.com