From: Luca Barbieri <ldb@ldb.ods.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jakub Jelinek <jakub@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
Linux-Kernel ML <linux-kernel@vger.kernel.org>,
Alexandre Julliard <julliard@winehq.com>
Subject: Re: [patch] tls-2.5.31-D5
Date: 12 Aug 2002 17:54:44 +0200 [thread overview]
Message-ID: <1029167684.4531.88.camel@ldb> (raw)
In-Reply-To: <Pine.LNX.4.44.0208121939260.22188-100000@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
> well, i think i have to agree ... if it wasnt for Wine's 0x40 descriptor.
> But it certainly does not come free. We could have 3 TLS entries (0x40
> will be the last entry), and the copying cost is 9 cycles. (compared to 6
> cycles in the 2 entries case.) Good enough?
Or we could leave 0x40 fixed to 0x400 and use only 2.
This loses flexibility but anyway the only 2 apps that could use it are
dosemu and wine and I think that they already need to have it mapped at
0x400 for vm86 (no one uses 16-bit DLLs anymore).
Of course this is only valid if Win32 doesn't use it because otherwise
we would lose the ability to do null-pointer checking in programs using
Win32 DLLs (e.g. mplayer).
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-08-12 15:51 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 18:10 [patch] tls-2.5.30-A1 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
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 [this message]
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=1029167684.4531.88.camel@ldb \
--to=ldb@ldb.ods.org \
--cc=jakub@redhat.com \
--cc=julliard@winehq.com \
--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