From: Eli Carter <eli.carter@inet.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.64-mm6
Date: Fri, 14 Mar 2003 14:38:23 -0600 [thread overview]
Message-ID: <3E723DBF.6040304@inet.com> (raw)
In-Reply-To: 20030313032615.7ca491d6.akpm@digeo.com
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.64/2.5.64-mm6/
[snip]
> kgdb.patch
I'm interested in this patch in your tree. (Just to warn you of my
biases, I'm currently working with the XScale/ARM arch.) I've noticed
some things about it in an initial look, namely:
There appears to be some code duplication between hex() and stubhex() in
arch/i386/kernel/gdbstub.c.
Also, the bulk of gdbstub.c appears to be generic code. There are a
number of functions that have x86 asm in them, but it looks to me on
initial viewing, that most of the logic is applicable to other arches.
Am I understanding that correctly?
Right now it looks like an arch would need to provide a way to:
- reboot the processor
- implement 'continue at address' and 'step one instruction from address'
- handle_exeption()
- printexception()
- correct_hw_break()
- regs_to_gdb_regs() and gdb_regs_to_regs()
Hmm, there's probably some more to that part...
The above is just for the gdbstub.c. I'm still reading the patch. :)
Would breaking the arch-independent parts out to linux/kernel/gdbstub.c
be a reasonable change or is that a dumb question? ;)
Thanks,
Eli
--------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------
WARNING: multiple messages have this Message-ID (diff)
From: Eli Carter <eli.carter@inet.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.64-mm6
Date: Fri, 14 Mar 2003 14:38:23 -0600 [thread overview]
Message-ID: <3E723DBF.6040304@inet.com> (raw)
In-Reply-To: 20030313032615.7ca491d6.akpm@digeo.com
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.64/2.5.64-mm6/
[snip]
> kgdb.patch
I'm interested in this patch in your tree. (Just to warn you of my
biases, I'm currently working with the XScale/ARM arch.) I've noticed
some things about it in an initial look, namely:
There appears to be some code duplication between hex() and stubhex() in
arch/i386/kernel/gdbstub.c.
Also, the bulk of gdbstub.c appears to be generic code. There are a
number of functions that have x86 asm in them, but it looks to me on
initial viewing, that most of the logic is applicable to other arches.
Am I understanding that correctly?
Right now it looks like an arch would need to provide a way to:
- reboot the processor
- implement 'continue at address' and 'step one instruction from address'
- handle_exeption()
- printexception()
- correct_hw_break()
- regs_to_gdb_regs() and gdb_regs_to_regs()
Hmm, there's probably some more to that part...
The above is just for the gdbstub.c. I'm still reading the patch. :)
Would breaking the arch-independent parts out to linux/kernel/gdbstub.c
be a reasonable change or is that a dumb question? ;)
Thanks,
Eli
--------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-03-14 20:27 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 11:26 2.5.64-mm6 Andrew Morton
2003-03-13 11:26 ` 2.5.64-mm6 Andrew Morton
2003-03-13 16:23 ` 2.5.64-mm6 Jeremy Fitzhardinge
2003-03-13 16:23 ` 2.5.64-mm6 Jeremy Fitzhardinge
2003-03-13 19:34 ` 2.5.64-mm6 Andrew Morton
2003-03-13 19:34 ` 2.5.64-mm6 Andrew Morton
2003-03-13 20:07 ` 2.5.64-mm6 Roger Larsson
2003-03-14 3:04 ` 2.5.64-mm6 Steven Cole
2003-03-14 3:04 ` 2.5.64-mm6 Steven Cole
2003-03-14 3:28 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:28 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:46 ` 2.5.64-mm6 Shawn
2003-03-14 3:46 ` 2.5.64-mm6 Shawn
2003-03-14 3:51 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:51 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:56 ` 2.5.64-mm6 Robert Love
2003-03-14 3:56 ` 2.5.64-mm6 Robert Love
2003-03-14 13:31 ` 2.5.64-mm6 jlnance
2003-03-14 20:05 ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:10 ` 2.5.64-mm6 Alex Tomas
2003-03-14 20:22 ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:19 ` 2.5.64-mm6 Alex Tomas
2003-03-13 20:35 ` 2.5.64-mm6 Thomas Molina
2003-03-13 20:35 ` 2.5.64-mm6 Thomas Molina
2003-03-14 9:29 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 9:29 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 11:55 ` 2.5.64-mm6 Andrew Morton
2003-03-14 11:55 ` 2.5.64-mm6 Andrew Morton
2003-03-15 8:38 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-15 8:38 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 12:01 ` 2.5.64-mm6 Helge Hafting
2003-03-14 12:01 ` 2.5.64-mm6 Helge Hafting
2003-03-14 12:14 ` 2.5.64-mm6 Andrew Morton
2003-03-14 12:14 ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:38 ` Eli Carter [this message]
2003-03-14 20:38 ` 2.5.64-mm6 Eli Carter
2003-03-14 20:53 ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:53 ` 2.5.64-mm6 Andrew Morton
2003-03-14 22:01 ` 2.5.64-mm6 Eli Carter
2003-03-14 22:01 ` 2.5.64-mm6 Eli Carter
2003-03-14 22:21 ` 2.5.64-mm6 Andrew Morton
2003-03-14 22:21 ` 2.5.64-mm6 Andrew Morton
[not found] <20030313032615.7ca491d6.akpm@digeo.com.suse.lists.linux.kernel>
2003-03-13 13:36 ` 2.5.64-mm6 Andi Kleen
2003-03-13 19:32 ` 2.5.64-mm6 Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2003-03-13 13:42 2.5.64-mm6 Felipe Alfaro Solana
2003-03-13 13:42 ` 2.5.64-mm6 Felipe Alfaro Solana
2003-03-13 21:49 2.5.64-mm6 Felipe Alfaro Solana
2003-03-13 21:49 ` 2.5.64-mm6 Felipe Alfaro Solana
2003-03-14 0:23 ` 2.5.64-mm6 Thomas Molina
2003-03-14 0:23 ` 2.5.64-mm6 Thomas Molina
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=3E723DBF.6040304@inet.com \
--to=eli.carter@inet.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.