lkml.org 
[lkml]   [2002]   [Aug]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch] tls-2.5.31-C3

On 12 Aug 2002, Alan Cox wrote:

> > No. The problem is that there are some BIOS's that contain code that (even
> > though they are called in protected mode) load 0x40 into ds and expect to
> > be able to reference stuff ... Causes really interesting OOPSs :-(
>
> Which does mean you can steal the old TLS value and put it back across
> the calls just by changing the TLS data for that process. For that
> matter on Windows emulation I thought Windows also needed 0x40 to be the
> same offset as the BIOS does so can't we leave it hardwired ?

i have no problem with hardwiring it (and excluding it from the TLS
allocation/setting syscalls) - in fact i almost did it that way. The
question is, is the required descriptor format 100% the same for all APM
variants, Wine and Windows and DOS emulators? It would suck if we had a
bad descriptor and also removed the ability of Wine to trap 0x40 access.

but, couldnt APM use its own private GDT for real-mode calls, with 0x40
filled in properly? That would pretty much decouple things.

Ingo

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

\
 
 \ /
  Last update: 2005-03-22 13:27    [W:4.515 / U:0.204 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site