Linus Torvalds wrote:
On Mon, 7 Nov 2005, Zachary Amsden wrote:
Both the APM BIOS and PnP BIOS code use a segment hack to simulate real
mode selector 0x40 (which points to the BIOS data area at 0x00400 in
real mode). Several broken BIOSen use selector 0x40 as if they were
running in real mode, which we make work by faking up selector 0x40 in
the GDT to point to physical memory starting at 0x400. We limit the
access to the remainder of this physical page using a byte granular
limit. Rather than have this tricky code in multiple places, it makes
sense to define it in one place, and the GDT makes a very convenient
place for it. Use GDT entry 4 as the BAD_BIOS_CACHE segment.
I'd much rather use entry 8 instead, which should just automatically mean
that selector 0x40 _always_ points to virtual address 0x400. No switching
etc..
Isn't this what Wine already has to work around, or something?
I have answers now to the questions:
Wine has to support allocating thread pointers for NT processes in
ntdll, so it needs a way to allocate descriptors. It doesn't seem to
care if they are LDT or GDT descriptors.
Ingo, can we move the TLS selectors upwards, or does user space perhaps
know about the current TLS layout? Wine in particular may well know ;(
It does not know. And DOSemu appears to only use LDT. GDT is used to
allocate a global thread area for Wine, but it has a fallback mechanism
that appears to have been built from the start to deal with varying
thread selectors rather than a fixed notion (as GDT TLS segments are not
available on 2.4). Rather convenient.
Now the million dollar question is : who uses three TLS segments? Wine
appears to use glibc, private, and I have no idea what other software
makes use of this. If only two thread selectors were needed, then this
does the trick. Or we could rebase the selectors down to 0x20-0x30.
* ------- start of TLS (Thread-Local Storage) segments:
*
* 6 - TLS segment #1 [ glibc's TLS segment ]
* 7 - TLS segment #2 [ Wine's %fs Win32 segment ]
* 8 - BIOS real mode segment
Zach
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]