Re: [PATCH 1/7] VFIO_IOMMU_TYPE1 workaround to build for platform devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Oct 1, 2013 at 9:21 PM, Yoder Stuart-B08248
<B08248@xxxxxxxxxxxxx> wrote:
>> >  static int __init vfio_iommu_type1_init(void)
>> >  {
>> > -   if (!iommu_present(&pci_bus_type))
>> > +#ifdef CONFIG_PCI
>> > +   if (iommu_present(&pci_bus_type)) {
>> > +           iommu_bus_type = &pci_bus_type;
>> > +           /* For PCI targets, IOMMU_CAP_INTR_REMAP is required */
>> > +           require_cap_intr_remap = true;
>> > +   }
>> > +#endif
>> > +   if (!iommu_bus_type && iommu_present(&platform_bus_type))
>> > +           iommu_bus_type = &platform_bus_type;
>> > +
>> > +   if(!iommu_bus_type)
>> >             return -ENODEV;
>> >
>> >     return vfio_register_iommu_driver(&vfio_iommu_driver_ops_type1);
>>
>> Is it possible to have a system with both PCI and platform devices?  How
>> would you support that?  Thanks,
>
> It most certainly is a requirement to support both.  This is how
> all of our (FSL) SoCs will expect to work.
>

Both with an IOMMU present?

> I need to understand better why 'iommu_bus_type' exists at
> all...

It exists because the API expects to know the bus type. Ideally, this
would be solved at the IOMMU API level, and we would be able to be
completely bus agnostic in the TYPE1 driver.

>
> Stuart
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm




[Index of Archives]     [Linux KVM]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux