From: Matthew Wilcox <willy@debian.org>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Matthew Wilcox <willy@debian.org>,
Christoph Hellwig <hch@infradead.org>,
Sourav Sen <souravs@india.hp.com>,
Matt_Domsch@dell.com, matthew.e.tolentino@intel.com,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6.6 PATCH] Exposing EFI memory map
Date: Thu, 06 May 2004 13:27:11 +0000 [thread overview]
Message-ID: <20040506132711.GA2281@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1083845904.3844.2.camel@laptop.fenrus.com>
On Thu, May 06, 2004 at 02:18:24PM +0200, Arjan van de Ven wrote:
> On Thu, 2004-05-06 at 13:59, Matthew Wilcox wrote:
> > On Thu, May 06, 2004 at 11:44:14AM +0100, Christoph Hellwig wrote:
> > > On Thu, May 06, 2004 at 02:22:46PM +0530, Sourav Sen wrote:
> > > > Hi,
> > > >
> > > > The following simple patch creates a read-only file
> > > > "memmap" under <mount point>/firmware/efi/ in sysfs
> > > > and exposes the efi memory map thru it.
> > >
> > > doesn't exactly fit into the one value per file approach, does it?
> >
> > It's not exactly modifiable.
>
> come on, it's the ideal hotplug memory interface ;)
> should we try to unify the memory map exports between architectures
> instead of matching the firmware-of-the-day for each architecture ??
Well, firmware-du-jour is what /sys/firmware/... is for ;-)
I don't have a clear picture of what a hotplug memory interface would look
like; and even if I did, I don't think the EFI memory map is of much help
in that matter.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2004-05-06 13:27 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 [this message]
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
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=20040506132711.GA2281@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=Matt_Domsch@dell.com \
--cc=arjanv@redhat.com \
--cc=hch@infradead.org \
--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