From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jean-Philippe Brucker Subject: Re: [PATCH] vfio/iommu_type1: report the IOMMU aperture info Date: Thu, 30 Nov 2017 15:23:00 +0000 Message-ID: <358f3253-6113-2d19-def7-d5d71dc78aaa@arm.com> References: <1512041678-4563-1-git-send-email-pmorel@linux.vnet.ibm.com> <1ad1aff9-1651-d1a9-cd1b-07bfd7dd0817@arm.com> <7cf3e03e-e9b4-0e27-098b-3bc391abcf96@linux.vnet.ibm.com> <76879d8a-3c5f-2fb0-c8f9-100368eafa6e@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: "cohuck@redhat.com" , "borntraeger@de.ibm.com" , "zyimin@linux.vnet.ibm.com" , "pasic@linux.vnet.ibm.com" , "kvm@vger.kernel.org" , "linux-kernel@vger.kernel.org" To: Pierre Morel , "alex.williamson@redhat.com" Return-path: In-Reply-To: <76879d8a-3c5f-2fb0-c8f9-100368eafa6e@linux.vnet.ibm.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org 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