From: ebiederm@xmission.com (Eric W. Biederman)
To: Matthew Garrett <mjg@redhat.com>
Cc: Takao Indoh <indou.takao@jp.fujitsu.com>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
horms@verge.net.au, nhorman@tuxdriver.com,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, hpa@zytor.com, tglx@linutronix.de,
vgoyal@redhat.com
Subject: Re: [PATCH v2][EFI] Run EFI in physical mode
Date: Thu, 13 Jan 2011 09:16:26 -0800 [thread overview]
Message-ID: <m1bp3kbu6t.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20110113163838.GA21289@srcf.ucam.org> (Matthew Garrett's message of "Thu, 13 Jan 2011 16:38:38 +0000")
Matthew Garrett <mjg@redhat.com> writes:
> We're seeing issues with some Dell hardware when EFI is run in physical
> mode - it seems that Windows uses virtual mode, so the physical path is
> never exercised. I'm not sure that changing the default to physical is
> going to be possible without compatibility issues.
The bootloaders use physical mode, and there shouldn't be a separate
physical vs virtual mode. It should be the same code with or without
relocations applied. At worst we can set virtual address to the
physical address, on buggy boards.
Honestly if the problem is the EFI code is so buggy we can't use it
in physical mode the answer is almost certainly not to use the
buggy EFI code.
The only bits that I don't think have an alternative are the firmware
variable accesses. Which are a nice to have, but not a show stopper
anywhere.
Eric
next prev parent reply other threads:[~2011-01-13 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 23:07 [PATCH v2][EFI] Run EFI in physical mode Takao Indoh
2010-12-14 3:43 ` Kenji Kaneshige
2010-12-14 18:01 ` Takao Indoh
2010-12-16 20:22 ` H. Peter Anvin
2011-01-13 16:38 ` Matthew Garrett
2011-01-13 17:16 ` Eric W. Biederman [this message]
2011-01-13 17:41 ` Matthew Garrett
2010-12-14 22:38 ` Takao Indoh
2010-12-15 23:42 ` Eric W. Biederman
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=m1bp3kbu6t.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=hpa@zytor.com \
--cc=indou.takao@jp.fujitsu.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjg@redhat.com \
--cc=nhorman@tuxdriver.com \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.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