From: Robin Murphy <robin.murphy@arm.com>
To: will@kernel.org
Cc: mark.rutland@arm.com, ilkka@os.amperecomputing.com,
john.g.garry@oracle.com, renyu.zj@linux.alibaba.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] perf/arm-cmn: Identifier support
Date: Mon, 12 Jun 2023 18:16:31 +0100 [thread overview]
Message-ID: <cover.1686588640.git.robin.murphy@arm.com> (raw)
Hi all,
Following on from the disussion on Jing's proposal[1], I've had
confirmation that we do actually have a reliable hardware identifier,
so this mini-series does a bit of refactoring to wire that up and then
expose a sysfs identifier based on it.
Thanks,
Robin.
[1] https://lore.kernel.org/r/1685438374-33287-1-git-send-email-renyu.zj@linux.alibaba.com/
Robin Murphy (2):
perf/arm-cmn: Revamp model detection
perf/arm-cmn: Add sysfs identifier
drivers/perf/arm-cmn.c | 165 +++++++++++++++++++++++++++--------------
1 file changed, 109 insertions(+), 56 deletions(-)
--
2.39.2.101.g768bb238c484.dirty
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Robin Murphy <robin.murphy@arm.com>
To: will@kernel.org
Cc: mark.rutland@arm.com, ilkka@os.amperecomputing.com,
john.g.garry@oracle.com, renyu.zj@linux.alibaba.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] perf/arm-cmn: Identifier support
Date: Mon, 12 Jun 2023 18:16:31 +0100 [thread overview]
Message-ID: <cover.1686588640.git.robin.murphy@arm.com> (raw)
Hi all,
Following on from the disussion on Jing's proposal[1], I've had
confirmation that we do actually have a reliable hardware identifier,
so this mini-series does a bit of refactoring to wire that up and then
expose a sysfs identifier based on it.
Thanks,
Robin.
[1] https://lore.kernel.org/r/1685438374-33287-1-git-send-email-renyu.zj@linux.alibaba.com/
Robin Murphy (2):
perf/arm-cmn: Revamp model detection
perf/arm-cmn: Add sysfs identifier
drivers/perf/arm-cmn.c | 165 +++++++++++++++++++++++++++--------------
1 file changed, 109 insertions(+), 56 deletions(-)
--
2.39.2.101.g768bb238c484.dirty
next reply other threads:[~2023-06-12 17:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 17:16 Robin Murphy [this message]
2023-06-12 17:16 ` [PATCH 0/2] perf/arm-cmn: Identifier support Robin Murphy
2023-06-12 17:16 ` [PATCH 1/2] perf/arm-cmn: Revamp model detection Robin Murphy
2023-06-12 17:16 ` Robin Murphy
2023-06-14 8:24 ` Ilkka Koskinen
2023-06-14 8:24 ` Ilkka Koskinen
2023-06-12 17:16 ` [PATCH 2/2] perf/arm-cmn: Add sysfs identifier Robin Murphy
2023-06-12 17:16 ` Robin Murphy
2023-06-14 8:25 ` Ilkka Koskinen
2023-06-14 8:25 ` Ilkka Koskinen
2023-06-14 12:45 ` Jing Zhang
2023-06-14 12:45 ` Jing Zhang
2023-06-14 14:55 ` John Garry
2023-06-14 14:55 ` John Garry
2023-06-14 17:29 ` Robin Murphy
2023-06-14 17:29 ` Robin Murphy
2023-06-16 11:23 ` [PATCH 0/2] perf/arm-cmn: Identifier support Will Deacon
2023-06-16 11:23 ` Will Deacon
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=cover.1686588640.git.robin.murphy@arm.com \
--to=robin.murphy@arm.com \
--cc=ilkka@os.amperecomputing.com \
--cc=john.g.garry@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=renyu.zj@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.