[lkml]   [2016]   [May]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v9 7/7] vfio/type1: return MSI geometry through VFIO_IOMMU_GET_INFO capability chains
On Wed, 4 May 2016 14:06:19 +0200
Eric Auger <> wrote:

> Hi Alex,
> On 05/04/2016 01:54 PM, Eric Auger wrote:
> > This patch allows the user-space to retrieve the MSI geometry. The
> > implementation is based on capability chains, now also added to
> If you prefer we could consider this patch outside of the main series
> since it brings extra functionalities (MSI geometry reporting). In a
> first QEMU integration we would live without knowing the MSI geometry I
> think, all the more so I currently report an arbitrary number of
> requested IOVA pages. The computation of the exact number of doorbells
> to map brings extra complexity and I did not address this issue yet.
> It sketches a possible user API to report the MSI geometry based on the
> capability chains, as you suggested some time ago. I am currently busy
> drafting a QEMU integration.

How would the user know that reserved MSI mappings are requires or
available without this? Wouldn't the only option be for userspace to
try to map something with the reserved MSI flag set and see if the
kernel accepts it? That's not a very desirable programming model. The
arbitrary size is pretty ugly, but it at least makes for a consistent
user interface. Is it a functional issue if we overestimate the size
or is it just a matter of wasting IOVA space? Is there significant
harm in making it obscenely large, like 1MB? The reference counting and
re-use of IOVA pages seems like we may often only be using a single
IOVA page for multiple doorbells. I guess I'm leaning towards defining
the API even if the value is somewhat arbitrary because we'd rather have
control of this rather than having the user guess and try to rope them
back in later to use a kernel recommended value. Thanks,


 \ /
  Last update: 2016-05-10 01:21    [W:0.044 / U:0.152 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site