[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Bug#46709: no subject)

From: Marcus Brinkmann
Subject: Bug#46709: no subject)
Date: Sun, 7 Oct 2001 22:20:48 +0200
User-agent: Mutt/1.3.22i

On Sun, Oct 07, 2001 at 03:32:15PM -0400, Roland McGrath wrote:
> The 0xff byte after the bitmap is a terminator byte, check your Intel book
> vol 1, section 9.5.2.

Ah, that explains it.  I have seen the extra byte, and was wondering what I
missed.  I have the Intel books now (got them today), so I can read up more
about this stuff.

BTW, the user tss does not contain such a terminator, so I will add one.

> Your fix is ok, though I would use memset (not that it matters for a
> boot-time only thing).  

Yes, of course that's better.
> According to my Intel book, the other solution is to have no io bitmap
> space at all: missing bits are treated as disallowed if the bitmap is
> shorter than 64k, down to 0.

It also should work to set the io bitmap base address to or beyond the
segment with the same effect.


`Rhubarb is no Egyptian god.' Debian http://www.debian.org brinkmd@debian.org
Marcus Brinkmann              GNU    http://www.gnu.org    marcus@gnu.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]