imported a new argument to add_special_device().
Best Regards
Friendy
> -Original Message-
> From: Joerg Roedel [mailto:j...@8bytes.org]
> Sent: Friday, September 05, 2014 9:53 PM
> To: Su, Friendy
> Cc: iommu@lists.linux-foundation.org; linux-ker...@vger.kernel.org
> S
From: Su Friendy
Subject: iommu/amd: make early mapped ioapic/hpet override IVHD
The early mapped ioapic/hpet specified by kernel boot parameter
ivrs_ioapic[ID]/ivrs_hpet[ID] always override the ioapic/hpet with
same ID reported by ACPI IVHD table.
Current driver still uses devid in IVHD to
Hi, Joerg,
> -Original Message-
> From: j...@8bytes.org [mailto:j...@8bytes.org]
> Sent: Wednesday, September 03, 2014 11:06 PM
> To: Su, Friendy
> Cc: iommu@lists.linux-foundation.org; linux-ker...@vger.kernel.org
> Subject: Re: [PATCH v1 1/1] iommu/amd: set iomm
From: Su Friendy
The early mapped ioapic/hpet specified by kernel boot parameter
ivrs_ioapic[ID]/ivrs_hpet[ID] always override the ioapic/hpet with
same ID reported by ACPI IVRS table. Therefore, the early mapped
should be always controlled by iommu.
Current driver did not set iommu for the
From: Su Friendy
set_device_exclusion_range(u16 devid, struct ivmd_header *m) enables
exclusion range for ONE device. IOMMU does not translate the access
to the exclusion range from the device.
The device is specified by input argument 'devid'. But 'devid' is not
pass
