From: Gabriel Paubert <paubert@iram.es>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: Boot failure in 2.5.31 BK with new TLS patch
Date: Sat, 17 Aug 2002 20:50:43 +0200 [thread overview]
Message-ID: <3D5E9B03.4070503@iram.es> (raw)
In-Reply-To: Pine.LNX.4.44.0208171134070.3169-100000@home.transmeta.com
Linus Torvalds wrote:
> The gdt descriptor alignment really shouldn't matter, but that bogus
> GDT _size_ thing in the descriptor might do it.
Indeed.
> Right now it's set to be 0x8000, which is not a legal GDT size (it
> should be of the form n*8-1), and is nonsensical anyway (the comment
> says 2048 entries, but the fact is, we don't _have_ 2048 entries in
> there).
In my source tree pulled about at the end of last night here (10pm in
California) it is still GDT_ENTRIES*8-1. Time to pull :-)
Gabriel.
P.S: since the first entry is not used, the first 8 bytes could be filled
with
1: .word 0
gdt_table_desc: .word GDT_ENTRIES*8-1
.long 1b
to eliminate the array of GDT descriptors and save a few bytes.
next prev parent reply other threads:[~2002-08-17 18:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-17 0:31 Boot failure in 2.5.31 BK with new TLS patch James Bottomley
2002-08-17 6:51 ` Ingo Molnar
2002-08-17 15:16 ` James Bottomley
2002-08-17 16:17 ` Ingo Molnar
2001-11-02 8:20 ` Pavel Machek
2002-08-17 17:09 ` Gabriel Paubert
2002-08-17 17:18 ` Ingo Molnar
2002-08-17 17:20 ` James Bottomley
2002-08-17 18:26 ` Gabriel Paubert
2002-08-17 18:36 ` Linus Torvalds
2002-08-17 18:42 ` Ingo Molnar
2002-08-17 18:50 ` Gabriel Paubert [this message]
2002-08-17 18:53 ` Ingo Molnar
2002-08-17 21:42 ` Ingo Molnar
2002-08-18 3:29 ` Linus Torvalds
2002-08-17 22:34 ` James Bottomley
2002-08-18 8:35 ` Ingo Molnar
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=3D5E9B03.4070503@iram.es \
--to=paubert@iram.es \
--cc=James.Bottomley@HansenPartnership.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.