From: Tom Rini <trini@kernel.crashing.org>
To: Andi Kleen <ak@suse.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][6/6] A different KGDB stub
Date: Thu, 12 Feb 2004 11:32:47 -0700 [thread overview]
Message-ID: <20040212183247.GR19676@smtp.west.cox.net> (raw)
In-Reply-To: <p73wu6syf0n.fsf@verdi.suse.de>
On Thu, Feb 12, 2004 at 07:43:04AM +0100, Andi Kleen wrote:
> Tom Rini <trini@kernel.crashing.org> writes:
[snip]
> > --- a/include/asm-x86_64/processor.h Wed Feb 11 15:42:06 2004
> > +++ b/include/asm-x86_64/processor.h Wed Feb 11 15:42:06 2004
> > @@ -252,6 +252,7 @@
> > unsigned long *io_bitmap_ptr;
> > /* cached TLS descriptors. */
> > u64 tls_array[GDT_ENTRY_TLS_ENTRIES];
> > + void *debuggerinfo;
> > };
>
> This should not be needed
OK. Unless there is a difference in this respect on i386 vs x86_64 in
2.6.3-rc2-mm1, this is needed for the thread support which is in this
version, but not the -mm version. OTOH, if there is a cleaner way of
doing this, and there indeed might be (I need to sit down and re-read
some of the previous threads), I'm all ears, not tied to doing it that
way, etc, etc.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-02-12 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040212000408.GG19676@smtp.west.cox.net.suse.lists.linux.kernel>
2004-02-12 6:43 ` Andi Kleen
2004-02-12 15:50 ` Tom Rini
2004-02-13 3:00 ` Andi Kleen
2004-02-12 16:27 ` Tom Rini
2004-02-16 19:47 ` Pavel Machek
2004-02-12 18:32 ` Tom Rini [this message]
2004-02-17 22:04 Tom Rini
[not found] ` <20040217223040.GA1560@elf.ucw.cz>
[not found] ` <20040217223817.GJ16881@smtp.west.cox.net>
2004-02-17 23:08 ` Pavel Machek
2004-02-17 23:13 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 0:04 Tom Rini
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=20040212183247.GR19676@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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®