Hi Alex,
On Thu, Dec 12, 2019 at 12:27:11PM -0700, Alex Williamson wrote:
> Sure, if you remember the ordering between these then that might be the
> better option. I checked that they both entered the kernel for
> v5.3-rc1 but didn't dig deeper than that.
>
> Joerg, if you'd like a respin for
On Wed Dec 11 19, Alex Williamson wrote:
Commit d850c2ee5fe2 ("iommu/vt-d: Expose ISA direct mapping region via
iommu_get_resv_regions") created a direct-mapped reserved memory region
in order to replace the static identity mapping of the ISA address
space, where the latter was then removed in
On Thu, 12 Dec 2019 09:49:37 +0100
Auger Eric wrote:
> Hi Alex,
>
> On 12/11/19 9:28 PM, Alex Williamson wrote:
> > Commit d850c2ee5fe2 ("iommu/vt-d: Expose ISA direct mapping region via
> > iommu_get_resv_regions") created a direct-mapped reserved memory region
> > in order to replace the
Hi Alex,
On 12/11/19 9:28 PM, Alex Williamson wrote:
> Commit d850c2ee5fe2 ("iommu/vt-d: Expose ISA direct mapping region via
> iommu_get_resv_regions") created a direct-mapped reserved memory region
> in order to replace the static identity mapping of the ISA address
> space, where the latter
Hi,
On 12/12/19 4:28 AM, Alex Williamson wrote:
Commit d850c2ee5fe2 ("iommu/vt-d: Expose ISA direct mapping region via
iommu_get_resv_regions") created a direct-mapped reserved memory region
in order to replace the static identity mapping of the ISA address
space, where the latter was then
Commit d850c2ee5fe2 ("iommu/vt-d: Expose ISA direct mapping region via
iommu_get_resv_regions") created a direct-mapped reserved memory region
in order to replace the static identity mapping of the ISA address
space, where the latter was then removed in commit df4f3c603aeb
("iommu/vt-d: Remove