From: Tom Rini <trini@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][1/6] A different KGDB stub
Date: Tue, 17 Feb 2004 17:03:15 -0700 [thread overview]
Message-ID: <20040218000315.GN16881@smtp.west.cox.net> (raw)
In-Reply-To: <20040217155036.33e37c67.akpm@osdl.org>
On Tue, Feb 17, 2004 at 03:50:36PM -0800, Andrew Morton wrote:
> Tom Rini <trini@kernel.crashing.org> wrote:
> >
> > The following is the core bits to this KGDB stub.
>
> This still contains the kern_do_schedule() gunk. Andi raised this issue
> last week. He identified several other significant issues as well, but
> there was no followup. Could you please dig out his email and address the
> points which he raised? (I can't find the email - perhaps Andi could
> re-review this patch?)
By my read of Andi's email, the kern_do_schedule() gunk is "I really
don't like this change. It is completely useless because you can get the
pt_regs as well from the stack. Please don't add it. George's stub also
didn't need it."
But I don't see how it does. But I'll look again tomorrow.
The next issue was about adding debuggerinfo to thread_struct. By my
read of the code, it's because of the thread handling bits that Amit's
version does that George's does not. So I'm not sure how it's not
needed (unless all of the relevant code goes. If that's too heavy, I
can remove all of that).
Next was that KGDB should use the notify_die hooks that are there, and
I've done that.
Finally, the save_context_frame stuff can go (x86_64-specific stuffs)
but as I don't have x86_64 hw (I'll try and whip up a toolchain
tomorrow, but I leave for FOSDEM Thursday) so I didn't touch that, in
hopes that someone who could test it would.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-02-18 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 22:02 Tom Rini
2004-02-17 23:50 ` Andrew Morton
2004-02-18 0:03 ` Tom Rini [this message]
2004-02-18 0:33 ` Andrew Morton
2004-02-18 0:39 ` Tom Rini
2004-02-25 17:50 ` Tom Rini
2004-02-18 19:36 ` Pavel Machek
2004-02-18 20:23 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 0:02 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=20040218000315.GN16881@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--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®