From: "Tolentino, Matthew E" <matthew.e.tolentino@intel.com>
To: "Matt Domsch" <Matt_Domsch@dell.com>,
"Sourav Sen" <souravs@india.hp.com>
Cc: <linux-ia64@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [2.6.6 PATCH] Exposing EFI memory map
Date: Thu, 6 May 2004 09:14:03 -0700 [thread overview]
Message-ID: <D36CE1FCEFD3524B81CA12C6FE5BCAB002FFEB18@fmsmsx406.fm.intel.com> (raw)
> 2) Can the memory map output ever be larger than PAGE_SIZE (lower
> limit is 4KB on x86)? If not, what guarantees that? If so, you need
> your own read mechanism rather than the generic sysfs one.
There are no size guarantees with the EFI memory map. It could
be of various sizes...
matt
next reply other threads:[~2004-05-06 16:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 16:14 Tolentino, Matthew E [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-06 20:54 Tolentino, Matthew E
2004-05-06 18:47 Tolentino, Matthew E
2004-05-06 18:57 ` Dave Hansen
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=D36CE1FCEFD3524B81CA12C6FE5BCAB002FFEB18@fmsmsx406.fm.intel.com \
--to=matthew.e.tolentino@intel.com \
--cc=Matt_Domsch@dell.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®