From: Dave Hansen <haveblue@us.ibm.com>
To: Matthew E Tolentino <matthew.e.tolentino@intel.com>
Cc: Sourav Sen <souravs@india.hp.com>,
"HELGAAS,BJORN (HP-Ft. Collins)" <bjorn_helgaas@am.exch.hp.com>,
Matt Domsch <Matt_Domsch@dell.com>,
linux-ia64@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Luck, Tony" <tony.luck@intel.com>,
lhms <lhms-devel@lists.sourceforge.net>
Subject: Re: [Lhms-devel] RE: [2.6.6 PATCH] Exposing EFI memory map
Date: Thu, 06 May 2004 14:44:38 -0700 [thread overview]
Message-ID: <1083879878.2811.971.camel@nighthawk> (raw)
In-Reply-To: <D36CE1FCEFD3524B81CA12C6FE5BCAB002FFEB1F@fmsmsx406.fm.intel.com>
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
prev parent reply other threads:[~2004-05-06 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 20:54 [2.6.6 PATCH] Exposing EFI memory map Tolentino, Matthew E
2004-05-06 21:44 ` Dave Hansen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1083879878.2811.971.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=Matt_Domsch@dell.com \
--cc=bjorn_helgaas@am.exch.hp.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=souravs@india.hp.com \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox