From: panand@redhat.com (Pratyush Anand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] arm64: Allow hw watchpoint of length 3,5,6 and 7
Date: Thu, 13 Oct 2016 15:52:17 +0530 [thread overview]
Message-ID: <1bc0dce6-eb26-dbf5-dd0c-d36055f5f1fe@redhat.com> (raw)
In-Reply-To: <CAH=s-PNFESLA6TTem-49g0CKsjpKOsj1XYfPUXz6YbEfMWXqXg@mail.gmail.com>
On Wednesday 12 October 2016 04:46 PM, Yao Qi wrote:
> On Wed, Oct 12, 2016 at 6:58 AM, Pratyush Anand <panand@redhat.com> wrote:
>> Since, arm64 can support all offset within a double word limit. Therefore,
>> now support other lengths within that range as well.
>
> How does ptracer (like GDB) detect kernel has already supported all byte
> address select values? I suppose ptrace(NT_ARM_HW_WATCH, ) with
> len is 3 or 5 fail on current kernel but is of success after your patches
> applied.
>
Thanks for testing these patches.
I do not know if we can know that other than the failure of
ptrace(PTRACE_SETREGSET, .., NT_ARM_HW_WATCH, ..). I do not see any such
option in `man ptrace`.
> GDB is aware of the byte address select limitation in kernel, so it always
> sets 1,2,4,8 in len in ctrl. GDB needs to know whether the limitation is still
> there or not.
>
Not sure if other than "kernel version" anything will help here.
~Pratyush
next prev parent reply other threads:[~2016-10-13 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 5:58 [PATCH 0/4] ARM64: More flexible HW watchpoint Pratyush Anand
2016-10-12 5:58 ` [PATCH 1/4] hw_breakpoint: Allow watchpoint of length 3,5,6 and 7 Pratyush Anand
2016-10-12 5:58 ` [PATCH 2/4] arm64: Allow hw watchpoint at varied offset from base address Pratyush Anand
2016-10-12 5:58 ` [PATCH 3/4] arm64: Allow hw watchpoint of length 3,5,6 and 7 Pratyush Anand
2016-10-12 11:16 ` Yao Qi
2016-10-13 10:22 ` Pratyush Anand [this message]
2016-10-13 14:29 ` Pavel Labath
2016-10-12 5:58 ` [PATCH 4/4] selftests: arm64: add test for unaligned watchpoint address handling Pratyush Anand
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=1bc0dce6-eb26-dbf5-dd0c-d36055f5f1fe@redhat.com \
--to=panand@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).