From: David Gibson <dwg@au1.ibm.com>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: linuxppc-dev list <Linuxppc-dev@ozlabs.org>,
Sergio Durigan Junior <sergiodj@br.ibm.com>,
Torez Smith <torez@us.ibm.com>,
Thiago Jung Bauermann <bauerman@br.ibm.com>
Subject: Re: [PATCH 01/04] powerpc/booke: Introduce new CONFIG options for advanced debug registers
Date: Thu, 11 Feb 2010 14:55:16 +1100 [thread overview]
Message-ID: <20100211035516.GO13335@yookeroo> (raw)
In-Reply-To: <20100208215057.17930.30833.sendpatchset@norville.austin.ibm.com>
On Mon, Feb 08, 2010 at 02:50:57PM -0700, Dave Kleikamp wrote:
> powerpc/booke: Introduce new CONFIG options for advanced debug registers
>
> From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
>
> Introduce new config options to simplify the ifdefs pertaining to the
> advanced debug registers for booke and 40x processors:
>
> CONFIG_PPC_ADV_DEBUG_REGS - boolean: true for dac-based processors
> CONFIG_PPC_ADV_DEBUG_IACS - number of IAC registers
> CONFIG_PPC_ADV_DEBUG_DACS - number of DAC registers
> CONFIG_PPC_ADV_DEBUG_DVCS - number of DVC registers
> CONFIG_PPC_ADV_DEBUG_DAC_RANGE - DAC ranges supported
>
> Beginning conservatively, since I only have the facilities to test 440
> hardware. I believe all 40x and booke platforms support at least 2 IAC
> and 2 DAC registers. For 440, 4 IAC and 2 DVC registers are enabled, as
> well as the DAC ranges.
Hrm. I'm not entirely convinced there aren't or won't be 44x chips
with a different number of regs. Still we fix it up to do runtime
checking later.
> Signed-off-by: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Acked-by: David Gibson <dwg@au1.ibm.com>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2010-02-11 3:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 21:50 [PATCH 00/04] powerpc/booke: Expose advanced debug registers through extended ptrace interface Dave Kleikamp
2010-02-08 21:50 ` [PATCH 01/04] powerpc/booke: Introduce new CONFIG options for advanced debug registers Dave Kleikamp
2010-02-11 3:55 ` David Gibson [this message]
2010-02-08 21:51 ` [PATCH 02/04] powerpc: Extended ptrace interface Dave Kleikamp
2010-02-08 21:51 ` [PATCH 04/04] powerpc/booke: Add support for advanced debug registers Dave Kleikamp
2010-02-08 21:53 ` [PATCH 03/04] powerpc/booke: Add definitions " Dave Kleikamp
2010-02-23 19:43 ` [PATCH] powerpc/booke: Fix a couple typos in the advanced ptrace code Dave Kleikamp
2010-03-01 14:57 ` [PATCH] powerpc/booke: Fix breakpoint/watchpoint one-shot behavior Dave Kleikamp
2010-03-04 16:52 ` [PATCH] powerpc/booke: Fix a couple typos in the advanced ptrace code Kumar Gala
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=20100211035516.GO13335@yookeroo \
--to=dwg@au1.ibm.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=bauerman@br.ibm.com \
--cc=sergiodj@br.ibm.com \
--cc=shaggy@linux.vnet.ibm.com \
--cc=torez@us.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox