[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170106110131.GM17255@8bytes.org>
Date: Fri, 6 Jan 2017 12:01:31 +0100
From: Joerg Roedel <joro@...tes.org>
To: Eric Auger <eric.auger@...hat.com>
Cc: eric.auger.pro@...il.com, christoffer.dall@...aro.org,
marc.zyngier@....com, robin.murphy@....com,
alex.williamson@...hat.com, will.deacon@....com,
tglx@...utronix.de, jason@...edaemon.net,
linux-arm-kernel@...ts.infradead.org, kvm@...r.kernel.org,
drjones@...hat.com, linux-kernel@...r.kernel.org,
pranav.sawargaonkar@...il.com, iommu@...ts.linux-foundation.org,
punit.agrawal@....com, diana.craciun@....com, gpkulkarni@...il.com,
shankerd@...eaurora.org, bharat.bhushan@....com,
geethasowjanya.akula@...il.com
Subject: Re: [PATCH v6 08/18] iommu/vt-d: Implement reserved region get/put
callbacks
On Thu, Jan 05, 2017 at 07:04:36PM +0000, Eric Auger wrote:
> +static void intel_iommu_get_resv_regions(struct device *device,
> + struct list_head *head)
> +{
> + struct iommu_resv_region *reg;
> +
> + reg = iommu_alloc_resv_region(IOAPIC_RANGE_START,
> + IOAPIC_RANGE_END - IOAPIC_RANGE_START + 1,
> + 0, IOMMU_RESV_NOMAP);
> + if (!reg)
> + return;
> + list_add_tail(®->list, head);
> +}
That is different from what AMD does, can you also report the RMRR
regions for the device here (as direct-map regions)?
Joerg
Powered by blists - more mailing lists