From: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
To: Christophe Leroy <christophe.leroy@c-s.fr>
Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/hw_breakpoint: move instruction stepping out of hw_breakpoint_handler()
Date: Mon, 8 Jul 2019 09:10:54 +0530 [thread overview]
Message-ID: <d0358cc8-00e2-cd5a-9a4f-f9eae1548026@linux.ibm.com> (raw)
In-Reply-To: <bef43f48-fa40-284e-a299-bc73ebc3e725@c-s.fr>
On 7/6/19 1:56 PM, Christophe Leroy wrote:
>
>
> Le 03/07/2019 à 08:20, Ravi Bangoria a écrit :
>>
>>
>> On 6/28/19 9:25 PM, Christophe Leroy wrote:
>>> On 8xx, breakpoints stop after executing the instruction, so
>>> stepping/emulation is not needed. Move it into a sub-function and
>>> remove the #ifdefs.
>>>
>>> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
>>> ---
>>
>> Reviewed-by: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
>>
>> Just one neat below...
>
> Thanks for the review.
>
>>
>> [...]
>>
>>> -#ifndef CONFIG_PPC_8xx
>>> - /* Do not emulate user-space instructions, instead single-step them */
>>> - if (user_mode(regs)) {
>>> - current->thread.last_hit_ubp = bp;
>>> - regs->msr |= MSR_SE;
>>> + if (!IS_ENABLED(CONFIG_PPC_8xx) && !stepping_handler(regs, bp, info->address))
>>
>> May be split this line. It's 86 chars long and checkpatch.pl is warning
>> about this:
>
> Didn't you use arch/powerpc/tools/checkpatch.sh ?
>
> powerpc accepts 90 chars per line.
Hmm.. wasn't aware of it. Thanks!
next prev parent reply other threads:[~2019-07-08 3:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 15:55 [PATCH] powerpc/hw_breakpoint: move instruction stepping out of hw_breakpoint_handler() Christophe Leroy
2019-07-03 6:20 ` Ravi Bangoria
2019-07-06 8:26 ` Christophe Leroy
2019-07-08 3:40 ` Ravi Bangoria [this message]
2019-08-22 13:08 ` Michael Ellerman
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=d0358cc8-00e2-cd5a-9a4f-f9eae1548026@linux.ibm.com \
--to=ravi.bangoria@linux.ibm.com \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
/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).