From: Bhupesh Sharma <bhsharma@redhat.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
bhsharma@redhat.com, linux-kernel@vger.kernel.org,
bhupesh.linux@gmail.com, Will Deacon <will@kernel.org>
Subject: [PATCH 0/2] Fix some arm64 perf issues
Date: Tue, 4 Feb 2020 03:56:22 +0530 [thread overview]
Message-ID: <1580768784-25868-1-git-send-email-bhsharma@redhat.com> (raw)
This patchset tries to address some arm64 perf issues.
While the 1st patch is a generic one and just removes a dead/left-over
declaration:
[PATCH 1/2]: hw_breakpoint: Remove unused '__register_perf_hw_breakpoint' declaration
the 2nd patch addresses 'perf stat -e' like use-cases on arm64 which
allow per-task address execution h/w breakpoints:
[PATCH 2/2]: perf/arm64: Allow per-task kernel breakpoints
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Bhupesh Sharma (2):
hw_breakpoint: Remove unused '__register_perf_hw_breakpoint'
declaration
perf/arm64: Allow per-task kernel breakpoints
arch/arm64/kernel/hw_breakpoint.c | 7 -------
include/linux/hw_breakpoint.h | 3 ---
2 files changed, 10 deletions(-)
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-02-03 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 22:26 Bhupesh Sharma [this message]
2020-02-03 22:26 ` [PATCH 1/2] hw_breakpoint: Remove unused '__register_perf_hw_breakpoint' declaration Bhupesh Sharma
2020-02-03 22:26 ` [PATCH 2/2] perf/arm64: Allow per-task kernel breakpoints Bhupesh Sharma
2020-02-06 10:38 ` Will Deacon
2020-02-07 7:22 ` Bhupesh Sharma
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=1580768784-25868-1-git-send-email-bhsharma@redhat.com \
--to=bhsharma@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bhupesh.linux@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.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).