From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: David Gibson <dwg@au1.ibm.com>
Cc: linuxppc-dev@ozlabs.org, "K.Prasad" <prasad@linux.vnet.ibm.com>,
Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/2] [PowerPC Book3E] Introduce new ptrace debug feature flag
Date: Wed, 15 Feb 2012 20:18:51 -0200 [thread overview]
Message-ID: <1329344331.10157.22.camel@hactar> (raw)
In-Reply-To: <20120116081833.GG4512@truffala.fritz.box>
On Mon, 2012-01-16 at 19:18 +1100, David Gibson wrote:
> Hrm. An EXACT breakpoint is not exactly the same as a range
> breakpoint of length 1 (consider unaligned accesses). But despite
> that, it should be possible to implement exact breakpoints on Book3S
> server hardware with some software filtering.
>
> And since that leaves no hardware that *can't* implement exact
> breakpoints (directly or indirectly), I'm not yet convinced of the
> need for a flag bit.
I agree.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2012-02-15 22:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 11:12 [PATCH 0/2] Changes to PowerPC ptrace flags using watchpoints - v2 K.Prasad
2011-12-08 11:19 ` [PATCH 1/2] [hw-breakpoint] Use generic hw-breakpoint interfaces for new PPC ptrace flags K.Prasad
2011-12-21 0:54 ` David Gibson
2011-12-08 11:23 ` [PATCH 2/2] [PowerPC Book3E] Introduce new ptrace debug feature flag K.Prasad
2011-12-21 0:55 ` David Gibson
2011-12-22 9:34 ` K.Prasad
2012-01-16 8:18 ` David Gibson
2012-02-15 22:18 ` Thiago Jung Bauermann [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-19 7:45 [PATCH 0/2] Changes to PowerPC ptrace flags using watchpoints K.Prasad
2011-08-19 7:53 ` [PATCH 2/2] [PowerPC Book3E] Introduce new ptrace debug feature flag K.Prasad
2011-08-23 5:09 ` David Gibson
2011-08-23 9:27 ` K.Prasad
2011-08-24 4:00 ` David Gibson
2011-08-25 0:41 ` Thiago Jung Bauermann
2011-08-26 4:41 ` David Gibson
2011-08-31 0:27 ` Thiago Jung Bauermann
2011-09-19 1:10 ` David Gibson
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=1329344331.10157.22.camel@hactar \
--to=bauerman@br.ibm.com \
--cc=dwg@au1.ibm.com \
--cc=emachado@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.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 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).