From: Nicolin Chen <nicolinc@nvidia.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
Cc: "qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"ddutile@redhat.com" <ddutile@redhat.com>,
"berrange@redhat.com" <berrange@redhat.com>,
"imammedo@redhat.com" <imammedo@redhat.com>,
"nathanc@nvidia.com" <nathanc@nvidia.com>,
"mochs@nvidia.com" <mochs@nvidia.com>,
"smostafa@google.com" <smostafa@google.com>,
"gustavo.romero@linaro.org" <gustavo.romero@linaro.org>,
"mst@redhat.com" <mst@redhat.com>,
"marcel.apfelbaum@gmail.com" <marcel.apfelbaum@gmail.com>,
Linuxarm <linuxarm@huawei.com>,
"Wangzhou (B)" <wangzhou1@hisilicon.com>,
jiangkunkun <jiangkunkun@huawei.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
"zhangfei.gao@linaro.org" <zhangfei.gao@linaro.org>
Subject: Re: [PATCH v8 08/12] hw/arm/virt: Allow user-creatable SMMUv3 dev instantiation
Date: Fri, 18 Jul 2025 01:12:24 -0700 [thread overview]
Message-ID: <aHoB6HvXgkmkMQnv@Asurada-Nvidia> (raw)
In-Reply-To: <f793c36c2cf145b7842eb72795553824@huawei.com>
On Fri, Jul 18, 2025 at 08:01:22AM +0000, Shameerali Kolothum Thodi wrote:
> > > + int irq = platform_bus_get_irqn(pbus, sbdev, 0);
> > > + hwaddr base = platform_bus_get_mmio_addr(pbus, sbdev, 0);
> > > + MachineState *ms = MACHINE(vms);
> > > +
> > > + if (!(vms->bootinfo.firmware_loaded && virt_is_acpi_enabled(vms))
> > &&
> > > + strcmp("pcie.0", bus->qbus.name)) {
> > > + warn_report("SMMUv3 device only supported with pcie.0 for DT");
> > > + return;
> > > + }
> > > + base += vms->memmap[VIRT_PLATFORM_BUS].base;
> > > + irq += vms->irqmap[VIRT_PLATFORM_BUS];
> >
> > The code is fine.
> >
> > Just a related question here:
> >
> > Do you know where we define the number of IRQs and the range of
> > MMIO for the SysBusDevice?
> >
> > SMMU has four IRQs. And I see multiple vSMMU instances do have
> > correct intervals to their IRQ numbers, but I cannot find where
> > the magic is done.
>
> Look for,
> #define PLATFORM_BUS_NUM_IRQS 64
>
> So in theory we could have around 16 vSMMU per VM. It depends on
> other platform devices specified as well. Do you see a need for more
> on a per VM basis? I know there are host systems with large number of
> SMMUv3s, but how many a VM will get assigned realistically?
Hmm, I was asking how platform bus knows that SMMU only has four
IRQs. But I think number of 16 might not be enough in some cases.
So, my question was: where do we set the number of 4 to the sbdev?
As platform_bus_get_irqn() returned very correctly with 0, 4, 8,
and so on..
Thanks
Nicolin
next prev parent reply other threads:[~2025-07-18 8:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 8:47 [PATCH v8 00/12] hw/arm/virt: Add support for user creatable SMMUv3 device Shameer Kolothum via
2025-07-11 8:47 ` [PATCH v8 01/12] hw/arm/virt-acpi-build: Don't create ITS id mappings by default Shameer Kolothum via
2025-07-11 8:47 ` [PATCH v8 02/12] hw/arm/smmu-common: Check SMMU has PCIe Root Complex association Shameer Kolothum via
2025-07-11 8:47 ` [PATCH v8 03/12] hw/arm/virt-acpi-build: Re-arrange SMMUv3 IORT build Shameer Kolothum via
2025-07-11 8:47 ` [PATCH v8 04/12] hw/arm/virt-acpi-build: Update IORT for multiple smmuv3 devices Shameer Kolothum via
2025-07-11 8:47 ` [PATCH v8 05/12] hw/arm/virt: Factor out common SMMUV3 dt bindings code Shameer Kolothum via
2025-07-11 8:47 ` [PATCH v8 06/12] hw/arm/virt: Add an SMMU_IO_LEN macro Shameer Kolothum via
2025-07-11 8:47 ` [PATCH v8 07/12] hw/pci: Introduce pci_setup_iommu_per_bus() for per-bus IOMMU ops retrieval Shameer Kolothum via
2025-07-11 8:47 ` [PATCH v8 08/12] hw/arm/virt: Allow user-creatable SMMUv3 dev instantiation Shameer Kolothum via
2025-07-18 4:13 ` Nicolin Chen
2025-07-18 8:01 ` Shameerali Kolothum Thodi via
2025-07-18 8:12 ` Nicolin Chen [this message]
2025-07-18 8:22 ` Shameerali Kolothum Thodi via
2025-07-18 8:28 ` Nicolin Chen
2025-07-11 8:47 ` [PATCH v8 09/12] qemu-options.hx: Document the arm-smmuv3 device Shameer Kolothum via
2025-07-11 8:47 ` [PATCH v8 10/12] bios-tables-test: Allow for smmuv3 test data Shameer Kolothum via
2025-07-11 8:47 ` [PATCH v8 11/12] qtest/bios-tables-test: Add tests for legacy smmuv3 and smmuv3 device Shameer Kolothum via
2025-07-11 8:47 ` [PATCH v8 12/12] qtest/bios-tables-test: Update tables for smmuv3 tests Shameer Kolothum via
2025-07-18 4:00 ` [PATCH v8 00/12] hw/arm/virt: Add support for user creatable SMMUv3 device Nicolin Chen
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=aHoB6HvXgkmkMQnv@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=berrange@redhat.com \
--cc=ddutile@redhat.com \
--cc=eric.auger@redhat.com \
--cc=gustavo.romero@linaro.org \
--cc=imammedo@redhat.com \
--cc=jgg@nvidia.com \
--cc=jiangkunkun@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linuxarm@huawei.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mochs@nvidia.com \
--cc=mst@redhat.com \
--cc=nathanc@nvidia.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=smostafa@google.com \
--cc=wangzhou1@hisilicon.com \
--cc=zhangfei.gao@linaro.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).