All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shameerali Kolothum Thodi via <qemu-arm@nongnu.org>
To: "eric.auger@redhat.com" <eric.auger@redhat.com>,
	Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: Linuxarm <linuxarm@huawei.com>,
	"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
	"jgg@nvidia.com" <jgg@nvidia.com>,
	"nicolinc@nvidia.com" <nicolinc@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>,
	"Wangzhou (B)" <wangzhou1@hisilicon.com>,
	jiangkunkun <jiangkunkun@huawei.com>,
	"zhangfei.gao@linaro.org" <zhangfei.gao@linaro.org>
Subject: RE: [PATCH v4 1/7] hw/arm/smmu-common: Check SMMU has PCIe Root Complex association
Date: Thu, 19 Jun 2025 08:05:07 +0000	[thread overview]
Message-ID: <5fd7717fcd7e45d9aaff3e293cf63683@huawei.com> (raw)
In-Reply-To: <6e180d39-b1eb-4935-98b0-3ac73766e8aa@redhat.com>



> -----Original Message-----
> From: Eric Auger <eric.auger@redhat.com>
> Sent: Thursday, June 19, 2025 8:41 AM
> To: Shameerali Kolothum Thodi
> <shameerali.kolothum.thodi@huawei.com>; Jonathan Cameron
> <jonathan.cameron@huawei.com>
> Cc: Linuxarm <linuxarm@huawei.com>; qemu-arm@nongnu.org; qemu-
> devel@nongnu.org; peter.maydell@linaro.org; jgg@nvidia.com;
> nicolinc@nvidia.com; ddutile@redhat.com; berrange@redhat.com;
> imammedo@redhat.com; nathanc@nvidia.com; mochs@nvidia.com;
> smostafa@google.com; Wangzhou (B) <wangzhou1@hisilicon.com>;
> jiangkunkun <jiangkunkun@huawei.com>; zhangfei.gao@linaro.org
> Subject: Re: [PATCH v4 1/7] hw/arm/smmu-common: Check SMMU has PCIe
> Root Complex association
> 
> Hi Shameer,
> 
> On 6/19/25 9:24 AM, Shameerali Kolothum Thodi wrote:
> > Hi Eric,
> >
> >> -----Original Message-----
> >> From: Eric Auger <eric.auger@redhat.com>
> >> Sent: Wednesday, June 18, 2025 6:00 PM
> >> To: Shameerali Kolothum Thodi
> >> <shameerali.kolothum.thodi@huawei.com>; Jonathan Cameron
> >> <jonathan.cameron@huawei.com>
> >> Cc: Linuxarm <linuxarm@huawei.com>; qemu-arm@nongnu.org; qemu-
> >> devel@nongnu.org; peter.maydell@linaro.org; jgg@nvidia.com;
> >> nicolinc@nvidia.com; ddutile@redhat.com; berrange@redhat.com;
> >> imammedo@redhat.com; nathanc@nvidia.com; mochs@nvidia.com;
> >> smostafa@google.com; Wangzhou (B) <wangzhou1@hisilicon.com>;
> >> jiangkunkun <jiangkunkun@huawei.com>; zhangfei.gao@linaro.org
> >> Subject: Re: [PATCH v4 1/7] hw/arm/smmu-common: Check SMMU has
> PCIe
> >> Root Complex association
> >>
> >> Hi Shameer, Jonathan,
> >>
> >> On 6/18/25 10:35 AM, Shameerali Kolothum Thodi wrote:
> >>>> -----Original Message-----
> >>>> From: Jonathan Cameron <jonathan.cameron@huawei.com>
> >>>> Sent: Tuesday, June 17, 2025 5:53 PM
> >>>> To: Eric Auger <eric.auger@redhat.com>
> >>>> Cc: Shameerali Kolothum Thodi
> >>>> <shameerali.kolothum.thodi@huawei.com>; Linuxarm
> >>>> <linuxarm@huawei.com>; qemu-arm@nongnu.org; qemu-
> >>>> devel@nongnu.org; peter.maydell@linaro.org; jgg@nvidia.com;
> >>>> nicolinc@nvidia.com; ddutile@redhat.com; berrange@redhat.com;
> >>>> imammedo@redhat.com; nathanc@nvidia.com; mochs@nvidia.com;
> >>>> smostafa@google.com; Wangzhou (B) <wangzhou1@hisilicon.com>;
> >>>> jiangkunkun <jiangkunkun@huawei.com>; zhangfei.gao@linaro.org
> >>>> Subject: Re: [PATCH v4 1/7] hw/arm/smmu-common: Check SMMU has
> >> PCIe
> >>>> Root Complex association
> >>>>
> >>>> On Tue, 17 Jun 2025 09:49:54 +0200
> >>>> Eric Auger <eric.auger@redhat.com> wrote:
> >>>>
> >>>>> On 6/16/25 12:20 PM, Jonathan Cameron wrote:
> >>>>>> On Fri, 13 Jun 2025 15:44:43 +0100
> >>>>>> Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> wrote:
> >>>>>>
> >>>>>>> Although this change does not affect functionality at present, it is
> >>>>>> Patch title says PCIe.  This check is vs PCI host bridge.
> >>>>>>
> >>>>>> No idea which one you wanted, but if it is PCIe needs to be
> >>>>>> TYPC_PCIE_HOST_BRIDGE from pcie_host.h not the pci_host.h one
> >>>>>> I think.
> >>>>> I think we need TYPE_PCI_HOST_BRIDGE as we want to check against
> >> pxb
> >>>>> pci-bridge/pci_expander_bridge.c:    .parent        =
> >>>> TYPE_PCI_HOST_BRIDGE,
> >> sorry but I still fail to understand why we can't just check against
> >>
> >> TYPE_PCI_HOST_BRIDGE for making sure the SMMU is attached to PXB or
> >> GPEX. What does it fail to check? Why shall we care about PCI vs PCIe?
> > I think the concern is  getting any other TYPE_PCI_HOST_BRIDGE types
> attached
> > to SMMUv3 other than pxb-pcie or GPEX. For example you could do,
> >
> > -device pxb-cxl,bus_nr=12,bus=pcie.0,id=cxl.1 \
> > -device arm-smmuv3,primary-bus=cxl.1,id=smmuv3.1 \
> >
> > as pxb-cxl is of type TYPE_PCI_HOST_BRIDGE. I don't know if there are any
> other
> > ones similar to this out there.
> >
> > So the aim is to make the checking more specific to PXB.
> 
> thank you for the clarification. Is it invalid to have the SMMU
> protecting RIDs comming from the pxb-cxl hierarchy?

That’s a good question. I don't know that for sure.
Anyway currently the full support for CXL on virt is in progress here,
https://lore.kernel.org/qemu-devel/20250612134338.1871023-1-Jonathan.Cameron@huawei.com/

Jonathan?

Thanks,
Shameer

> 


WARNING: multiple messages have this Message-ID (diff)
From: Shameerali Kolothum Thodi via <qemu-devel@nongnu.org>
To: "eric.auger@redhat.com" <eric.auger@redhat.com>,
	Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: Linuxarm <linuxarm@huawei.com>,
	"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
	"jgg@nvidia.com" <jgg@nvidia.com>,
	"nicolinc@nvidia.com" <nicolinc@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>,
	"Wangzhou (B)" <wangzhou1@hisilicon.com>,
	jiangkunkun <jiangkunkun@huawei.com>,
	"zhangfei.gao@linaro.org" <zhangfei.gao@linaro.org>
Subject: RE: [PATCH v4 1/7] hw/arm/smmu-common: Check SMMU has PCIe Root Complex association
Date: Thu, 19 Jun 2025 08:05:07 +0000	[thread overview]
Message-ID: <5fd7717fcd7e45d9aaff3e293cf63683@huawei.com> (raw)
In-Reply-To: <6e180d39-b1eb-4935-98b0-3ac73766e8aa@redhat.com>



> -----Original Message-----
> From: Eric Auger <eric.auger@redhat.com>
> Sent: Thursday, June 19, 2025 8:41 AM
> To: Shameerali Kolothum Thodi
> <shameerali.kolothum.thodi@huawei.com>; Jonathan Cameron
> <jonathan.cameron@huawei.com>
> Cc: Linuxarm <linuxarm@huawei.com>; qemu-arm@nongnu.org; qemu-
> devel@nongnu.org; peter.maydell@linaro.org; jgg@nvidia.com;
> nicolinc@nvidia.com; ddutile@redhat.com; berrange@redhat.com;
> imammedo@redhat.com; nathanc@nvidia.com; mochs@nvidia.com;
> smostafa@google.com; Wangzhou (B) <wangzhou1@hisilicon.com>;
> jiangkunkun <jiangkunkun@huawei.com>; zhangfei.gao@linaro.org
> Subject: Re: [PATCH v4 1/7] hw/arm/smmu-common: Check SMMU has PCIe
> Root Complex association
> 
> Hi Shameer,
> 
> On 6/19/25 9:24 AM, Shameerali Kolothum Thodi wrote:
> > Hi Eric,
> >
> >> -----Original Message-----
> >> From: Eric Auger <eric.auger@redhat.com>
> >> Sent: Wednesday, June 18, 2025 6:00 PM
> >> To: Shameerali Kolothum Thodi
> >> <shameerali.kolothum.thodi@huawei.com>; Jonathan Cameron
> >> <jonathan.cameron@huawei.com>
> >> Cc: Linuxarm <linuxarm@huawei.com>; qemu-arm@nongnu.org; qemu-
> >> devel@nongnu.org; peter.maydell@linaro.org; jgg@nvidia.com;
> >> nicolinc@nvidia.com; ddutile@redhat.com; berrange@redhat.com;
> >> imammedo@redhat.com; nathanc@nvidia.com; mochs@nvidia.com;
> >> smostafa@google.com; Wangzhou (B) <wangzhou1@hisilicon.com>;
> >> jiangkunkun <jiangkunkun@huawei.com>; zhangfei.gao@linaro.org
> >> Subject: Re: [PATCH v4 1/7] hw/arm/smmu-common: Check SMMU has
> PCIe
> >> Root Complex association
> >>
> >> Hi Shameer, Jonathan,
> >>
> >> On 6/18/25 10:35 AM, Shameerali Kolothum Thodi wrote:
> >>>> -----Original Message-----
> >>>> From: Jonathan Cameron <jonathan.cameron@huawei.com>
> >>>> Sent: Tuesday, June 17, 2025 5:53 PM
> >>>> To: Eric Auger <eric.auger@redhat.com>
> >>>> Cc: Shameerali Kolothum Thodi
> >>>> <shameerali.kolothum.thodi@huawei.com>; Linuxarm
> >>>> <linuxarm@huawei.com>; qemu-arm@nongnu.org; qemu-
> >>>> devel@nongnu.org; peter.maydell@linaro.org; jgg@nvidia.com;
> >>>> nicolinc@nvidia.com; ddutile@redhat.com; berrange@redhat.com;
> >>>> imammedo@redhat.com; nathanc@nvidia.com; mochs@nvidia.com;
> >>>> smostafa@google.com; Wangzhou (B) <wangzhou1@hisilicon.com>;
> >>>> jiangkunkun <jiangkunkun@huawei.com>; zhangfei.gao@linaro.org
> >>>> Subject: Re: [PATCH v4 1/7] hw/arm/smmu-common: Check SMMU has
> >> PCIe
> >>>> Root Complex association
> >>>>
> >>>> On Tue, 17 Jun 2025 09:49:54 +0200
> >>>> Eric Auger <eric.auger@redhat.com> wrote:
> >>>>
> >>>>> On 6/16/25 12:20 PM, Jonathan Cameron wrote:
> >>>>>> On Fri, 13 Jun 2025 15:44:43 +0100
> >>>>>> Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> wrote:
> >>>>>>
> >>>>>>> Although this change does not affect functionality at present, it is
> >>>>>> Patch title says PCIe.  This check is vs PCI host bridge.
> >>>>>>
> >>>>>> No idea which one you wanted, but if it is PCIe needs to be
> >>>>>> TYPC_PCIE_HOST_BRIDGE from pcie_host.h not the pci_host.h one
> >>>>>> I think.
> >>>>> I think we need TYPE_PCI_HOST_BRIDGE as we want to check against
> >> pxb
> >>>>> pci-bridge/pci_expander_bridge.c:    .parent        =
> >>>> TYPE_PCI_HOST_BRIDGE,
> >> sorry but I still fail to understand why we can't just check against
> >>
> >> TYPE_PCI_HOST_BRIDGE for making sure the SMMU is attached to PXB or
> >> GPEX. What does it fail to check? Why shall we care about PCI vs PCIe?
> > I think the concern is  getting any other TYPE_PCI_HOST_BRIDGE types
> attached
> > to SMMUv3 other than pxb-pcie or GPEX. For example you could do,
> >
> > -device pxb-cxl,bus_nr=12,bus=pcie.0,id=cxl.1 \
> > -device arm-smmuv3,primary-bus=cxl.1,id=smmuv3.1 \
> >
> > as pxb-cxl is of type TYPE_PCI_HOST_BRIDGE. I don't know if there are any
> other
> > ones similar to this out there.
> >
> > So the aim is to make the checking more specific to PXB.
> 
> thank you for the clarification. Is it invalid to have the SMMU
> protecting RIDs comming from the pxb-cxl hierarchy?

That’s a good question. I don't know that for sure.
Anyway currently the full support for CXL on virt is in progress here,
https://lore.kernel.org/qemu-devel/20250612134338.1871023-1-Jonathan.Cameron@huawei.com/

Jonathan?

Thanks,
Shameer

> 


  reply	other threads:[~2025-06-19  8:05 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 14:44 [PATCH v4 0/7] hw/arm/virt: Add support for user creatable SMMUv3 device Shameer Kolothum via
2025-06-13 14:44 ` Shameer Kolothum via
2025-06-13 14:44 ` [PATCH v4 1/7] hw/arm/smmu-common: Check SMMU has PCIe Root Complex association Shameer Kolothum via
2025-06-13 14:44   ` Shameer Kolothum via
2025-06-16  5:04   ` Nicolin Chen
2025-06-16 10:20   ` Jonathan Cameron via
2025-06-16 10:20     ` Jonathan Cameron via
2025-06-16 11:20     ` Shameerali Kolothum Thodi via
2025-06-16 11:20       ` Shameerali Kolothum Thodi via
2025-06-17  7:49     ` Eric Auger
2025-06-17 16:52       ` Jonathan Cameron via
2025-06-17 16:52         ` Jonathan Cameron via
2025-06-17 19:11         ` Donald Dutile
2025-06-18  8:35         ` Shameerali Kolothum Thodi via
2025-06-18  8:35           ` Shameerali Kolothum Thodi via
2025-06-18 10:38           ` Jonathan Cameron via
2025-06-18 10:38             ` Jonathan Cameron via
2025-06-18 16:59           ` Eric Auger
2025-06-19  7:24             ` Shameerali Kolothum Thodi via
2025-06-19  7:24               ` Shameerali Kolothum Thodi via
2025-06-19  7:41               ` Eric Auger
2025-06-19  8:05                 ` Shameerali Kolothum Thodi via [this message]
2025-06-19  8:05                   ` Shameerali Kolothum Thodi via
2025-06-19  9:30                   ` Jonathan Cameron via
2025-06-19  9:38                     ` Jonathan Cameron via
2025-06-19  9:38                       ` Jonathan Cameron via
2025-06-20 11:50                       ` Jonathan Cameron via
2025-06-20 11:50                         ` Jonathan Cameron via
2025-06-13 14:44 ` [PATCH v4 2/7] hw/arm/virt-acpi-build: Re-arrange SMMUv3 IORT build Shameer Kolothum via
2025-06-13 14:44   ` Shameer Kolothum via
2025-06-16  5:20   ` Nicolin Chen
2025-06-16 10:32   ` Jonathan Cameron via
2025-06-16 10:32     ` Jonathan Cameron via
2025-06-17  9:09   ` Eric Auger
2025-06-13 14:44 ` [PATCH v4 3/7] hw/arm/virt-acpi-build: Update IORT for multiple smmuv3 devices Shameer Kolothum via
2025-06-13 14:44   ` Shameer Kolothum via
2025-06-16  5:25   ` Nicolin Chen
2025-06-16 10:55   ` Jonathan Cameron via
2025-06-16 10:55     ` Jonathan Cameron via
2025-06-16 11:22     ` Shameerali Kolothum Thodi via
2025-06-16 11:22       ` Shameerali Kolothum Thodi via
2025-06-17  9:21   ` Eric Auger
2025-06-13 14:44 ` [PATCH v4 4/7] hw/arm/virt: Factor out common SMMUV3 dt bindings code Shameer Kolothum via
2025-06-16 10:57   ` Jonathan Cameron via
2025-06-16 10:57     ` Jonathan Cameron via
2025-06-13 14:44 ` [PATCH v4 5/7] hw/arm/virt: Add an SMMU_IO_LEN macro Shameer Kolothum via
2025-06-13 14:44   ` Shameer Kolothum via
2025-06-16 11:02   ` Jonathan Cameron via
2025-06-16 11:02     ` Jonathan Cameron via
2025-06-16 11:26     ` Shameerali Kolothum Thodi via
2025-06-16 11:26       ` Shameerali Kolothum Thodi via
2025-06-13 14:44 ` [PATCH v4 6/7] hw/arm/virt: Allow user-creatable SMMUv3 dev instantiation Shameer Kolothum via
2025-06-16  5:31   ` Nicolin Chen
2025-06-16 12:31     ` Shameerali Kolothum Thodi via
2025-06-16 12:31       ` Shameerali Kolothum Thodi via
2025-06-16 11:05   ` Jonathan Cameron via
2025-06-17  9:25   ` Eric Auger
2025-06-13 14:44 ` [PATCH v4 7/7] qemu-options.hx: Document the arm-smmuv3 device Shameer Kolothum via
2025-06-16  5:33   ` Nicolin Chen
2025-06-16 11:12   ` Jonathan Cameron via
2025-06-16 11:12     ` Jonathan Cameron via
2025-06-16 11:24     ` Shameerali Kolothum Thodi via
2025-06-16 17:28     ` Donald Dutile

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=5fd7717fcd7e45d9aaff3e293cf63683@huawei.com \
    --to=qemu-arm@nongnu.org \
    --cc=berrange@redhat.com \
    --cc=ddutile@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=jiangkunkun@huawei.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linuxarm@huawei.com \
    --cc=mochs@nvidia.com \
    --cc=nathanc@nvidia.com \
    --cc=nicolinc@nvidia.com \
    --cc=peter.maydell@linaro.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 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.