From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: mikey@neuling.org
Subject: Re: [V4] powerpc, xmon: Enable HW instruction breakpoint on POWER8
Date: Tue, 02 Dec 2014 10:35:18 +0530 [thread overview]
Message-ID: <547D488E.6080606@linux.vnet.ibm.com> (raw)
In-Reply-To: <20141201054020.2E47A140160@ozlabs.org>
On 12/01/2014 11:10 AM, Michael Ellerman wrote:
> On Fri, 2014-28-11 at 04:36:42 UTC, Anshuman Khandual wrote:
>> This patch enables support for hardware instruction breakpoint in
>> xmon on POWER8 platform with the help of a new register called the
>> CIABR (Completed Instruction Address Breakpoint Register). With this
>> patch, a single hardware instruction breakpoint can be added and
>> cleared during any active xmon debug session. The hardware based
>> instruction breakpoint mechanism works correctly with the existing
>> TRAP based instruction breakpoint available on xmon.
>>
>> There are no powerpc CPU with CPU_FTR_IABR feature any more. This
>> patch has re-purposed all the existing IABR related code to work
>> with CIABR register based HW instruction breakpoint.
>
> OK I think I'm happy with this, I am going to add this to the changelog though:
>
> This has one odd feature, which is that when we hit a breakpoint xmon
> doesn't tell us we have hit the breakpoint. This is because xmon is
> expecting bp->address == regs->nip. Because CIABR fires on completition
> regs->nip points to the instruction after the breakpoint. We could fix
> that, but it would then confuse other parts of the xmon code which think
> we need to emulate the instruction. [mpe]
Sounds good. Thanks Michael.
prev parent reply other threads:[~2014-12-02 5:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 4:36 [PATCH V4] powerpc, xmon: Enable HW instruction breakpoint on POWER8 Anshuman Khandual
2014-12-01 5:40 ` [V4] " Michael Ellerman
2014-12-02 5:05 ` Anshuman Khandual [this message]
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=547D488E.6080606@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
/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).