From: "Tolentino, Matthew E" <matthew.e.tolentino@intel.com>
To: "Dave Hansen" <haveblue@us.ibm.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: [2.6.6 PATCH] Exposing EFI memory map
Date: Thu, 6 May 2004 13:54:36 -0700 [thread overview]
Message-ID: <D36CE1FCEFD3524B81CA12C6FE5BCAB002FFEB1F@fmsmsx406.fm.intel.com> (raw)
> > 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. ;-)
> Actually, I was thinking that we'd just allocate the
> kobjects, and note
> the presence of the memory in the nonlinear phys_section table. Then,
> when we online it, we can decide where it's mapped, what zone
> to put it
> in, and where to get the mem_map space from. I think that approach
> gives the best flexibility.
Yes, indeed.
matt
next reply other threads:[~2004-05-06 20:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 20:54 Tolentino, Matthew E [this message]
2004-05-06 21:44 ` [Lhms-devel] " Dave Hansen
-- strict thread matches above, loose matches on Subject: below --
2004-05-06 18:47 Tolentino, Matthew E
2004-05-06 18:57 ` Dave Hansen
2004-05-06 16:14 Tolentino, Matthew E
2004-05-06 13:23 Luck, Tony
2004-05-06 9:18 Sourav Sen
2004-05-06 8:52 Sourav Sen
2004-05-06 10:44 ` Christoph Hellwig
2004-05-06 11:59 ` Matthew Wilcox
2004-05-06 12:18 ` Arjan van de Ven
2004-05-06 13:27 ` Matthew Wilcox
2004-05-06 14:00 ` Dave Hansen
2004-05-06 14:09 ` Arjan van de Ven
2004-05-06 14:09 ` Christoph Hellwig
2004-05-06 12:46 ` Matt Domsch
2004-05-06 13:20 ` Sourav Sen
2004-05-06 15:08 ` Bjorn Helgaas
2004-05-06 16:25 ` Sourav Sen
2004-05-06 16:49 ` Dave Hansen
2004-05-06 16:40 ` Greg KH
2004-05-07 9:45 ` Sourav Sen
2004-05-07 21:49 ` Greg KH
2004-05-11 14:44 ` Sourav Sen
2004-05-11 15:42 ` Dave Hansen
2004-05-12 10:24 ` Sourav Sen
2004-05-12 16:15 ` Dave Hansen
2004-05-13 14:10 ` Sourav Sen
2004-05-13 15:32 ` Dave Hansen
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=D36CE1FCEFD3524B81CA12C6FE5BCAB002FFEB1F@fmsmsx406.fm.intel.com \
--to=matthew.e.tolentino@intel.com \
--cc=Matt_Domsch@dell.com \
--cc=bjorn_helgaas@am.exch.hp.com \
--cc=haveblue@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®