From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
To: Pierre Morel <pmorel@linux.vnet.ibm.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>
Cc: "cohuck@redhat.com" <cohuck@redhat.com>,
"borntraeger@de.ibm.com" <borntraeger@de.ibm.com>,
"zyimin@linux.vnet.ibm.com" <zyimin@linux.vnet.ibm.com>,
"pasic@linux.vnet.ibm.com" <pasic@linux.vnet.ibm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vfio/iommu_type1: report the IOMMU aperture info
Date: Thu, 30 Nov 2017 15:23:00 +0000 [thread overview]
Message-ID: <358f3253-6113-2d19-def7-d5d71dc78aaa@arm.com> (raw)
In-Reply-To: <76879d8a-3c5f-2fb0-c8f9-100368eafa6e@linux.vnet.ibm.com>
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
next prev parent reply other threads:[~2017-11-30 15:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 11:34 Pierre Morel
2017-11-30 12:57 ` Jean-Philippe Brucker
2017-11-30 14:16 ` Pierre Morel
2017-11-30 14:49 ` Pierre Morel
2017-11-30 15:23 ` Jean-Philippe Brucker [this message]
2017-12-01 8:50 ` Pierre Morel
2017-11-30 19:02 ` Alex Williamson
2017-11-30 13:22 ` Auger Eric
2017-11-30 14:17 ` Pierre Morel
2017-11-30 14:08 ` Alex Williamson
2017-11-30 15:11 ` Pierre Morel
2017-11-30 18:30 ` Alex Williamson
2017-12-01 9:38 ` Pierre Morel
2017-12-01 16:22 ` Alex Williamson
2017-12-04 12:36 ` Pierre Morel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=358f3253-6113-2d19-def7-d5d71dc78aaa@arm.com \
--to=jean-philippe.brucker@arm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=zyimin@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®