[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFyDO=a4HvbWYtds3nnBFpwK9oeoptPGcGW-skw3v9jvRg@mail.gmail.com>
Date: Sat, 23 Jul 2016 10:16:45 +0900
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Matt Fleming <matt@...eblueprint.co.uk>
Cc: Andy Lutomirski <luto@...capital.net>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Mario Limonciello <mario_limonciello@...l.com>,
Kees Cook <keescook@...omium.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Matthew Garrett <mjg59@...f.ucam.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
X86 ML <x86@...nel.org>, Josh Triplett <josh@...htriplett.org>,
Peter Jones <pjones@...hat.com>
Subject: Re: [PATCH] x86/boot: Reorganize and clean up the BIOS area
reservation code
On Fri, Jul 22, 2016 at 10:00 PM, Matt Fleming <matt@...eblueprint.co.uk> wrote:
>
> I suppose we could rewrite the page table mapping for those precious
> <1MB regions to coerce the firmware into accessing different pages
> instead of the 1:1 addresses and copy the regions elsewhere. Maybe.
> That assumes we don't hit other firmware bugs though.
.. it also assumes that firmware honors our page tables. Which at a
minimum won't be true for things like SMM, which happens with paging
entirely disabled.
And that's exactly the kind of code that touches some of the memory in
the low 1M region - things like the legacy keyboard state bits in the
low 4kB etc, for crazy old DOS days, iirc.
Linus
Powered by blists - more mailing lists