From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
mpe@ellerman.id.au, mikey@neuling.org
Cc: paulus@samba.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] powerpc/watchpoint: Disable watchpoint hit by larx/stcx instruction
Date: Tue, 10 Sep 2019 12:30:38 +0200 [thread overview]
Message-ID: <34c222f3-e185-f859-f9d5-7447886fd1a8@c-s.fr> (raw)
In-Reply-To: <20190910102422.23233-1-ravi.bangoria@linux.ibm.com>
Le 10/09/2019 à 12:24, Ravi Bangoria a écrit :
> I've prepared my patch on top of Christophe's patch as it's easy
> to change stepping_handler() rather than hw_breakpoint_handler().
> 2nd patch is the actual fix.
Anyway, my patch is already commited on powerpc/next
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20190904&id=658d029df0bce6472c94b724ca54d74bc6659c2e
Christophe
>
> Christophe Leroy (1):
> powerpc/hw_breakpoint: move instruction stepping out of
> hw_breakpoint_handler()
>
> Ravi Bangoria (1):
> powerpc/watchpoint: Disable watchpoint hit by larx/stcx instructions
>
> arch/powerpc/kernel/hw_breakpoint.c | 77 +++++++++++++++++++----------
> 1 file changed, 50 insertions(+), 27 deletions(-)
>
prev parent reply other threads:[~2019-09-10 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 10:24 [PATCH 0/2] powerpc/watchpoint: Disable watchpoint hit by larx/stcx instruction Ravi Bangoria
2019-09-10 10:24 ` [PATCH 1/2] powerpc/hw_breakpoint: move instruction stepping out of hw_breakpoint_handler() Ravi Bangoria
2019-09-10 10:24 ` [PATCH 2/2] powerpc/watchpoint: Disable watchpoint hit by larx/stcx instructions Ravi Bangoria
2019-09-10 10:44 ` Naveen N. Rao
2019-09-10 10:30 ` Christophe Leroy [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=34c222f3-e185-f859-f9d5-7447886fd1a8@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=ravi.bangoria@linux.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).