From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: interesting line in process.c
Date: Sat, 13 Oct 2001 13:14:02 -0400 [thread overview]
Message-ID: <20011013131402.A26264@nevyn.them.org> (raw)
In-Reply-To: <15304.11248.720092.645241@cargo.ozlabs.ibm.com>
On Sat, Oct 13, 2001 at 09:56:32PM +1000, Paul Mackerras wrote:
>
> I'm intrigued by this line, line 276 in arch/ppc/kernel/process.c in
> linuxppc_2_4_devel:
>
> #if defined(CONFIG_4xx) && defined(DCRN_PLB0_BEAR) && defined(DCRN_PLB0_BEAR)
>
> When could we have DCRN_PLB0_BEAR defined but DCRN_PLB0_BEAR not? :)
> Could it ever be defined if CONFIG_4xx was not defined?
>
> Which brings up another question that I have been meaning to ask: what
> is the rationale for adding the dbcr0/1 fields to the ptrace struct
> for 4xx?
>
> Since struct ptrace is part of the kernel/user ABI, I prefer not to
> change it unless it is absolutely necessary. Could the dbcr0/1 fields
> go in the thread_struct instead? Where and how are they used?
Well, I don't know anything about the 4xx, so this might not be
reasonable - but could they be used in setting hardware breakpoints?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-13 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 11:56 interesting line in process.c Paul Mackerras
2001-10-13 17:14 ` Daniel Jacobowitz [this message]
2001-10-15 14:38 ` Dan Malek
2001-10-15 15:47 ` Edward Swarthout
2001-10-15 15:54 ` Dan Malek
2001-10-15 17:44 ` Daniel Jacobowitz
2001-10-20 1:42 ` Dan Malek
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=20011013131402.A26264@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=linuxppc-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).