From: Rob Bradford <rbradford@rivosinc.com>
To: qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, atishp@rivosinc.com, palmer@dabbelt.com,
alistair.francis@wdc.com, bin.meng@windriver.com,
liweiwei@iscas.ac.cn, dbarboza@ventanamicro.com,
zhiwei_liu@linux.alibaba.com,
Rob Bradford <rbradford@rivosinc.com>
Subject: [PATCH 0/3] Support discontinuous PMU counters
Date: Tue, 3 Oct 2023 13:49:34 +0100 [thread overview]
Message-ID: <20231003125107.34859-1-rbradford@rivosinc.com> (raw)
Currently the available PMU counters start at HPM3 and run through to
the number specified by the "pmu-num" property. There is no
requirement in the specification that the available counters be
continously numbered. This series add suppport for specifying a
discountinuous range of counters though a "pmu-mask" property.
Rob Bradford (3):
target/riscv: Propagate error from PMU setup
target/riscv: Support discontinuous PMU counters
target/riscv: Don't assume PMU counters are continuous
target/riscv/cpu.c | 9 ++++++++-
target/riscv/cpu_cfg.h | 1 +
target/riscv/csr.c | 5 +++--
target/riscv/pmu.c | 32 +++++++++++++++++++++-----------
target/riscv/pmu.h | 3 ++-
5 files changed, 35 insertions(+), 15 deletions(-)
--
2.41.0
next reply other threads:[~2023-10-03 12:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 12:49 Rob Bradford [this message]
2023-10-03 12:49 ` [PATCH 1/3] target/riscv: Propagate error from PMU setup Rob Bradford
2023-10-09 0:55 ` Alistair Francis
2023-10-03 12:49 ` [PATCH 2/3] target/riscv: Support discontinuous PMU counters Rob Bradford
2023-10-03 20:25 ` Atish Kumar Patra
2023-10-04 9:35 ` Rob Bradford
2023-10-09 0:57 ` Alistair Francis
2023-10-09 18:00 ` Atish Kumar Patra
2023-10-11 1:06 ` Alistair Francis
2023-10-11 9:51 ` Rob Bradford
2023-10-16 4:44 ` Alistair Francis
2023-10-03 12:49 ` [PATCH 3/3] target/riscv: Don't assume PMU counters are continuous Rob Bradford
2023-10-12 8:25 ` LIU Zhiwei
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=20231003125107.34859-1-rbradford@rivosinc.com \
--to=rbradford@rivosinc.com \
--cc=alistair.francis@wdc.com \
--cc=atishp@rivosinc.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=liweiwei@iscas.ac.cn \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.com \
/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).