[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <3764d829-2e88-d100-191e-98bf8dac3bfc@linux.vnet.ibm.com>
Date: Fri, 1 Dec 2017 09:50:11 +0100
From: Pierre Morel <pmorel@...ux.vnet.ibm.com>
To: Jean-Philippe Brucker <jean-philippe.brucker@....com>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>
Cc: "cohuck@...hat.com" <cohuck@...hat.com>,
"borntraeger@...ibm.com" <borntraeger@...ibm.com>,
"zyimin@...ux.vnet.ibm.com" <zyimin@...ux.vnet.ibm.com>,
"pasic@...ux.vnet.ibm.com" <pasic@...ux.vnet.ibm.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] vfio/iommu_type1: report the IOMMU aperture info
On 30/11/2017 16:23, Jean-Philippe Brucker wrote:
> On 30/11/17 14:49, Pierre Morel wrote:
> [...]
>> Shouldn't the 52bit problem be reported by the iommu geometry?
>
> Yes, and most IOMMUs seem to set force_aperture. My comment was only about
> default values to adopt in case a new IOMMU driver doesn't set
> force_aperture to true.
>
> Thanks,
> Jean
>
Yes, clear, thanks.
Pierre
--
Pierre Morel
Linux/KVM/QEMU in Böblingen - Germany
Powered by blists - more mailing lists