mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: castet.matthieu@free.fr
To: linux-kernel@vger.kernel.org
Cc: Siarhei Liakh <sliakh.lkml@gmail.com>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [tip:x86/mm] x86, mm: Set first MB as RW+NX
Date: Sat, 12 Jun 2010 22:04:41 +0200	[thread overview]
Message-ID: <1276373081.4c13e859a61fc@imp.free.fr> (raw)
In-Reply-To: <1276360709.4c13b80507f8b@imp.free.fr>

Selon castet.matthieu@free.fr:

> hi,
>
> > Special accommodations have been made for BIOS32/PCI BIOS services:
> > 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.
> From my understanding only the service directory take 2 pages.
>
> The no info for the pci service :
> - the length field could be used to find the number of page it takes.
> - could we assume data ro ?
>

http://members.datafast.net.au/dft0802/specs/bios21.pdf got all info for pci
bios [1].
So I was right : we shouldn't assume pci bios routine take only 2 pages, but use
the length parameter.


Matthieu



[1]
The 32-bit PCI BIOS functions must be accessed using CALL FAR. The CS and DS
descriptors must be setup to encompass the physical addresses specified by the
Base and
Length parameters returned by the BIOS32 Service Directory. The CS and DS
descriptors must have the same base. The calling environment must allow access
to IO
space and provide at least 1K of stack space. Platform BIOS writers must assume
that CS
is execute-only and DS is read-only.

  reply	other threads:[~2010-06-12 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-12 16:38 castet.matthieu
2010-06-12 20:04 ` castet.matthieu [this message]
2010-06-17  0:36   ` Siarhei Liakh
  -- strict thread matches above, loose matches on Subject: below --
2010-06-07  1:00 [PATCH 2/4 V4] [tip:x86/mm] " Siarhei Liakh
2010-06-11 22:55 ` [tip:x86/mm] x86, mm: " tip-bot for Siarhei Liakh
2010-06-12 13:00   ` Ingo Molnar

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=1276373081.4c13e859a61fc@imp.free.fr \
    --to=castet.matthieu@free.fr \
    --cc=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sliakh.lkml@gmail.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

all inboxes | Powered by JetHome®