From: Peter Xu <peterx@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
intel-gvt-dev@lists.freedesktop.org, aik@ozlabs.ru,
kwankhede@nvidia.com, zhenyuw@linux.intel.com,
zhi.a.wang@intel.com
Subject: Re: [PATCH] vfio: Simplify capability helper
Date: Wed, 13 Dec 2017 14:49:36 +0800 [thread overview]
Message-ID: <20171213064936.GC7780@xz-mi> (raw)
In-Reply-To: <20171212195850.13691.40496.stgit@gimli.home>
On Tue, Dec 12, 2017 at 12:59:39PM -0700, Alex Williamson wrote:
> The vfio_info_add_capability() helper requires the caller to pass a
> capability ID, which it then uses to fill in header fields, assuming
> hard coded versions. This makes for an awkward and rigid interface.
> The only thing we want this helper to do is allocate sufficient
> space in the caps buffer and chain this capability into the list.
> Reduce it to that simple task.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Though during review I had a question related to the function
msix_sparse_mmap_cap(): Is it possible that one PCI device BAR is very
small (e.g., 4K) that only contains the MSI-X table (and another small
PBA area)? If so, should we just mark that region unmappable instead
of setting vfio_region_info_cap_sparse_mmap.nr_areas to 1 in
msix_sparse_mmap_cap()?
/* If MSI-X table is aligned to the start or end, only one area */
if (((vdev->msix_offset & PAGE_MASK) == 0) ||
(PAGE_ALIGN(vdev->msix_offset + vdev->msix_size) >= end))
nr_areas = 1;
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2017-12-13 6:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 19:59 [PATCH] vfio: Simplify capability helper Alex Williamson
2017-12-13 1:13 ` Alexey Kardashevskiy
2017-12-13 7:01 ` Zhenyu Wang
2017-12-13 9:04 ` Kirti Wankhede
2017-12-13 6:49 ` Peter Xu [this message]
2017-12-13 15:04 ` Auger Eric
2017-12-13 15:32 ` Auger Eric
2017-12-15 6:20 ` Peter Xu
2017-12-13 15:35 ` Alex Williamson
2017-12-15 6:18 ` Peter Xu
2017-12-13 9:23 ` Auger Eric
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=20171213064936.GC7780@xz-mi \
--to=peterx@redhat.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.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