From: ebiederm@xmission.com (Eric W. Biederman)
To: "Tolentino, Matthew E" <matthew.e.tolentino@intel.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [CFT][PATCH] 2.6.4-rc1 remove x86 boot page tables
Date: 05 Mar 2004 07:23:38 -0700 [thread overview]
Message-ID: <m1smgnwexh.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <D36CE1FCEFD3524B81CA12C6FE5BCAB002FFE9B4@fmsmsx406.fm.intel.com>
"Tolentino, Matthew E" <matthew.e.tolentino@intel.com> writes:
> >
> > Stupid question. What is efi doing in arch/i386 anyway?
>
> Not a stupid question at all. Despite the recent announcement,
> efi is still working its way into x86 systems. I think that
> decision lies with OEMs. I believe some are already out there...
>
> > All of the to be production efi x86 systems I have heard of support
> > x86-64. So shouldn't it be 64bit calls that we need to worry about?
>
> Not necessarily, although some systems (such as servers) will
> indeed have support for x86-64. I've just started looking at what
> support needs to added for x86-64, in terms of efi, since I
> learned about the announcement via cnet as well... ;-(
Given how many pointers EFI exposes I don't see a way a
dual 32bit/64bit EFI could be made to work. So either EFI needs
to go 64bit on x86, or it will start it's life with crippled. Think
you could find this out?
If EFI is stuck at 32 bits on x86 it should be killed now.
Eric
next prev parent reply other threads:[~2004-03-05 14:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 19:45 Tolentino, Matthew E
2004-03-05 14:23 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-01 18:13 Tolentino, Matthew E
2004-03-02 5:36 ` Eric W. Biederman
2004-03-03 6:47 ` Eric W. Biederman
2004-03-03 8:15 ` Eric W. Biederman
2004-03-01 7:32 Eric W. Biederman
2004-03-01 19:05 ` Dave Hansen
2004-03-02 5:29 ` Eric W. Biederman
2004-03-02 6:47 ` H. Peter Anvin
2004-03-02 17:56 ` Eric W. Biederman
2004-03-02 9:21 ` H. Peter Anvin
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=m1smgnwexh.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@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®