From: Dave Hansen <haveblue@us.ibm.com>
To: Sourav Sen <souravs@india.hp.com>
Cc: 'Greg KH' <greg@kroah.com>,
Matt_Domsch@dell.com,
'Matthew E Tolentino' <matthew.e.tolentino@intel.com>,
linux-ia64@vger.kernel.org,
'Linux Kernel Mailing List' <linux-kernel@vger.kernel.org>
Subject: RE: [2.6.6 PATCH] Exposing EFI memory map
Date: Thu, 13 May 2004 15:32:51 +0000 [thread overview]
Message-ID: <1084462371.1417.20.camel@nighthawk> (raw)
In-Reply-To: <012201c438f4$0cbb6580$39624c0f@india.hp.com>
On Thu, 2004-05-13 at 07:10, Sourav Sen wrote:
> + We're planning on doing this anyway for memory hotplug, so some of the
> + work and ideas are already there. I'd be happy to point you to some
> + past discussions and code on the subject.
Here was my sample implementation of how to export memory areas:
http://sourceforge.net/mailarchive/forum.php?thread_idA20609&forum_id"3
There was at least one other way to do the same thing on the lhms-devel
list. I believe it was some time last month.
-- Dave
prev parent reply other threads:[~2004-05-13 15:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 8:53 [2.6.6 PATCH] Exposing EFI memory map Sourav Sen
2004-05-06 9:30 ` 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:23 ` Luck, Tony
2004-05-06 13:32 ` Sourav Sen
2004-05-06 15:08 ` Bjorn Helgaas
2004-05-06 16:14 ` Tolentino, Matthew E
2004-05-06 16:37 ` Sourav Sen
2004-05-06 16:49 ` Dave Hansen
2004-05-06 16:40 ` Greg KH
2004-05-06 18:47 ` Tolentino, Matthew E
2004-05-06 18:57 ` Dave Hansen
2004-05-06 20:54 ` Tolentino, Matthew E
2004-05-06 21:44 ` [Lhms-devel] " Dave Hansen
2004-05-07 9:57 ` Sourav Sen
2004-05-07 21:49 ` Greg KH
2004-05-11 14:56 ` Sourav Sen
2004-05-11 15:42 ` Dave Hansen
2004-05-12 10:36 ` Sourav Sen
2004-05-12 16:15 ` Dave Hansen
2004-05-13 14:22 ` Sourav Sen
2004-05-13 15:32 ` 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=1084462371.1417.20.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=Matt_Domsch@dell.com \
--cc=greg@kroah.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=souravs@india.hp.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