From: Matthew Garrett <mjg59@srcf.ucam.org>
To: rwright@hp.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] function probe_roms accessing improper addresses on UEFI systems
Date: Thu, 4 Oct 2012 20:22:56 +0100 [thread overview]
Message-ID: <20121004192256.GA6521@srcf.ucam.org> (raw)
In-Reply-To: <201210032353.q93NrkNi018443@filesys1.fc.hp.com>
On Wed, Oct 03, 2012 at 05:53:46PM -0600, Randy Wright wrote:
> The following proposed patch takes advantage of the fact that on EFI
> systems, the memory map provides a better description of the physical
> space than on pre-EFI legacy systems. If the efi_enabled state variable
> indicates the kernel is running on an UEFI system, the patch will use
> information from the UEFI memory map so as not to access addresses that
> should avoided according to the UEFI specification.
This turns out to be awkward. Some (mostly older) EFI platforms still
only provide the video ROM through the 0xc0000 window, and that's
sometimes needed even if the platform isn't using int10 for anything
(for instance, some Intel graphics machines only provide the VBT through
the video ROM and don't provide that via the PCI BAR). And, of course,
they have an EFI memory map that just shows a hole there.
So we can't distinguish between the two cases easily. The only thing I
can think of would be to push that policy out to the graphics drivers
and have them trigger a scan only if they can't get the required
information from any other source. I suspect that this patch as is would
break graphics on a reasonable number of EFI platforms.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2012-10-04 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 23:53 [PATCH RFC] function probe_roms accessing improper addresses on UEFI systems Randy Wright
2012-10-04 19:22 ` Matthew Garrett [this message]
2012-10-10 4:31 ` [PATCH RFC] function probe_roms accessing improper addresses Randy Wright
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=20121004192256.GA6521@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rwright@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;
as well as URLs for NNTP newsgroup(s).