All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org,
	Benjamin Herrenschmidt <benh@au1.ibm.com>,
	"K.Prasad" <prasad@linux.vnet.ibm.com>,
	paulus@samba.org
Subject: Re: [RFC] Hardware Breakpoint interfaces implementation for PPC64
Date: Tue, 12 May 2009 11:47:38 -0500	[thread overview]
Message-ID: <20090512164738.GA1173@b07421-ec1.am.freescale.net> (raw)
In-Reply-To: <20090512115149.GA1885@yoda.jdub.homelinux.org>

On Tue, May 12, 2009 at 07:51:49AM -0400, Josh Boyer wrote:
> On Tue, May 12, 2009 at 01:33:55AM +0530, K.Prasad wrote:
> >- The patch is currently implemented only for PPC64 architecture. Other
> >  architectures (especially Book-E implementations are expected to
> >  happen in due course).
> 
> Does this mean you will work on transitioning Book-E implementations, or that
> you expect the Book-E maintainers to?  I'm just curious.  The code as written
> relies heavily on the DABR/MSR setup that ppc64 has and Book-E unfortunately
> doesn't follow that at all.

And since there will eventually be 64-bit book E chips, we need to use
something more specific than CONFIG_PPC64 in the #ifdef (easier now than
figuring out which ones are breakpoint-related later).

-Scott

  reply	other threads:[~2009-05-12 16:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 20:03 [RFC] Hardware Breakpoint interfaces implementation for PPC64 K.Prasad
2009-05-12  0:56 ` Michael Neuling
2009-05-12  2:48   ` Michael Neuling
2009-05-12 20:01   ` K.Prasad
2009-05-12 11:51 ` Josh Boyer
2009-05-12 16:47   ` Scott Wood [this message]
2009-05-12 20:28     ` K.Prasad
2009-05-12 20:25   ` K.Prasad
2009-05-13  2:57     ` David Gibson
2009-05-13  3:00       ` David Gibson
2009-05-14 18:52       ` K.Prasad

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=20090512164738.GA1173@b07421-ec1.am.freescale.net \
    --to=scottwood@freescale.com \
    --cc=benh@au1.ibm.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=prasad@linux.vnet.ibm.com \
    /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.