From: Will Deacon <will@kernel.org>
To: "guoyaxing@bosc.ac.cn" <guoyaxing@bosc.ac.cn>
Cc: linux-riscv <linux-riscv@lists.infradead.org>,
iommu <iommu@lists.linux.dev>, tjeznach <tjeznach@rivosinc.com>,
joro <joro@8bytes.org>, "robin.murphy" <robin.murphy@arm.com>,
"paul.walmsley" <paul.walmsley@sifive.com>,
palmer <palmer@dabbelt.com>, aou <aou@eecs.berkeley.edu>,
alex <alex@ghiti.fr>, anxu <anxu@bosc.ac.cn>,
wangran <wangran@bosc.ac.cn>
Subject: Re: Re: [PATCH v1 1/3] iommu/riscv: Add iommu perf driver
Date: Wed, 17 Sep 2025 13:10:47 +0100 [thread overview]
Message-ID: <aMqlR4vDOgrFuCUj@willie-the-truck> (raw)
In-Reply-To: <202509161827232434929@bosc.ac.cn>
[nit: your email client has made a big mess of the thread here]
On Tue, Sep 16, 2025 at 06:27:23PM +0800, guoyaxing@bosc.ac.cn wrote:
> > PMU drivers are better placed under drivers/perf/
>
> I did a quick reading of SMMU pmu driver in drivers/perf/. However, If
> the RISC-V IOMMU PMU driver is placed under drivers/perf/ as the SMMU did,
> it would cause an overlap in the iomem resource region between the two
> devices(iommu & iommu pmu), because it needs to share interrupt-related
> registers (such as the IPSR register) with the main IOMMU driver.
Is that not something you can resolve with IRQF_SHARED?
Will
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-09-17 12:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 2:09 [PATCH v1 1/3] iommu/riscv: Add iommu perf driver Yaxing Guo
2025-09-15 2:09 ` [PATCH v1 2/3] iommu/riscv: Add Makefile support for RISC-V IOMMU " Yaxing Guo
2025-09-16 3:40 ` kernel test robot
2025-09-15 2:09 ` [PATCH v1 3/3] iommu/riscv: Register RISC-V IOMMU PMU at init time Yaxing Guo
2025-09-15 10:38 ` [PATCH v1 1/3] iommu/riscv: Add iommu perf driver Will Deacon
2025-09-16 10:27 ` guoyaxing
2025-09-17 12:10 ` Will Deacon [this message]
2025-09-18 3:20 ` 郭亚星
2025-09-18 14:20 ` Will Deacon
2025-09-16 1:47 ` kernel test robot
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=aMqlR4vDOgrFuCUj@willie-the-truck \
--to=will@kernel.org \
--cc=alex@ghiti.fr \
--cc=anxu@bosc.ac.cn \
--cc=aou@eecs.berkeley.edu \
--cc=guoyaxing@bosc.ac.cn \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robin.murphy@arm.com \
--cc=tjeznach@rivosinc.com \
--cc=wangran@bosc.ac.cn \
/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