From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: linux-arch@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Vineet.Gupta1@synopsys.com,
arc-linux-dev@synopsys.com, arnd@arndb.de, peterz@infradead.org,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Subject: [PATCH v2 0/8] ARCv2 port to Linux - (C) perf
Date: Wed, 5 Aug 2015 18:13:26 +0300 [thread overview]
Message-ID: <1438787614-14074-1-git-send-email-abrodkin@synopsys.com> (raw)
Hi Peter,
This mini-series adds perf support for ARCv2 based cores, which brings in
overflow interupts and SMP. Additionally now raw events are supported as well.
Please review !
Compared to v1 this series has:
[1] Addressed review comments
[2] More verbose commit messages and comments in sources
[3] Minor cosmetics
Thanks,
Alexey
Alexey Brodkin (6):
ARC: perf: support RAW events
ARCv2: perf: implement "event_set_period" for future use with
interrupts
ARCv2: perf: Support sampling events using overflow interrupts
ARCv2: perf: set usable max period as a half of real max period
ARCv2: perf: implement exclusion of event counting in user or kernel
mode
ARCv2: perf: SMP support
Vineet Gupta (2):
ARC: perf: cap the number of counters to hardware max of 32
ARCv2: perf: Finally introduce HS perf unit
.../devicetree/bindings/arc/archs-pct.txt | 17 +
MAINTAINERS | 2 +-
arch/arc/include/asm/perf_event.h | 24 +-
arch/arc/kernel/perf_event.c | 350 ++++++++++++++++++---
4 files changed, 345 insertions(+), 48 deletions(-)
create mode 100644 Documentation/devicetree/bindings/arc/archs-pct.txt
--
2.4.3
next reply other threads:[~2015-08-05 15:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 15:13 Alexey Brodkin [this message]
2015-08-05 15:13 ` [PATCH v2 1/8] ARC: perf: support RAW events Alexey Brodkin
2015-08-05 15:13 ` [PATCH v2 2/8] ARC: perf: cap the number of counters to hardware max of 32 Alexey Brodkin
2015-08-05 15:13 ` Alexey Brodkin
2015-08-05 15:13 ` [PATCH v2 3/8] ARCv2: perf: implement "event_set_period" for future use with interrupts Alexey Brodkin
2015-08-05 15:13 ` Alexey Brodkin
2015-08-18 17:52 ` Peter Zijlstra
2015-08-18 18:03 ` Alexey Brodkin
2015-08-20 10:46 ` Alexey Brodkin
2015-08-18 17:55 ` Peter Zijlstra
2015-08-20 11:25 ` Alexey Brodkin
2015-08-05 15:13 ` [PATCH v2 4/8] ARCv2: perf: Support sampling events using overflow interrupts Alexey Brodkin
2015-08-05 15:13 ` Alexey Brodkin
2015-08-18 22:12 ` Peter Zijlstra
2015-08-20 11:30 ` Alexey Brodkin
2015-08-05 15:13 ` [PATCH v2 5/8] ARCv2: perf: set usable max period as a half of real max period Alexey Brodkin
2015-08-05 15:13 ` Alexey Brodkin
2015-08-05 15:13 ` [PATCH v2 6/8] ARCv2: perf: implement exclusion of event counting in user or kernel mode Alexey Brodkin
2015-08-05 15:13 ` Alexey Brodkin
2015-08-18 23:37 ` Peter Zijlstra
2015-08-20 11:33 ` Alexey Brodkin
2015-08-05 15:13 ` [PATCH v2 7/8] ARCv2: perf: SMP support Alexey Brodkin
2015-08-05 15:13 ` [PATCH v2 8/8] ARCv2: perf: Finally introduce HS perf unit Alexey Brodkin
2015-08-05 15:13 ` Alexey Brodkin
2015-08-10 8:29 ` [PATCH v2 0/8] ARCv2 port to Linux - (C) perf Alexey Brodkin
2015-08-10 8:29 ` Alexey Brodkin
2015-08-14 7:41 ` [arc-linux-dev] " Vineet Gupta
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=1438787614-14074-1-git-send-email-abrodkin@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=arc-linux-dev@synopsys.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@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).