From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] arm64: hw_breakpoint: Handle inexact watchpoint addresses
Date: Wed, 19 Oct 2016 13:07:15 +0100 [thread overview]
Message-ID: <20161019120714.GM9193@arm.com> (raw)
In-Reply-To: <16572d35-bf69-1680-717a-d2815b121c32@redhat.com>
On Fri, Oct 14, 2016 at 08:45:43AM +0530, Pratyush Anand wrote:
>
>
> On Thursday 13 October 2016 10:33 PM, Pavel Labath wrote:
> >>I think, its easier to go with your implementation. So, I have taken
> >>> your patch and updated my perf/upstream_arm64_devel branch. May be you
> >>> can give it a test for your test cases.
> >I've checked out the new version of your branch, and it works great.
> >I'll write a patch with additional test cases to go on top of your
> >branch, as the tests there do not capture the bug I was fixing.
>
> That would be great. We can send them all together as V2.
Did you send a v2? I've been holding off reviewing this, but I just want
to make sure I didn't miss the update.
Cheers,
Will
next prev parent reply other threads:[~2016-10-19 12:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 15:18 [PATCH 1/3] arm64: hw_breakpoint: Add get_hwbkt_alignment_mask Pavel Labath
2016-09-23 15:19 ` [PATCH 2/3] arm64: hw_breakpoint: Handle inexact watchpoint addresses Pavel Labath
2016-09-26 14:06 ` Will Deacon
2016-10-07 16:38 ` Pratyush Anand
2016-10-07 17:24 ` Pavel Labath
2016-10-08 5:10 ` Pratyush Anand
2016-10-12 13:50 ` Pavel Labath
2016-10-13 9:58 ` Pratyush Anand
2016-10-13 17:03 ` Pavel Labath
2016-10-14 3:15 ` Pratyush Anand
2016-10-19 12:07 ` Will Deacon [this message]
2016-10-19 13:30 ` Pavel Labath
2016-10-20 5:53 ` Pratyush Anand
2016-10-10 17:08 ` Pratyush Anand
2016-09-23 15:19 ` [PATCH 3/3] selftests: arm64: add test for inexact watchpoint address handling Pavel Labath
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=20161019120714.GM9193@arm.com \
--to=will.deacon@arm.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).