From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263104AbUEFWBh (ORCPT ); Thu, 6 May 2004 18:01:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263107AbUEFWBh (ORCPT ); Thu, 6 May 2004 18:01:37 -0400 Received: from e32.co.us.ibm.com ([32.97.110.130]:57487 "EHLO e32.co.us.ibm.com") by vger.kernel.org with ESMTP id S263104AbUEFWBg (ORCPT ); Thu, 6 May 2004 18:01:36 -0400 Subject: Re: [Lhms-devel] RE: [2.6.6 PATCH] Exposing EFI memory map From: Dave Hansen To: Matthew E Tolentino Cc: Sourav Sen , "HELGAAS,BJORN (HP-Ft. Collins)" , Matt Domsch , linux-ia64@vger.kernel.org, Linux Kernel Mailing List , "Luck, Tony" , lhms In-Reply-To: References: Content-Type: text/plain Message-Id: <1083879878.2811.971.camel@nighthawk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 06 May 2004 14:44:38 -0700 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2004-05-06 at 13:54, Tolentino, Matthew E wrote: > > > Interesting. What does ppc64 do with the memmap after that? > > > > This doesn't even concern mem_map yet. The userspace ppc64 hotplug > > tools actually write into the "OpenFirmware" tree from > > userspace, after > > a hotplug happens. This is partly because all of the ppc64 hotplug > > operations happen in userspace as it stands now. > > Umm.. my mistake, I meant the memory map passed up by the firmware, > not THE mem_map. ;-) Sorry for the ppc64 tangent, ia64 list people... :) I'm not quite sure what's it's used for. I *think* there's a node in each of the fake OpenFirmware tree directories that exports a magic resource tag that can identify the memory when it's handed back to the hypervisor. We need this number exported to userspace, because we basically make the hypervisor calls from there. It's safe to say that I'd prefer this method be revised at some point in the future. -- Dave