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 4/5] s390x/pci: Add routine to get the vfio dma available count
Date: Wed, 16 Sep 2020 09:21:39 +0200 [thread overview]
Message-ID: <0b28ae63-faad-953d-85c2-04bcdefeb7bf@redhat.com> (raw)
In-Reply-To: <1600197283-25274-5-git-send-email-mjrosato@linux.ibm.com>
On 9/15/20 9:14 PM, Matthew Rosato wrote:
> Create new files for separating out vfio-specific work for s390
> pci. Add the first such routine, which issues VFIO_IOMMU_GET_INFO
> ioctl to collect the current dma available count.
>
> Signed-off-by: Matthew Rosato <mjrosato@linux.ibm.com>
> ---
> hw/s390x/meson.build | 1 +
> hw/s390x/s390-pci-vfio.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++
> hw/s390x/s390-pci-vfio.h | 17 +++++++++++++++
> 3 files changed, 72 insertions(+)
> create mode 100644 hw/s390x/s390-pci-vfio.c
> create mode 100644 hw/s390x/s390-pci-vfio.h
>
> diff --git a/hw/s390x/meson.build b/hw/s390x/meson.build
> index b63782d..ed2f66b 100644
> --- a/hw/s390x/meson.build
> +++ b/hw/s390x/meson.build
> @@ -10,6 +10,7 @@ s390x_ss.add(files(
> 's390-ccw.c',
> 's390-pci-bus.c',
> 's390-pci-inst.c',
> + 's390-pci-vfio.c',
> 's390-skeys.c',
> 's390-stattrib.c',
> 's390-virtio-hcall.c',
> diff --git a/hw/s390x/s390-pci-vfio.c b/hw/s390x/s390-pci-vfio.c
> new file mode 100644
> index 0000000..75e3ac1
> --- /dev/null
> +++ b/hw/s390x/s390-pci-vfio.c
> @@ -0,0 +1,54 @@
> +/*
> + * s390 vfio-pci interfaces
> + *
> + * Copyright 2020 IBM Corp.
> + * Author(s): Matthew Rosato <mjrosato@linux.ibm.com>
> + *
> + * This work is licensed under the terms of the GNU GPL, version 2 or (at
> + * your option) any later version. See the COPYING file in the top-level
> + * directory.
> + */
> +
> +#include <sys/ioctl.h>
> +
> +#include "qemu/osdep.h"
> +#include "s390-pci-vfio.h"
> +#include "hw/vfio/vfio-common.h"
> +
> +/*
> + * Get the current DMA available count from vfio. Returns true if vfio is
> + * limiting DMA requests, false otherwise. The current available count read
> + * from vfio is returned in avail.
> + */
> +bool s390_pci_update_dma_avail(int fd, unsigned int *avail)
> +{
> + g_autofree struct vfio_iommu_type1_info *info;
> + uint32_t argsz;
> + int ret;
> +
> + assert(avail);
> +
> + argsz = sizeof(struct vfio_iommu_type1_info);
> + info = g_malloc0(argsz);
> + info->argsz = argsz;
> + /*
> + * If the specified argsz is not large enough to contain all
> + * capabilities it will be updated upon return. In this case
> + * use the updated value to get the entire capability chain.
> + */
> + ret = ioctl(fd, VFIO_IOMMU_GET_INFO, info);
> + if (argsz != info->argsz) {
> + argsz = info->argsz;
> + info = g_realloc(info, argsz);
Do we need to bzero [sizeof(struct vfio_iommu_type1_info)..argsz[?
> + info->argsz = argsz;
> + ret = ioctl(fd, VFIO_IOMMU_GET_INFO, info);
> + }
> +
> + if (ret) {
> + return false;
> + }
> +
> + /* If the capability exists, update with the current value */
> + return vfio_get_info_dma_avail(info, avail);
> +}
> +
> diff --git a/hw/s390x/s390-pci-vfio.h b/hw/s390x/s390-pci-vfio.h
> new file mode 100644
> index 0000000..2a5a261
> --- /dev/null
> +++ b/hw/s390x/s390-pci-vfio.h
> @@ -0,0 +1,17 @@
> +/*
> + * s390 vfio-pci interfaces
> + *
> + * Copyright 2020 IBM Corp.
> + * Author(s): Matthew Rosato <mjrosato@linux.ibm.com>
> + *
> + * This work is licensed under the terms of the GNU GPL, version 2 or (at
> + * your option) any later version. See the COPYING file in the top-level
> + * directory.
> + */
> +
> +#ifndef HW_S390_PCI_VFIO_H
> +#define HW_S390_PCI_VFIO_H
> +
> +bool s390_pci_update_dma_avail(int fd, unsigned int *avail);
> +
> +#endif
>
next prev parent reply other threads:[~2020-09-16 7:22 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é
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é [this message]
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=0b28ae63-faad-953d-85c2-04bcdefeb7bf@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).