linux-kernel - Re: [PATCH V3 3/4] PCI: Add support for non-BAR ROMs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120905134454.GD16399@srcf.ucam.org>
Date:	Wed, 5 Sep 2012 14:44:55 +0100
From:	Matthew Garrett <mjg@...hat.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Don Dutile <ddutile@...hat.com>, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org, linux-efi@...r.kernel.org,
	mfleming@...el.com, dwmw2@...radead.org, bhelgaas@...gle.com
Subject: Re: [PATCH V3 3/4] PCI: Add support for non-BAR ROMs

On Wed, Sep 05, 2012 at 02:30:10PM +0100, Alan Cox wrote:
> On Wed, 5 Sep 2012 14:20:07 +0100
> Matthew Garrett <mjg@...hat.com> wrote:
> > We've no good way of knowing what the firmware's giving us - we copy it 
> > to RAM in the EFI init process, so by the time we're here it certainly 
> > shouldn't be on the PCI bus.
> 
> In which case how do you know that physical address you have been given
> actually has a mapping in kernel virtual space. It seems like it ought to
> be getting an ioremap in that case ?
> 
> phys_to_virt is not valid for arbitary addresses.

The pages are allocated as EFI_LOADER_DATA, and that gets mapped as 
E820_RAM.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/