From: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
To: mpe@ellerman.id.au
Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
mikey@neuling.org, linux-kernel@vger.kernel.org,
npiggin@gmail.com, paulus@samba.org,
naveen.n.rao@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v6 0/7] Powerpc/Watchpoint: Few important fixes
Date: Thu, 7 Nov 2019 20:00:52 +0530 [thread overview]
Message-ID: <047a102b-9578-88cc-872f-06c2952fb74c@linux.ibm.com> (raw)
In-Reply-To: <ecb3eda1-f111-9485-c28c-e20020ae1d46@c-s.fr>
On 10/29/19 7:31 PM, Christophe Leroy wrote:
>
>
> Le 29/10/2019 à 05:54, Ravi Bangoria a écrit :
>>
>>
>> On 10/17/19 3:01 PM, Ravi Bangoria wrote:
>>> v5: https://lists.ozlabs.org/pipermail/linuxppc-dev/2019-October/198069.html
>>>
>>> v5->v6:
>>> - patch 6/7: mpe reported that the perf-hwbreak.c doesn't compile with older
>>> gcc:
>>> perf-hwbreak.c:182:2: error: dereferencing type-punned pointer will
>>> break strict-aliasing rules [-Werror=strict-aliasing]
>>> temp16 = *((__u16 *)target);
>>> ^
>>> Fixed that.
>>>
>>
>> Hi Christophe, Are you ok with the series wrt 8xx?
>
> Yes it looks ok on my 885:
>
> root@vgoip:~# ./ptrace-hwbreak
> test: ptrace-hwbreak
> tags: git_version:v5.4-rc4-835-gb235e63aa9f0-dirty
> PTRACE_SET_DEBUGREG, WO, len: 1: Ok
> PTRACE_SET_DEBUGREG, WO, len: 2: Ok
> PTRACE_SET_DEBUGREG, WO, len: 4: Ok
> PTRACE_SET_DEBUGREG, WO, len: 8: Ok
> PTRACE_SET_DEBUGREG, RO, len: 1: Ok
> PTRACE_SET_DEBUGREG, RO, len: 2: Ok
> PTRACE_SET_DEBUGREG, RO, len: 4: Ok
> PTRACE_SET_DEBUGREG, RO, len: 8: Ok
> PTRACE_SET_DEBUGREG, RW, len: 1: Ok
> PTRACE_SET_DEBUGREG, RW, len: 2: Ok
> PTRACE_SET_DEBUGREG, RW, len: 4: Ok
> PTRACE_SET_DEBUGREG, RW, len: 8: Ok
> PPC_PTRACE_SETHWDEBUG, MODE_EXACT, WO, len: 1: Ok
> PPC_PTRACE_SETHWDEBUG, MODE_EXACT, RO, len: 1: Ok
> PPC_PTRACE_SETHWDEBUG, MODE_EXACT, RW, len: 1: Ok
> success: ptrace-hwbreak
>
> Also ok on book3s/32:
mpe, Can you please pull the series.
Ravi
prev parent reply other threads:[~2019-11-07 14:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 9:31 [PATCH v6 0/7] Powerpc/Watchpoint: Few important fixes Ravi Bangoria
2019-10-17 9:31 ` [PATCH v6 1/7] Powerpc/Watchpoint: Introduce macros for watchpoint length Ravi Bangoria
2019-11-14 9:07 ` Michael Ellerman
2019-10-17 9:31 ` [PATCH v6 2/7] Powerpc/Watchpoint: Fix length calculation for unaligned target Ravi Bangoria
2019-10-17 9:32 ` [PATCH v6 3/7] Powerpc/Watchpoint: Fix ptrace code that muck around with address/len Ravi Bangoria
2019-10-17 9:32 ` [PATCH v6 4/7] Powerpc/Watchpoint: Don't ignore extraneous exceptions blindly Ravi Bangoria
2019-10-17 9:32 ` [PATCH v6 5/7] Powerpc/Watchpoint: Rewrite ptrace-hwbreak.c selftest Ravi Bangoria
2019-10-17 9:32 ` [PATCH v6 6/7] Powerpc/Watchpoint: Add dar outside test in perf-hwbreak.c selftest Ravi Bangoria
2019-10-17 9:32 ` [PATCH v6 7/7] Powerpc/Watchpoint: Support for 8xx in ptrace-hwbreak.c selftest Ravi Bangoria
2019-10-29 4:54 ` [PATCH v6 0/7] Powerpc/Watchpoint: Few important fixes Ravi Bangoria
2019-10-29 14:01 ` Christophe Leroy
2019-11-07 14:30 ` Ravi Bangoria [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=047a102b-9578-88cc-872f-06c2952fb74c@linux.ibm.com \
--to=ravi.bangoria@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=npiggin@gmail.com \
--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).