From: Tom Rini <trini@kernel.crashing.org>
To: Andi Kleen <ak@suse.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, amitkale@emsyssoft.com
Subject: Re: [PATCH][6/6] A different KGDB stub
Date: Thu, 12 Feb 2004 09:27:27 -0700 [thread overview]
Message-ID: <20040212162727.GO19676@smtp.west.cox.net> (raw)
In-Reply-To: <20040213040041.3e1ec2c2.ak@suse.de>
On Fri, Feb 13, 2004 at 04:00:41AM +0100, Andi Kleen wrote:
> On Thu, 12 Feb 2004 08:50:55 -0700
> Tom Rini <trini@kernel.crashing.org> wrote:
> >
> > Part of why I'm trying to get this into -mm is so that someone who has
> > the hw and knowledge can try and merge some of the things that the other
> > stubs got right into the stub that every arch can use.
>
> The kgdb stub in current -mm* does all the things I mentioned correctly.
Yes, and it also makes every arch implement the entire stub and provide
its own serial driver. Having said that, I'll try and pull out more of
the things that the other stub gets right, but I don't have any x86_64
hw (nor toolchain) so I can't test any of the x86_64 changes I make.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-02-12 16:27 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 [this message]
2004-02-16 19:47 ` Pavel Machek
2004-02-12 18:32 ` Tom Rini
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=20040212162727.GO19676@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=amitkale@emsyssoft.com \
--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®