From: Armin <akuster@pacbell.net>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: pt_regs.dbcr0/1
Date: Sun, 02 Jun 2002 23:04:35 -0700 [thread overview]
Message-ID: <3CFB06F3.6060704@pacbell.net> (raw)
In-Reply-To: 15608.22230.504008.818858@argo.ozlabs.ibm.com
Paul Mackerras wrote:
> Is anyone prepared to speak up for the dbcr0 and dbcr1 fields that
> someone added to struct pt_regs for 4xx in the 2_4_devel tree?
>
> If not, they are going. If so, we can discuss it.
>
> Better still, does anyone have a clearly thought-out vision of how the
> debug facilities on 4xx should be managed?
>
> I would much prefer to see these fields put in the thread_struct
> rather than pt_regs. I am reluctant to change pt_regs without a good
> reason since it is visible to userspace and is therefore part of the
> kernel API. If the intention is to make the debug facilities
> available to userspace then the thread_struct is a good place to put
> fields relating to the debug facilities.
>
> Paul.
>
>
>
>
>
Oh man its been a while... hmmm IIRC I thought we used pt_regs for kgdb.
IIRC we already use the thread_struct for gdb. There are two people
who did the bulk of the debugger work, if they don't pipe up , I will do
my best.
I'll get back to you.
armin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-03 6:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 5:08 pt_regs.dbcr0/1 Paul Mackerras
2002-06-03 6:04 ` Armin [this message]
2002-06-04 1:23 ` pt_regs.dbcr0/1 Dan Malek
2002-06-04 5:02 ` pt_regs.dbcr0/1 Paul Mackerras
2002-06-04 17:22 ` pt_regs.dbcr0/1 Dan Malek
2002-06-04 21:34 ` pt_regs.dbcr0/1 Kumar Gala
2002-06-04 22:00 ` pt_regs.dbcr0/1 Frank Rowand
2002-06-04 22:10 ` pt_regs.dbcr0/1 Dan Malek
2002-06-04 21:55 ` pt_regs.dbcr0/1 Frank Rowand
2002-06-04 22:03 ` pt_regs.dbcr0/1 Paul Mackerras
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=3CFB06F3.6060704@pacbell.net \
--to=akuster@pacbell.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.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.