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 12:57:56 +0000 [thread overview]
Message-ID: <1ad1aff9-1651-d1a9-cd1b-07bfd7dd0817@arm.com> (raw)
In-Reply-To: <1512041678-4563-1-git-send-email-pmorel@linux.vnet.ibm.com>
Hello,
On 30/11/17 11:34, Pierre Morel wrote:
[...]
> +/**
> + * vfio_get_aperture - report minimal aperture of a vfio_iommu
> + * @iommu: the current vfio_iommu
> + * @start: a pointer to the aperture start
> + * @end : a pointer to the aperture end
> + *
> + * This function iterate on the domains using the given vfio_iommu
> + * and restrict the aperture to the minimal aperture common
> + * to all domains sharing this vfio_iommu.
> + */
> +static void vfio_get_aperture(struct vfio_iommu *iommu, uint64_t *start,
> + uint64_t *end)
> +{
> + struct iommu_domain_geometry geometry;
> + struct vfio_domain *domain;
> +
> + *start = 0;
> + *end = U64_MAX;
I wonder if the default values should also reflect what the VFIO
implementation actually supports. Looking at vfio_dma_do_map, a 32-bit
host will reject any iova greater than 32 bits. In addition,
vfio_dma_do_unmap doesn't support unmapping the last page of a 64-bit
address space (existing IOMMUs would probably reject map requests with
IOVA > 52 bits anyway, but if they don't report a domain aperture, VFIO
can't guess it).
I think it's convenient to use VFIO_IOMMU_UNMAP_DMA on the full address
space when an unmap-all is needed, maybe we could provide default aperture
values that help doing this? (~0U for 32-bit and (~0ULL - PAGE_SIZE) for
64-bit)
Thanks,
Jean
next prev parent reply other threads:[~2017-11-30 12:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 11:34 [PATCH] vfio/iommu_type1: report the IOMMU aperture info Pierre Morel
2017-11-30 12:57 ` Jean-Philippe Brucker [this message]
2017-11-30 14:16 ` Pierre Morel
2017-11-30 14:49 ` Pierre Morel
2017-11-30 15:23 ` Jean-Philippe Brucker
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=1ad1aff9-1651-d1a9-cd1b-07bfd7dd0817@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