mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Siarhei Liakh <sliakh.lkml@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	Arjan van de Ven <arjan@infradead.org>,
	Andi Kleen <andi@firstfloor.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Ingo Molnar <mingo@elte.hu>, James Morris <jmorris@namei.org>,
	Andrew Morton <akpm@linux-foundation.org>, Andi Kleen <ak@muc.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-cris-kernel@axis.com, Roland Dreier <rdreier@cisco.com>
Subject: Re: [PATCH] x86: Reducing footprint of BIOS32 service mappings
Date: Sun, 19 Jul 2009 21:02:47 -0400	[thread overview]
Message-ID: <817ecb6f0907191802g4fd0970dj9e8327d44cf7e5a@mail.gmail.com> (raw)
In-Reply-To: <4A63C00A.2070805@zytor.com>

For now I have only tested it on my home system and qemu. Actuallym in
both cases, I had to compile kernel with only CONFIG_PCI_GOBIOS=y,
since Kernel prefers other ways to access PCI when possible (with
CONFIG_PCI_GOANY=y).

On Sun, Jul 19, 2009 at 8:53 PM, H. Peter Anvin<hpa@zytor.com> wrote:
> Siarhei Liakh wrote:
>> According to BIOS32 specification
>> (http://members.datafast.net.au/dft0802/specs/bios32.pdf), at most two
>> pages per BIOS32 service should be set executable and no pages need to
>> be writeable. This patch modifies bios32_service() to set proper page
>> access permissions at time of service discovery, as described in the
>> specification.
>> Further, hardcoded protection of memory area between 640k to 1Mb have
>> been removed from static_protections(), since only pages mentioned
>> above need to be executable, not whole BIOS region.
>>
>> The patch have been developed for Linux 2.6.30 x86 by Siarhei Liakh
>> <sliakh.lkml@gmail.com> and Xuxian Jiang <jiang@cs.ncsu.edu>.
>>
>
> Specifications mean little in the BIOS space, unfortunately.  Do we have
> any notion about how many machines this has been tested on?
>
>        -hpa
>
> --
> H. Peter Anvin, Intel Open Source Technology Center
> I work for Intel.  I don't speak on their behalf.
>
>

      reply	other threads:[~2009-07-20  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20  0:42 Siarhei Liakh
2009-07-20  0:53 ` H. Peter Anvin
2009-07-20  1:02   ` Siarhei Liakh [this message]

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=817ecb6f0907191802g4fd0970dj9e8327d44cf7e5a@mail.gmail.com \
    --to=sliakh.lkml@gmail.com \
    --cc=ak@muc.de \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=arjan@infradead.org \
    --cc=hpa@zytor.com \
    --cc=jmorris@namei.org \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdreier@cisco.com \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    /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®