Hi Jan,
On 05/19/2016 04:09 AM, Jan Beulich wrote:
>>>+int __init amd_iommu_get_supported_ivhd_type(void)
>>>+{
>>>+if ( unlikely(acpi_gbl_FADT.boot_flags & ACPI_FADT_NO_MSI) )
>>>+return -EPERM;
>>
>>This check appears out of the blue, and isn't being mentioned in
>>the
>>> On 19.05.16 at 08:30, wrote:
> On 05/17/2016 09:25 AM, Jan Beulich wrote:
> On 13.05.16 at 21:54, wrote:
>>> --- a/xen/drivers/passthrough/amd/iommu_acpi.c
>>> +++ b/xen/drivers/passthrough/amd/iommu_acpi.c
>>> [...]
>>> @@
Hi Jan,
On 05/17/2016 09:25 AM, Jan Beulich wrote:
On 13.05.16 at 21:54, wrote:
--- a/xen/drivers/passthrough/amd/iommu_acpi.c
+++ b/xen/drivers/passthrough/amd/iommu_acpi.c
[...]
@@ -901,7 +911,7 @@ static int __init parse_ivhd_block(const struct
>>> On 13.05.16 at 21:54, wrote:
> --- a/xen/drivers/passthrough/amd/iommu_acpi.c
> +++ b/xen/drivers/passthrough/amd/iommu_acpi.c
> @@ -821,13 +821,23 @@ static u16 __init parse_ivhd_device_special(
> return dev_length;
> }
>
> +static inline int
From: Suravee Suthikulpanit
Along with the IVHD block type 10h, newer AMD platforms also come with
types 11h, which is a superset of the older one. Having multiple IVHD
block types in the same platform allows backward compatibility of newer
systems to work with