From: Thiago Jung Bauermann <bauerman@br•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>, David Gibson <dwg@au1•ibm.com>
Subject: Re: [RFC:PATCH 00/03] powerpc: Expose BookE debug registers through extended ptrace interface
Date: Fri, 11 Dec 2009 18:07:56 -0200 [thread overview]
Message-ID: <200912111807.56262.bauerman@br.ibm.com> (raw)
In-Reply-To: <1260498456.4329.8.camel@norville.austin.ibm.com>
On Fri 11 Dec 2009 00:27:36 Dave Kleikamp wrote:
> On Thu, 2009-12-10 at 20:23 -0600, Kumar Gala wrote:
> > On Dec 10, 2009, at 9:57 AM, Dave Kleikamp wrote:
> > > #define PPC_DEBUG_FEATURE_INSN_BP_RANGE 0x1
> > > #define PPC_DEBUG_FEATURE_INSN_BP_MASK 0x2
> > > #define PPC_DEBUG_FEATURE_DATA_BP_RANGE 0x4
> > > #define PPC_DEBUG_FEATURE_DATA_BP_MASK 0x8
> >
> > Is GDB smart enough to deal w/no condition_regs? On some Book-E
> > devices we have 2 IACs, 2 DACs, and 0 DVCs. Does it need to be in the
> > features?
>
> I had discussed it with the gdb team. I could easily add a feature
> flag, but it would be equivalent to num_condition_regs > 0. I don't
> have a strong opinion either way.
The current GDB code we have here uses num_condition_regs > 0 to discover if
DVCs are supported, so a PPC_DEBUG_FEATURE constant for that is redundant
IMHO.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2009-12-11 20:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 15:57 [RFC:PATCH 00/03] powerpc: Expose BookE debug registers through extended ptrace interface Dave Kleikamp
2009-12-10 15:57 ` [RFC:PATCH 01/03] powerpc: Extended " Dave Kleikamp
2009-12-11 0:44 ` David Gibson
2009-12-11 2:51 ` Kumar Gala
2009-12-10 15:57 ` [RFC:PATCH 02/03] powerpc: Add definitions for Debug Registers on BookE Platforms Dave Kleikamp
2009-12-10 17:07 ` Josh Boyer
2010-01-18 22:07 ` Dave Kleikamp
2009-12-11 0:53 ` David Gibson
2009-12-11 1:31 ` Dave Kleikamp
2010-01-18 22:10 ` Dave Kleikamp
2009-12-11 2:41 ` Kumar Gala
2009-12-11 3:28 ` David Gibson
2009-12-11 14:35 ` Kumar Gala
2009-12-14 1:16 ` David Gibson
2009-12-10 15:57 ` [RFC:PATCH 03/03] powerpc: Add support for BookE Debug Reg. traps, exceptions and ptrace Dave Kleikamp
2009-12-10 17:27 ` Josh Boyer
2009-12-10 17:41 ` Josh Boyer
2009-12-10 18:05 ` Dave Kleikamp
2009-12-11 2:50 ` Kumar Gala
2010-01-18 22:18 ` Dave Kleikamp
2009-12-11 3:26 ` David Gibson
2010-01-18 22:31 ` Dave Kleikamp
2009-12-11 2:23 ` [RFC:PATCH 00/03] powerpc: Expose BookE debug registers through extended ptrace interface Kumar Gala
2009-12-11 2:27 ` Dave Kleikamp
2009-12-11 20:07 ` Thiago Jung Bauermann [this message]
2009-12-11 20:51 ` Kumar Gala
2010-01-18 22:34 ` Dave Kleikamp
2010-02-03 2:03 ` Dave Kleikamp
2009-12-11 2:24 ` Kumar Gala
2009-12-11 2:29 ` Dave Kleikamp
2009-12-11 2:32 ` Kumar Gala
2009-12-12 4:18 ` Benjamin Herrenschmidt
2009-12-11 2:45 ` Kumar Gala
2010-01-18 22:41 ` Dave Kleikamp
-- strict thread matches above, loose matches on Subject: below --
2010-01-18 21:57 Dave Kleikamp
2010-01-24 19:18 K.Prasad
2010-01-24 20:32 ` Benjamin Herrenschmidt
2010-01-28 7:13 ` K.Prasad
2010-01-30 20:44 ` Frederic Weisbecker
2010-01-30 21:33 ` Benjamin Herrenschmidt
2010-01-31 1:00 ` Frederic Weisbecker
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=200912111807.56262.bauerman@br.ibm.com \
--to=bauerman@br$(echo .)ibm.com \
--cc=Linuxppc-dev@ozlabs$(echo .)org \
--cc=dwg@au1$(echo .)ibm.com \
--cc=sergiodj@br$(echo .)ibm.com \
--cc=shaggy@linux$(echo .)vnet.ibm.com \
--cc=torez@us$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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