On 10/30/2017 06:15 PM, Alex Williamson wrote:
> On Mon, 30 Oct 2017 16:39:31 -0400
> Vishwanath Pai via iommu wrote:
>
>> This patch adds a new sysfile for intel-iommu driver which prints out
>> all allocated iommu domains:
>>
>> $> cat /sys/class/iommu/dmar0/intel-iommu/domains
>> did | pci_d
On Mon, 30 Oct 2017 16:39:31 -0400
Vishwanath Pai via iommu wrote:
> This patch adds a new sysfile for intel-iommu driver which prints out
> all allocated iommu domains:
>
> $> cat /sys/class/iommu/dmar0/intel-iommu/domains
> did | pci_device_name
> 1 | :00:14.0
> 2 | :00:1d.0
>
This patch adds a new sysfile for intel-iommu driver which prints out
all allocated iommu domains:
$> cat /sys/class/iommu/dmar0/intel-iommu/domains
did | pci_device_name
1 | :00:14.0
2 | :00:1d.0
3 | :00:1f.0
4 | :02:00.0
5 | :02:00.1
6 | :02:00.2
7 | :02
It is annoyingly non-obvious when DMA transactions silently go missing
due to undetected SMMU faults. Help skip the first few debugging steps
in those situations by making it clear when we have neither wired IRQs
nor MSIs with which to raise error conditions.
Signed-off-by: Robin Murphy
---
v2:
There exist two Mediatek iommu drivers for the two different
generations of the device. But both drivers have the same name
"mtk-iommu". This breaks the registration of the second driver:
Error: Driver 'mtk-iommu' is already registered, aborting...
Fix this by changing the name for first generati
On 25/10/17 19:05, Raj, Ashok wrote:
> Hi Jean
>
> On Mon, Oct 23, 2017 at 01:17:07PM +0100, Jean-Philippe Brucker wrote:
>> On 23/10/17 12:04, Liu, Yi L wrote:
+ idr_preload(GFP_KERNEL);
+ spin_lock(&iommu_process_lock);
+ pasid = idr_alloc_cyclic(&iommu_process_idr, process, do