From: Alex Williamson <alex.williamson@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Fam Zheng <fam@euphon.net>, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [RFC PATCH v3 4/5] util/vfio-helpers: Introduce qemu_vfio_pci_init_msix_irqs()
Date: Tue, 18 Aug 2020 11:25:44 -0600 [thread overview]
Message-ID: <20200818112544.1ce38439@x1.home> (raw)
In-Reply-To: <20200818164509.736367-5-philmd@redhat.com>
On Tue, 18 Aug 2020 18:45:08 +0200
Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
> qemu_vfio_pci_init_irq() allows us to initialize any type of IRQ,
> but only one. Introduce qemu_vfio_pci_init_msix_irqs() which is
> specific to MSIX IRQ type, and allow us to use multiple IRQs
> (thus passing multiple eventfd notifiers).
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> include/qemu/vfio-helpers.h | 2 ++
> util/vfio-helpers.c | 53 +++++++++++++++++++++++++++++++++++++
> 2 files changed, 55 insertions(+)
>
> diff --git a/include/qemu/vfio-helpers.h b/include/qemu/vfio-helpers.h
> index 1f057c2b9e4..63108ebc8da 100644
> --- a/include/qemu/vfio-helpers.h
> +++ b/include/qemu/vfio-helpers.h
> @@ -28,5 +28,7 @@ void qemu_vfio_pci_unmap_bar(QEMUVFIOState *s, int index, void *bar,
> uint64_t offset, uint64_t size);
> int qemu_vfio_pci_init_irq(QEMUVFIOState *s, EventNotifier *e,
> int irq_type, Error **errp);
> +int qemu_vfio_pci_init_msix_irqs(QEMUVFIOState *s, EventNotifier *e,
> + unsigned irq_count, Error **errp);
>
> #endif
> diff --git a/util/vfio-helpers.c b/util/vfio-helpers.c
> index 696f2d51712..fb3a79a5bcb 100644
> --- a/util/vfio-helpers.c
> +++ b/util/vfio-helpers.c
> @@ -215,6 +215,59 @@ int qemu_vfio_pci_init_irq(QEMUVFIOState *s, EventNotifier *e,
> return 0;
> }
>
> +/**
> + * Initialize device MSIX IRQs and register event notifiers.
> + * @irq_count: number of MSIX IRQs to initialize
> + * @e: Array of @irq_count notifiers (each corresponding to a MSIX IRQ)
> + */
> +int qemu_vfio_pci_init_msix_irqs(QEMUVFIOState *s, EventNotifier *e,
> + unsigned irq_count, Error **errp)
> +{
> + int r;
> + struct vfio_irq_set *irq_set;
> + size_t irq_set_size;
> + struct vfio_irq_info irq_info = { .argsz = sizeof(irq_info) };
> +
> + irq_info.index = VFIO_PCI_MSIX_IRQ_INDEX;
Nit, this could be initialized in the declaration with argsz.
> + if (ioctl(s->device, VFIO_DEVICE_GET_IRQ_INFO, &irq_info)) {
> + error_setg_errno(errp, errno, "Failed to get device interrupt info");
> + return -errno;
> + }
> + if (irq_info.count <= irq_count) {
Shouldn't this only test strictly less than? The API seems to leave
the problem of determining how many vectors might be available as an
exercise for the caller. Thanks,
Alex
> + error_setg(errp,
> + "Not enough device interrupts available (only %" PRIu32 ")",
> + irq_info.count);
> + return -EINVAL;
> + }
> + if (!(irq_info.flags & VFIO_IRQ_INFO_EVENTFD)) {
> + error_setg(errp, "Device interrupt doesn't support eventfd");
> + return -EINVAL;
> + }
> +
> + irq_set_size = sizeof(*irq_set) + irq_count * sizeof(int32_t);
> + irq_set = g_malloc0(irq_set_size);
> +
> + /* Get to a known IRQ state */
> + *irq_set = (struct vfio_irq_set) {
> + .argsz = irq_set_size,
> + .flags = VFIO_IRQ_SET_DATA_EVENTFD | VFIO_IRQ_SET_ACTION_TRIGGER,
> + .index = irq_info.index,
> + .start = 0,
> + .count = irq_count,
> + };
> +
> + for (unsigned i = 0; i < irq_count; i++) {
> + ((int32_t *)&irq_set->data)[i] = event_notifier_get_fd(&e[i]);
> + }
> + r = ioctl(s->device, VFIO_DEVICE_SET_IRQS, irq_set);
> + g_free(irq_set);
> + if (r) {
> + error_setg_errno(errp, errno, "Failed to setup device interrupts");
> + return -errno;
> + }
> + return 0;
> +}
> +
> static int qemu_vfio_pci_read_config(QEMUVFIOState *s, void *buf,
> int size, int ofs)
> {
next prev parent reply other threads:[~2020-08-18 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 16:45 [RFC PATCH v3 0/5] util/vfio-helpers: Add support for multiple IRQs Philippe Mathieu-Daudé
2020-08-18 16:45 ` [RFC PATCH v3 1/5] block/nvme: Use an array of EventNotifier Philippe Mathieu-Daudé
2020-08-19 8:08 ` Stefan Hajnoczi
2020-08-19 15:55 ` Philippe Mathieu-Daudé
2020-08-18 16:45 ` [RFC PATCH v3 2/5] util/vfio-helpers: Report error on unsupported host architectures Philippe Mathieu-Daudé
2020-08-18 17:12 ` Alex Williamson
2020-08-18 17:26 ` Philippe Mathieu-Daudé
2020-08-18 16:45 ` [RFC PATCH v3 3/5] util/vfio-helpers: Store eventfd using int32_t type Philippe Mathieu-Daudé
2020-08-18 16:45 ` [RFC PATCH v3 4/5] util/vfio-helpers: Introduce qemu_vfio_pci_init_msix_irqs() Philippe Mathieu-Daudé
2020-08-18 17:25 ` Alex Williamson [this message]
2020-08-18 16:45 ` [RFC PATCH v3 5/5] block/nvme: Use qemu_vfio_pci_init_msix_irqs() to initialize our IRQ Philippe Mathieu-Daudé
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=20200818112544.1ce38439@x1.home \
--to=alex.williamson@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).