From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Alexandre Julliard <julliard@winehq.com>,
Luca Barbieri <ldb@ldb.ods.org>
Subject: Re: [patch] tls-2.5.30-A1
Date: 07 Aug 2002 23:01:34 +0100 [thread overview]
Message-ID: <1028757694.26935.9.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0208071115290.4961-100000@home.transmeta.com>
On Wed, 2002-08-07 at 19:33, Linus Torvalds wrote:
> - keep the TLS entries contiguous, and make sure that segment 0040 (ie
> GDT entry #8) is available to a TLS entry, since if I remember
> correctly, that one is also magical for old Windows binaries for all
> the wrong reasons (ie it was some system data area in DOS and in
> Windows 3.1)
Lots of BIOSes (a million monkeys bashing on typewriters will write
something that passes some BIOS vendor QA in about 2 seconds) illegally
assume that 0040: points at the BIOS data segment 0040 when making APM32
calls. Sufficient that Windows makea it so and its never going to get
corrected.
> Then, for double extra bonus points somebody should look into whether
> those damn PnP BIOS segments could be simply made to be TLS segments
> during module init. I don't know if that PnP stuff is required later or
> not.
PnPBIOS has to rewrite segments as it goes for data passing. It doesnt
really matter where you stuff them though.
next prev parent reply other threads:[~2002-08-07 20:43 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 18:10 Ingo Molnar
2002-08-07 18:33 ` Linus Torvalds
2002-08-07 18:43 ` Stephen Rothwell
2002-08-07 18:57 ` Linus Torvalds
2002-08-07 19:40 ` Alexandre Julliard
2002-08-07 19:31 ` Ingo Molnar
2002-08-07 19:49 ` Alexandre Julliard
2002-08-07 22:01 ` Alan Cox [this message]
2002-08-07 22:36 ` Luca Barbieri
2002-08-07 22:54 ` Ingo Molnar
2002-08-07 23:21 ` Luca Barbieri
2002-08-07 23:35 ` DMA Problems with Intel 845 Chipset and Northwood CPU Mark Cuss
2002-08-08 0:58 ` John L. Korpi
2002-08-08 16:12 ` Mark Cuss
2002-08-11 21:46 ` [patch] tls-2.5.31-C3 Ingo Molnar
2002-08-12 7:34 ` Stephen Rothwell
2002-08-12 10:07 ` Ingo Molnar
2002-08-12 8:23 ` Stephen Rothwell
2002-08-12 10:08 ` Alan Cox
2002-08-12 10:49 ` Ingo Molnar
2002-08-12 10:34 ` Alan Cox
2002-08-12 12:17 ` Ingo Molnar
2002-08-12 11:47 ` Alan Cox
2002-08-12 12:55 ` Ingo Molnar
2002-08-12 12:29 ` Alan Cox
2002-08-12 10:35 ` Alan Cox
2002-08-12 13:10 ` Kasper Dupont
2002-08-12 15:20 ` Ingo Molnar
2002-08-12 14:46 ` Stephen Rothwell
2002-08-12 12:18 ` Luca Barbieri
2002-08-12 15:12 ` Ingo Molnar
2002-08-12 13:43 ` Luca Barbieri
2002-08-12 15:57 ` Ingo Molnar
2002-08-12 14:17 ` Luca Barbieri
2002-08-12 15:53 ` [patch] tls-2.5.31-D3 Ingo Molnar
2002-08-12 16:13 ` [patch] tls-2.5.31-D4 Ingo Molnar
2002-08-12 14:32 ` Luca Barbieri
2002-08-12 17:06 ` [patch] tls-2.5.31-D5 Ingo Molnar
2002-08-12 15:21 ` Jakub Jelinek
2002-08-12 17:41 ` Ingo Molnar
2002-08-12 15:54 ` Luca Barbieri
2002-08-12 18:03 ` [patch] tls-2.5.31-D9 Ingo Molnar
2002-08-13 1:50 ` [patch] tls-2.5.31-D5 Alexandre Julliard
2002-08-12 17:24 ` [patch] tls-2.5.31-D7 Ingo Molnar
2002-08-12 15:45 ` Christoph Hellwig
2002-08-07 19:02 ` [patch] tls-2.5.30-A1 Christoph Hellwig
2002-08-08 12:25 ` Jamie Lokier
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=1028757694.26935.9.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=julliard@winehq.com \
--cc=ldb@ldb.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.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®