emu-devel@nongnu.org; Linuxarm
> ; Wangzhou (B) ;
> jiangkunkun ; Jonathan Cameron
> ; zhangfei@linaro.org; Peng, Chao P
>
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> Hi Shammeer,
>
Hi Eric,
> >
> >
utile
>> Cc: eric.au...@redhat.com; Peter Maydell ;
>> Jason Gunthorpe ; Daniel P. Berrangé
>> ; qemu-...@nongnu.org; qemu-
>> de...@nongnu.org; Linuxarm ; Wangzhou (B)
>> ; jiangkunkun ;
>> Jonathan Cameron ;
>> zhangfei....@linaro.org; Peng, Chao P
>>
utile
>> Cc: Peter Maydell ; Jason Gunthorpe
>> ; Daniel P. Berrangé ; qemu-
>> a...@nongnu.org; qemu-devel@nongnu.org; Linuxarm
>> ; Wangzhou (B) ;
>> jiangkunkun ; Jonathan Cameron
>> ; zhangfei....@linaro.org; Peng, Chao P
>>
>> Subject: Re: [RFC PATCH
Linuxarm ; Wangzhou
> (B) ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei....@linaro.org
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Mon, Mar 03, 2025 at 03:21:57PM +, Shameerali Kolothum Thodi
> wrote:
> > I am wor
On Mon, Mar 03, 2025 at 03:21:57PM +, Shameerali Kolothum Thodi wrote:
> I am working on the above now and have quick question to youđ.
>
> Looking at the smmu_dev_attach_viommu() fn here[0],
> it appears to do the following:
>
> 1. Alloc a s2_hwpt if not allocated already and attach it.
> 2.
vel@nongnu.org; Linuxarm ; Wangzhou
> (B) ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei....@linaro.org
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
[..]
> > One of the feedback I received on my series was to rename "arm-smm
-...@nongnu.org; qemu-
> de...@nongnu.org; Linuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei@linaro.org; Peng, Chao P
> Subject: RE: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> Hi Shameer, Nicolin,
>
[...
Hi Shameer, Nicolin,
>-Original Message-
>From: Duan, Zhenzhong
>Subject: RE: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable nested
>SMMUv3
>
>Hi Shameer,
>
>>-Original Message-
>>From: Shameerali Kolothum Thodi
>>Subject: RE: [
On Fri, Feb 07, 2025 at 12:21:54PM +, Shameerali Kolothum Thodi wrote:
> Just wondering whether we can have something like the
> vfio_register_iommu_driver() for iommufd subsystem by which it can directly
> access iommu drivers ops(may be a restricted set).
I very much want to try hard to av
g; ddut...@redhat.com;
> Linuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei@linaro.org; nath...@nvidia.com
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Fri, Feb 07, 2025 at 10:21:
nthorpe
> > Cc: qemu-...@nongnu.org; qemu-devel@nongnu.org;
> > eric.au...@redhat.com; peter.mayd...@linaro.org; ddut...@redhat.com;
> > Linuxarm ; Wangzhou (B)
> > ; jiangkunkun ;
> > Jonathan Cameron ;
> > zhangfei....@linaro.org; nath...@nvidia.com
> >
.org; ddut...@redhat.com;
> Linuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei@linaro.org; nath...@nvidia.com
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Thu, Feb 06, 2025 at 02:22:01PM -0400, Jason
On Thu, Feb 06, 2025 at 02:46:42PM -0800, Nicolin Chen wrote:
> > You'd use the command line information and wouldn't need GET_HW_INFO,
> > it would be complicated
>
> Do you mean the "-device arm-smmuv3-accel,id=xx" line? This still
> won't give us the host IDR/IIDR register values to probe a vSM
On Thu, Feb 06, 2025 at 05:11:13PM -0400, Jason Gunthorpe wrote:
> On Thu, Feb 06, 2025 at 12:48:40PM -0800, Nicolin Chen wrote:
> > On Thu, Feb 06, 2025 at 04:38:55PM -0400, Jason Gunthorpe wrote:
> > > On Thu, Feb 06, 2025 at 12:33:19PM -0800, Nicolin Chen wrote:
> > > > On Thu, Feb 06, 2025 at 0
On Thu, Feb 06, 2025 at 12:48:40PM -0800, Nicolin Chen wrote:
> On Thu, Feb 06, 2025 at 04:38:55PM -0400, Jason Gunthorpe wrote:
> > On Thu, Feb 06, 2025 at 12:33:19PM -0800, Nicolin Chen wrote:
> > > On Thu, Feb 06, 2025 at 02:22:01PM -0400, Jason Gunthorpe wrote:
> > > > On Thu, Feb 06, 2025 at 0
On Thu, Feb 06, 2025 at 04:38:55PM -0400, Jason Gunthorpe wrote:
> On Thu, Feb 06, 2025 at 12:33:19PM -0800, Nicolin Chen wrote:
> > On Thu, Feb 06, 2025 at 02:22:01PM -0400, Jason Gunthorpe wrote:
> > > On Thu, Feb 06, 2025 at 06:18:14PM +, Shameerali Kolothum Thodi wrote:
> > >
> > > > > So
On Thu, Feb 06, 2025 at 12:33:19PM -0800, Nicolin Chen wrote:
> On Thu, Feb 06, 2025 at 02:22:01PM -0400, Jason Gunthorpe wrote:
> > On Thu, Feb 06, 2025 at 06:18:14PM +, Shameerali Kolothum Thodi wrote:
> >
> > > > So even if you invent an iommu ID we cannot accept it as a handle to
> > > > c
On Thu, Feb 06, 2025 at 02:22:01PM -0400, Jason Gunthorpe wrote:
> On Thu, Feb 06, 2025 at 06:18:14PM +, Shameerali Kolothum Thodi wrote:
>
> > > So even if you invent an iommu ID we cannot accept it as a handle to
> > > create viommu in iommufd.
> >
> > Creating the vIOMMU only happens when
On Thu, Feb 06, 2025 at 10:34:15AM +, Shameerali Kolothum Thodi wrote:
> > -Original Message-
> > From: Nicolin Chen
> > On Tue, Feb 04, 2025 at 06:49:15PM +0100, Eric Auger wrote:
> > > However in
> > >
> > > Shameer suggested he may include it in his SMMU multi instance series.
> > >
On Thu, Feb 06, 2025 at 06:18:14PM +, Shameerali Kolothum Thodi wrote:
> > So even if you invent an iommu ID we cannot accept it as a handle to
> > create viommu in iommufd.
>
> Creating the vIOMMU only happens when the user does a cold/hot plug of
> a VFIO device. At that time Qemu checks w
m; ddut...@redhat.com;
> Linuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei@linaro.org; nath...@nvidia.com
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Thu, Feb 06, 2025 at 06:04:57PM +, Shame
On Thu, Feb 06, 2025 at 01:58:43PM -0400, Jason Gunthorpe wrote:
> On Thu, Feb 06, 2025 at 05:54:57PM +, Daniel P. Berrangé wrote:
> > > > We shouldn't assume any VFIO device exists in the QEMU cnofig at the
> > > > time
> > > > we realize the virtual ssmu. I expect the SMMU may be cold plugge
On Thu, Feb 06, 2025 at 06:04:57PM +, Shameerali Kolothum Thodi wrote:
> > Some kind of hot plug smmu would have to create a vSMMU without any
> > kernel backing and then later bind it to a kernel implementation.
>
> Not sure I get the problem with associating vSMMU with a pSMMU. Something
> l
.com; ddut...@redhat.com;
> Linuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei@linaro.org; nath...@nvidia.com
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Thu, Feb 06, 2025 at 05:54:57PM +
On Thu, Feb 06, 2025 at 05:54:57PM +, Daniel P. Berrangé wrote:
> > > We shouldn't assume any VFIO device exists in the QEMU cnofig at the time
> > > we realize the virtual ssmu. I expect the SMMU may be cold plugged, while
> > > the VFIO devices may be hot plugged arbitrarly later, and we shou
On Thu, Feb 06, 2025 at 05:57:38PM +, Shameerali Kolothum Thodi wrote:
> Also how do we do it with multiple VF devices under a pSUMMU ? Which
> cdev fd in that case?
It doesn't matter, they are all interchangeable. Creating the VIOMMU
object just requires any vfio device that is attached to
.com; ddut...@redhat.com;
> Linuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei@linaro.org; nath...@nvidia.com
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Thu, Feb 06, 2025 at 05:10:32PM +, Da
On Thu, Feb 06, 2025 at 01:46:47PM -0400, Jason Gunthorpe wrote:
> On Thu, Feb 06, 2025 at 05:10:32PM +, Daniel P. Berrangé wrote:
> > On Thu, Feb 06, 2025 at 01:02:38PM -0400, Jason Gunthorpe wrote:
> > > On Thu, Feb 06, 2025 at 03:07:06PM +, Shameerali Kolothum Thodi wrote:
> > > > > If w
On Thu, Feb 06, 2025 at 05:10:32PM +, Daniel P. Berrangé wrote:
> On Thu, Feb 06, 2025 at 01:02:38PM -0400, Jason Gunthorpe wrote:
> > On Thu, Feb 06, 2025 at 03:07:06PM +, Shameerali Kolothum Thodi wrote:
> > > > If we set the physical/guest SMMU relationship directly, then at the
> > > >
On Thu, Feb 06, 2025 at 01:02:38PM -0400, Jason Gunthorpe wrote:
> On Thu, Feb 06, 2025 at 03:07:06PM +, Shameerali Kolothum Thodi wrote:
> > > If we set the physical/guest SMMU relationship directly, then at the
> > > time the VFIO device is plugged, we can diagnose the incorrectly
> > > place
On Thu, Feb 06, 2025 at 03:07:06PM +, Shameerali Kolothum Thodi wrote:
> > If we set the physical/guest SMMU relationship directly, then at the
> > time the VFIO device is plugged, we can diagnose the incorrectly
> > placed VFIO device, and better reason about behaviour.
>
> Agree.
Can you ju
hat.com;
>>>> Linuxarm ; Wangzhou (B)
>>>> ; jiangkunkun ;
>>>> Jonathan Cameron ;
>>>> zhangfei@linaro.org; Nathan Chen
>>>> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
>>>> nested SMMUv3
>
m; ddut...@redhat.com; Linuxarm
> ; Wangzhou (B) ;
> jiangkunkun ; Jonathan Cameron
> ; zhangfei@linaro.org;
> nath...@nvidia.com
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Thu, Feb 06, 2025 at 01:51:15PM +, Shamee
On Thu, Feb 06, 2025 at 01:51:15PM +, Shameerali Kolothum Thodi wrote:
> Hmm..I donât think just swapping the order will change the association with
> Guest SMMU here. Because, we have,
>
> > -device arm-smmuv3-accel,id=smmuv2,bus=pcie.2
>
> During smmuv3-accel realize time, this will result
m; ddut...@redhat.com; Linuxarm
> ; Wangzhou (B) ;
> jiangkunkun ; Jonathan Cameron
> ; zhangfei@linaro.org;
> nath...@nvidia.com
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Thu, Feb 06, 2025 at 10:02:25AM +, Sha
; qemu-devel@nongnu.org;
> > eric.au...@redhat.com; peter.mayd...@linaro.org; j...@nvidia.com;
> > nicol...@nvidia.com; ddut...@redhat.com; Linuxarm
> > ; Wangzhou (B) ;
> > jiangkunkun ; Jonathan Cameron
> > ; zhangfei@linaro.org
> > Subject: Re: [RFC PATCH 0/5] h
-devel@nongnu.org; Linuxarm
> ; Wangzhou (B) ;
> jiangkunkun ; Jonathan Cameron
> ; zhangfei@linaro.org
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Tue, Feb 04, 2025 at 06:49:15PM +0100, Eric Auger wrote:
> > &g
l...@nvidia.com; ddut...@redhat.com; Linuxarm
> ; Wangzhou (B) ;
> jiangkunkun ; Jonathan Cameron
> ; zhangfei....@linaro.org
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Thu, Jan 30, 2025 at 06:09:24PM +, Shameerali Kolothum Thod
On Wed, Feb 05, 2025 at 12:53:42PM -0800, Nathan Chen wrote:
>
>
> On 1/31/2025 8:08 AM, Eric Auger wrote:
> > > > > > > And Qemu does some checking to make sure that the device is indeed
> > > > > > associated
> > > > > > > with the specified phys-smmuv3. This can be done going through
> > > >
>> Jonathan Cameron ;
> >> zhangfei....@linaro.org; Nathan Chen
> >> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> >> nested SMMUv3
> >>
> >> On Fri, Jan 31, 2025 at 02:39:53PM +, Shameerali Kolothum Thodi
> &
On 1/31/2025 8:08 AM, Eric Auger wrote:
And Qemu does some checking to make sure that the device is indeed
associated
with the specified phys-smmuv3. This can be done going through the
sysfs path checking
which is what I guess libvirt is currently doing to populate the
topology.
So basi
Hi Nicolin,
On 2/5/25 1:08 AM, Nicolin Chen wrote:
> On Tue, Feb 04, 2025 at 06:49:15PM +0100, Eric Auger wrote:
>>> In summary, we will have the following series:
>>> 1) HWPT uAPI patches in backends/iommufd.c (Zhenzhong or Shameer)
>>>
>>> https://lore.kernel.org/qemu-devel/sj0pr11mb6744943
-devel@nongnu.org; Linuxarm
> ; Wangzhou (B) ;
> jiangkunkun ; Jonathan Cameron
> ; zhangfei@linaro.org
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Tue, Feb 04, 2025 at 06:49:15PM +0100, Eric Auger wrote:
> > > In summa
On Tue, Feb 04, 2025 at 06:49:15PM +0100, Eric Auger wrote:
> > In summary, we will have the following series:
> > 1) HWPT uAPI patches in backends/iommufd.c (Zhenzhong or Shameer)
> >
> > https://lore.kernel.org/qemu-devel/sj0pr11mb6744943702eb5798ec9b3b9992...@sj0pr11mb6744.namprd11.prod.outl
Hi Nicolin, Shameer,
On 2/3/25 7:50 PM, Nicolin Chen wrote:
> On Fri, Jan 31, 2025 at 05:54:56PM +0100, Eric Auger wrote:
>> On 1/9/25 5:45 AM, Nicolin Chen wrote:
>>> On Mon, Dec 16, 2024 at 10:01:29AM +, Shameerali Kolothum Thodi wrote:
And patches prior to this commit adds that support
Hi Nathan,
On 11/22/24 7:53 PM, Nathan Chen wrote:
> >Â >> Also as a heads up, I've added support for auto-inserting PCIe
> switch
> >Â >> between the PXB and GPUs in libvirt to attach multiple devices to a
> > SMMU
> >Â >> node per libvirt's documentation - "If you intend to plug multiple
> >Â >
On Fri, Jan 31, 2025 at 05:54:56PM +0100, Eric Auger wrote:
> On 1/9/25 5:45 AM, Nicolin Chen wrote:
> > On Mon, Dec 16, 2024 at 10:01:29AM +, Shameerali Kolothum Thodi wrote:
> >> And patches prior to this commit adds that support:
> >> 4ccdbe3: ("cover-letter: Add HW accelerated nesting supp
On Thu, Jan 30, 2025 at 06:09:24PM +, Shameerali Kolothum Thodi wrote:
>
> Each "arm-smmuv3-nested" instance, when the first device gets attached
> to it, will create a S2 HWPT and a corresponding SMMUv3 domain in kernel
> SMMUv3 driver. This domain will have a pointer representing the physica
Hi Nicolin,
On 1/9/25 5:45 AM, Nicolin Chen wrote:
> On Mon, Dec 16, 2024 at 10:01:29AM +, Shameerali Kolothum Thodi wrote:
>> And patches prior to this commit adds that support:
>> 4ccdbe3: ("cover-letter: Add HW accelerated nesting support for arm
>> SMMUv3")
>>
>> Nicolin is soon going to
devel@nongnu.org; eric.au...@redhat.com;
>> peter.mayd...@linaro.org; nicol...@nvidia.com; ddut...@redhat.com;
>> Linuxarm ; Wangzhou (B)
>> ; jiangkunkun ;
>> Jonathan Cameron ;
>> zhangfei@linaro.org; Nathan Chen
>> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add supp
m; ddut...@redhat.com;
> Linuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei@linaro.org; Nathan Chen
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Fri, Jan 31, 2025 at 02:39:53PM +, Shameerali Kol
On Fri, Jan 31, 2025 at 02:39:53PM +, Shameerali Kolothum Thodi wrote:
> > > And Qemu does some checking to make sure that the device is indeed
> > associated
> > > with the specified phys-smmuv3. This can be done going through the
> > sysfs path checking
> > > which is what I guess libvirt i
m; ddut...@redhat.com;
> Linuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei@linaro.org; Nathan Chen
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Fri, Jan 31, 2025 at 09:33:16AM +, Shameerali
On Fri, Jan 31, 2025 at 09:33:16AM +, Shameerali Kolothum Thodi wrote:
> And Qemu does some checking to make sure that the device is indeed associated
> with the specified phys-smmuv3. This can be done going through the sysfs
> path checking
> which is what I guess libvirt is currently doing
u.org;
>> eric.au...@redhat.com; peter.mayd...@linaro.org; j...@nvidia.com;
>> nicol...@nvidia.com; ddut...@redhat.com; Linuxarm
>> ; Wangzhou (B) ;
>> jiangkunkun ; Jonathan Cameron
>> ; zhangfei....@linaro.org
>> Subject: RE: [RFC PATCH 0/5] hw/arm/virt: Add su
@nvidia.com; ddut...@redhat.com; Linuxarm
> ; Wangzhou (B) ;
> jiangkunkun ; Jonathan Cameron
> ; zhangfei....@linaro.org
> Subject: RE: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> Hi Daniel,
>
> > -Original Message-
> >
l...@nvidia.com; ddut...@redhat.com; Linuxarm
> ; Wangzhou (B) ;
> jiangkunkun ; Jonathan Cameron
> ; zhangfei....@linaro.org
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Fri, Nov 08, 2024 at 12:52:37PM +, Shameer Kolothum via w
On Mon, Nov 18, 2024 at 11:50:46AM +0100, Eric Auger wrote:
> Hi Shameer,
>
> On 11/8/24 13:52, Shameer Kolothum wrote:
> > Hi,
> >
> > This series adds initial support for a user-creatable "arm-smmuv3-nested"
> > device to Qemu. At present the Qemu ARM SMMUv3 emulation is per machine
> > and cann
On Fri, Nov 08, 2024 at 12:52:37PM +, Shameer Kolothum via wrote:
> How to use it(Eg:):
>
> On a HiSilicon platform that has multiple physical SMMUv3s, the ACC ZIP VF
> devices and HNS VF devices are behind different SMMUv3s. So for a Guest,
> specify two smmuv3-nested devices each behind a px
>with an error message indicating DMA mapping failed for the
passthrough >devices.
A correction - the message indicates UEFI failed to find a mapping for
the boot partition ("map: no mapping found"), not that DMA mapping
failed. But earlier EDK debug logs still show PCI host bridge resource
conf
.@nvidia.com; peter.mayd...@linaro.org;
> qemu-...@nongnu.org; Wangzhou (B) ;
> zhangfei@linaro.org; qemu-devel@nongnu.org
> Subject: RE: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> >> >with an error message indicating DMA mapping fa
>with an error message indicating DMA mapping failed for the
passthrough >devices.
A correction - the message indicates UEFI failed to find a mapping for
the boot partition ("map: no mapping found"), not that DMA mapping
failed. But earlier EDK debug logs still show PCI host bridge resource
conf
Hi Shameer,
>-Original Message-
>From: Shameerali Kolothum Thodi
>Subject: RE: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable nested
>SMMUv3
>
>
>
>> -Original Message-
>> From: Nicolin Chen
>> Sent: Thursday, January 23, 2
On Thu, Jan 23, 2025 at 08:28:34AM +, Shameerali Kolothum Thodi wrote:
> > -Original Message-
> > From: Nicolin Chen
> > I wonder if we can make some progress in Feb? If so, we can start
> > to wrap up the iommufd uAPI patches for HWPT, which was a part of
> > intel's series but never
-devel@nongnu.org; Linuxarm ; Wangzhou
> (B) ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei@linaro.org
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> Hi Don,
>
> On Fri, Jan 10, 2025 at 11:05:24PM -0500, Donald Dutile wrote
Hi Don,
On Fri, Jan 10, 2025 at 11:05:24PM -0500, Donald Dutile wrote:
> On 1/8/25 11:45 PM, Nicolin Chen wrote:
> > On Mon, Dec 16, 2024 at 10:01:29AM +, Shameerali Kolothum Thodi wrote:
> > > And patches prior to this commit adds that support:
> > > 4ccdbe3: ("cover-letter: Add HW accelerate
Nicolin,
Hi!
On 1/8/25 11:45 PM, Nicolin Chen wrote:
On Mon, Dec 16, 2024 at 10:01:29AM +, Shameerali Kolothum Thodi wrote:
And patches prior to this commit adds that support:
4ccdbe3: ("cover-letter: Add HW accelerated nesting support for arm
SMMUv3")
Nicolin is soon going to send out th
On Mon, Dec 16, 2024 at 10:01:29AM +, Shameerali Kolothum Thodi wrote:
> And patches prior to this commit adds that support:
> 4ccdbe3: ("cover-letter: Add HW accelerated nesting support for arm
> SMMUv3")
>
> Nicolin is soon going to send out those for review. Or I can include
> those in thi
On 12/13/24 8:19 AM, Daniel P. Berrangé wrote:
On Fri, Dec 13, 2024 at 08:46:42AM -0400, Jason Gunthorpe wrote:
On Fri, Dec 13, 2024 at 12:00:43PM +, Daniel P. Berrangé wrote:
On Fri, Nov 08, 2024 at 12:52:37PM +, Shameer Kolothum via wrote:
Hi,
This series adds initial support for
...@redhat.com; Linuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei....@linaro.org
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Fri, 13 Dec 2024 at 12:46, Jason Gunthorpe wrote:
> >
> > On
.com; ddut...@redhat.com;
> Linuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei@linaro.org
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Fri, Dec 13, 2024 at 08:46:42AM -0400, Jason Gunthorpe wro
; Linuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei@linaro.org; Nicolin Chen
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
>
> >with an error message indicating DMA mapping failed for the
> pa
On Fri, 13 Dec 2024 at 12:46, Jason Gunthorpe wrote:
>
> On Fri, Dec 13, 2024 at 12:00:43PM +, Daniel P. Berrangé wrote:
> > On Fri, Nov 08, 2024 at 12:52:37PM +, Shameer Kolothum via wrote:
> > > Hi,
> > >
> > > This series adds initial support for a user-creatable "arm-smmuv3-nested"
> >
On Fri, Dec 13, 2024 at 08:46:42AM -0400, Jason Gunthorpe wrote:
> On Fri, Dec 13, 2024 at 12:00:43PM +, Daniel P. Berrangé wrote:
> > On Fri, Nov 08, 2024 at 12:52:37PM +, Shameer Kolothum via wrote:
> > > Hi,
> > >
> > > This series adds initial support for a user-creatable "arm-smmuv3-n
On Fri, Dec 13, 2024 at 12:00:43PM +, Daniel P. Berrangé wrote:
> On Fri, Nov 08, 2024 at 12:52:37PM +, Shameer Kolothum via wrote:
> > Hi,
> >
> > This series adds initial support for a user-creatable "arm-smmuv3-nested"
> > device to Qemu. At present the Qemu ARM SMMUv3 emulation is per
On Fri, Dec 13, 2024 at 11:58:02AM +, Daniel P. Berrangé wrote:
> Libvirt does not rquire use of pcie-switch. It supports them, but in the
> absence of app requested configs, libvirt will always just populate
> pcie-root-port devices. switches are something that has to be explicitly
> asked fo
On Fri, Nov 08, 2024 at 12:52:37PM +, Shameer Kolothum via wrote:
> Hi,
>
> This series adds initial support for a user-creatable "arm-smmuv3-nested"
> device to Qemu. At present the Qemu ARM SMMUv3 emulation is per machine
> and cannot support multiple SMMUv3s.
>
> In order to support vfio-p
ongnu.org;
> > eric.au...@redhat.com; peter.mayd...@linaro.org; j...@nvidia.com;
> > ddut...@redhat.com; Linuxarm ; Wangzhou (B)
> > ; jiangkunkun ;
> > Jonathan Cameron ;
> > zhangfei....@linaro.org; Nicolin Chen
> > Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add s
>with an error message indicating DMA mapping failed for the
passthrough >devices.
A correction - the message indicates UEFI failed to find a mapping for
the boot partition ("map: no mapping found"), not that DMA mapping
failed. But earlier EDK debug logs still show PCI host bridge resource
Hi Shameer,
Could you share the branch/version of the boot firmware file
"QEMU_EFI.fd" from your example, and where you retrieved it from? I've
been encountering PCI host bridge resource conflicts whenever assigning
more than one passthrough device to a multi-vSMMU VM, booting with the
boot f
> >> Also as a heads up, I've added support for auto-inserting PCIe switch
> >> between the PXB and GPUs in libvirt to attach multiple devices to a
> SMMU
> >> node per libvirt's documentation - "If you intend to plug multiple
> >> devices into a pcie-expander-bus, you must connect a
> >> pci
inuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei@linaro.org; Nicolin Chen
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> >> Also as a heads up, I've added support for auto-inserting PCIe switc
>> Also as a heads up, I've added support for auto-inserting PCIe switch
>> between the PXB and GPUs in libvirt to attach multiple devices to a SMMU
>> node per libvirt's documentation - "If you intend to plug multiple
>> devices into a pcie-expander-bus, you must connect a
>> pcie-switch-upstream
Hi Shameer,
> Attempt to add the HNS VF to a different SMMUv3 will result in,
>
> -device vfio-pci,host=:7d:02.2,bus=pcie.port3,iommufd=iommufd0:
Unable to attach viommu
> -device vfio-pci,host=:7d:02.2,bus=pcie.port3,iommufd=iommufd0:
vfio :7d:02.2:
>Failed to set iommu_device
@redhat.com; Linuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei@linaro.org; Nicolin Chen
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> Hi Shameer,
>
> > Attempt to add the HNS VF to a different SMM
Hi Shameer,
On 11/8/24 13:52, Shameer Kolothum wrote:
> Hi,
>
> This series adds initial support for a user-creatable "arm-smmuv3-nested"
> device to Qemu. At present the Qemu ARM SMMUv3 emulation is per machine
> and cannot support multiple SMMUv3s.
>
> In order to support vfio-pci dev assignment
..@nongnu.org; qemu-devel@nongnu.org;
> > eric.au...@redhat.com; peter.mayd...@linaro.org; j...@nvidia.com;
> > nicol...@nvidia.com; ddut...@redhat.com; Linuxarm
> > ; Wangzhou (B) ;
> > jiangkunkun ; Jonathan Cameron
> > ; zhangfei@linaro.org
> > Subject: Re
inuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei....@linaro.org
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Fri, Nov 08, 2024 at 12:52:37PM +, Shameer Kolothum wrote:
> > This RFC is for in
l...@nvidia.com; ddut...@redhat.com; Linuxarm
> ; Wangzhou (B) ;
> jiangkunkun ; Jonathan Cameron
> ; zhangfei....@linaro.org
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> Hi Shameer,
>
> On Fri, Nov 08, 2024 at 12:52:37PM +,
> ddut...@redhat.com; Linuxarm ; Wangzhou (B)
> ; jiangkunkun ;
> Jonathan Cameron ;
> zhangfei....@linaro.org
> Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable
> nested SMMUv3
>
> On Fri, Nov 08, 2024 at 12:52:37PM +, Shameer Kolothum wrote:
> &g
On Fri, Nov 08, 2024 at 12:52:37PM +, Shameer Kolothum wrote:
> This RFC is for initial discussion/test purposes only and includes patches
> that are only relevant for adding the "arm-smmuv3-nested" support. For the
> complete branch please find,
> https://github.com/hisilicon/qemu/commits/priv
Hi Shameer,
On Fri, Nov 08, 2024 at 12:52:37PM +, Shameer Kolothum via wrote:
> Hi,
>
> This series adds initial support for a user-creatable "arm-smmuv3-nested"
> device to Qemu. At present the Qemu ARM SMMUv3 emulation is per machine
> and cannot support multiple SMMUv3s.
>
I had a quick
On Fri, Nov 08, 2024 at 12:52:37PM +, Shameer Kolothum wrote:
> Few ToDos to note,
> 1. At present default-bus-bypass-iommu=on should be set when
>arm-smmuv3-nested dev is specified. Otherwise you may get an IORT
>related boot error. Requires fixing.
> 2. Hot adding a device is not wor
Hi,
This series adds initial support for a user-creatable "arm-smmuv3-nested"
device to Qemu. At present the Qemu ARM SMMUv3 emulation is per machine
and cannot support multiple SMMUv3s.
In order to support vfio-pci dev assignment with vSMMUv3, the physical
SMMUv3 has to be configured in nested m
94 matches
Mail list logo
