From: "Jörg Rödel" <joro@8bytes.org>
To: Zong Li <zong.li@sifive.com>
Cc: tomasz.jeznach@linux.dev, will@kernel.org, robin.murphy@arm.com,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, mark.rutland@arm.com,
andrew.jones@oss.qualcomm.com, guoren@kernel.org,
david.laight.linux@gmail.com,
zhangzhanpeng.jasper@bytedance.com, yang.yicong@picoheart.com,
nutty.liu@hotmail.com, iommu@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v14 0/2] RISC-V IOMMU HPM support
Date: Thu, 24 Sep 2026 14:07:19 +0200 [thread overview]
Message-ID: <arUSRcgzWurL-YrL@8bytes.org> (raw)
In-Reply-To: <20260924100106.2054127-1-zong.li@sifive.com>
On Thu, Sep 24, 2026 at 03:01:03AM -0700, Zong Li wrote:
> This series implements support for the RISC-V IOMMU hardware performance
> monitor.
Do you have a link to the specification of the HPM (and additionally the IOMMU
itself)?
WARNING: multiple messages have this Message-ID (diff)
From: "Jörg Rödel" <joro@8bytes.org>
To: Zong Li <zong.li@sifive.com>
Cc: tomasz.jeznach@linux.dev, will@kernel.org, robin.murphy@arm.com,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, mark.rutland@arm.com,
andrew.jones@oss.qualcomm.com, guoren@kernel.org,
david.laight.linux@gmail.com,
zhangzhanpeng.jasper@bytedance.com, yang.yicong@picoheart.com,
nutty.liu@hotmail.com, iommu@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v14 0/2] RISC-V IOMMU HPM support
Date: Thu, 24 Sep 2026 14:07:19 +0200 [thread overview]
Message-ID: <arUSRcgzWurL-YrL@8bytes.org> (raw)
In-Reply-To: <20260924100106.2054127-1-zong.li@sifive.com>
On Thu, Sep 24, 2026 at 03:01:03AM -0700, Zong Li wrote:
> This series implements support for the RISC-V IOMMU hardware performance
> monitor.
Do you have a link to the specification of the HPM (and additionally the IOMMU
itself)?
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-09-24 12:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 10:01 [PATCH v14 0/2] RISC-V IOMMU HPM support Zong Li
2026-09-24 10:01 ` Zong Li
2026-09-24 10:01 ` [PATCH v14 1/2] drivers/perf: riscv-iommu: add risc-v iommu pmu driver Zong Li
2026-09-24 10:01 ` Zong Li
2026-09-24 10:12 ` sashiko-bot
2026-09-24 10:01 ` [PATCH v14 2/2] iommu/riscv: create a auxiliary device for HPM Zong Li
2026-09-24 10:01 ` Zong Li
2026-09-24 10:06 ` sashiko-bot
2026-09-24 12:07 ` Jörg Rödel [this message]
2026-09-24 12:07 ` [PATCH v14 0/2] RISC-V IOMMU HPM support Jörg Rödel
2026-09-24 14:13 ` Zong Li
2026-09-24 14:13 ` Zong Li
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=arUSRcgzWurL-YrL@8bytes.org \
--to=joro@8bytes.org \
--cc=alex@ghiti.fr \
--cc=andrew.jones@oss.qualcomm.com \
--cc=aou@eecs.berkeley.edu \
--cc=david.laight.linux@gmail.com \
--cc=guoren@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=nutty.liu@hotmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tomasz.jeznach@linux.dev \
--cc=will@kernel.org \
--cc=yang.yicong@picoheart.com \
--cc=zhangzhanpeng.jasper@bytedance.com \
--cc=zong.li@sifive.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 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.