From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Matthew Rosato <mjrosato@linux.ibm.com>,
alex.williamson@redhat.com, cohuck@redhat.com
Cc: thuth@redhat.com, kvm@vger.kernel.org, pmorel@linux.ibm.com,
schnelle@linux.ibm.com, david@redhat.com, qemu-devel@nongnu.org,
pasic@linux.ibm.com, borntraeger@de.ibm.com,
qemu-s390x@nongnu.org, mst@redhat.com, pbonzini@redhat.com,
rth@twiddle.net
Subject: Re: [PATCH v3 2/5] vfio: Create shared routine for scanning info capabilities
Date: Wed, 16 Sep 2020 09:15:58 +0200 [thread overview]
Message-ID: <3ee0b4c6-865e-82b3-b003-64a4ddaab4b5@redhat.com> (raw)
In-Reply-To: <1600197283-25274-3-git-send-email-mjrosato@linux.ibm.com>
On 9/15/20 9:14 PM, Matthew Rosato wrote:
> Rather than duplicating the same loop in multiple locations,
> create a static function to do the work.
>
> Signed-off-by: Matthew Rosato <mjrosato@linux.ibm.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> hw/vfio/common.c | 21 +++++++++++++--------
> 1 file changed, 13 insertions(+), 8 deletions(-)
>
> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> index 3335714..eba7b55 100644
> --- a/hw/vfio/common.c
> +++ b/hw/vfio/common.c
> @@ -825,17 +825,12 @@ static void vfio_listener_release(VFIOContainer *container)
> }
> }
>
> -struct vfio_info_cap_header *
> -vfio_get_region_info_cap(struct vfio_region_info *info, uint16_t id)
> +static struct vfio_info_cap_header *
> +vfio_get_cap(void *ptr, uint32_t cap_offset, uint16_t id)
> {
> struct vfio_info_cap_header *hdr;
> - void *ptr = info;
> -
> - if (!(info->flags & VFIO_REGION_INFO_FLAG_CAPS)) {
> - return NULL;
> - }
>
> - for (hdr = ptr + info->cap_offset; hdr != ptr; hdr = ptr + hdr->next) {
> + for (hdr = ptr + cap_offset; hdr != ptr; hdr = ptr + hdr->next) {
> if (hdr->id == id) {
> return hdr;
> }
> @@ -844,6 +839,16 @@ vfio_get_region_info_cap(struct vfio_region_info *info, uint16_t id)
> return NULL;
> }
>
> +struct vfio_info_cap_header *
> +vfio_get_region_info_cap(struct vfio_region_info *info, uint16_t id)
> +{
> + if (!(info->flags & VFIO_REGION_INFO_FLAG_CAPS)) {
> + return NULL;
> + }
> +
> + return vfio_get_cap((void *)info, info->cap_offset, id);
> +}
> +
> static int vfio_setup_region_sparse_mmaps(VFIORegion *region,
> struct vfio_region_info *info)
> {
>
next prev parent reply other threads:[~2020-09-16 7:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 19:14 [PATCH v3 0/5] s390x/pci: Accomodate vfio DMA limiting Matthew Rosato
2020-09-15 19:14 ` [PATCH v3 1/5] linux-headers: update against 5.9-rc5 Matthew Rosato
2020-09-15 19:14 ` [PATCH v3 2/5] vfio: Create shared routine for scanning info capabilities Matthew Rosato
2020-09-16 7:15 ` Philippe Mathieu-Daudé [this message]
2020-09-16 9:58 ` Cornelia Huck
2020-09-15 19:14 ` [PATCH v3 3/5] vfio: Find DMA available capability Matthew Rosato
2020-09-16 10:01 ` Cornelia Huck
2020-09-15 19:14 ` [PATCH v3 4/5] s390x/pci: Add routine to get the vfio dma available count Matthew Rosato
2020-09-16 7:21 ` Philippe Mathieu-Daudé
2020-09-16 10:27 ` Cornelia Huck
2020-09-16 12:55 ` Matthew Rosato
2020-09-17 9:59 ` Cornelia Huck
2020-09-15 19:14 ` [PATCH v3 5/5] s390x/pci: Honor DMA limits set by vfio Matthew Rosato
2020-09-16 11:05 ` Cornelia Huck
2020-09-16 12:58 ` Matthew Rosato
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=3ee0b4c6-865e-82b3-b003-64a4ddaab4b5@redhat.com \
--to=philmd@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=schnelle@linux.ibm.com \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).