From: Alex Williamson <alex.williamson@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Tian\, Kevin" <kevin.tian@intel.com>,
Jason Gunthorpe <jgg@nvidia.com>, "Dey\,
Megha" <megha.dey@intel.com>, "Raj\, Ashok" <ashok.raj@intel.com>,
"Pan\, Jacob jun" <jacob.jun.pan@intel.com>, "Jiang\,
Dave" <dave.jiang@intel.com>, "Liu\, Yi L" <yi.l.liu@intel.com>,
"Lu\, Baolu" <baolu.lu@intel.com>, "Williams\,
Dan J" <dan.j.williams@intel.com>, "Luck\,
Tony" <tony.luck@intel.com>, "Kumar\,
Sanjay K" <sanjay.k.kumar@intel.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>,
Kirti Wankhede <kwankhede@nvidia.com>,
Peter Zijlstra <peterz@infradead.org>,
Marc Zyngier <maz@kernel.org>, Bjorn Helgaas <helgaas@kernel.org>
Subject: Re: Virtualizing MSI-X on IMS via VFIO
Date: Wed, 23 Jun 2021 20:48:28 -0600 [thread overview]
Message-ID: <20210623204828.2bc7e6dc.alex.williamson@redhat.com> (raw)
In-Reply-To: <87mtrgatqo.ffs@nanos.tec.linutronix.de>
On Thu, 24 Jun 2021 04:20:31 +0200
Thomas Gleixner <tglx@linutronix.de> wrote:
> Kevin,
>
> thank you very much for digging into this! You made my day!
>
> On Thu, Jun 24 2021 at 00:00, Kevin Tian wrote:
> >> From: Alex Williamson <alex.williamson@redhat.com>
> >> To work with what we've got, the vfio API describes the limitation of
> >> the host interfaces via the VFIO_IRQ_INFO_NORESIZE flag. QEMU then
> >> makes a choice in an attempt to better reflect what we can infer of the
> >> guest programming of the device to incrementally enable vectors. We
> >
> > It's a surprise to me that Qemu even doesn't look at this flag today after
> > searching its code...
>
> Indeed.
>
> git clone https://github.com/qemu/qemu.git
> cd qemu
> git log -p | grep NORESIZE
> + * The NORESIZE flag indicates that the interrupt lines within the index
> +#define VFIO_IRQ_INFO_NORESIZE (1 << 3)
>
> According to the git history of QEMU this was never used at all and I
> don't care about the magic muck which might be in some RHT repository
> which might make use of that.
>
> Find below the proper fix for this nonsense which just wasted everyones
> time. I'll post it officialy with a proper changelog tomorrow unless
> Kevin beats me to it who actually unearthed this and surely earns the
> credit.
>
> Alex, I seriously have to ask what you were trying to tell us about this
> flag and it's great value and the design related to this.
>
> I'm sure you can submit the corresponding fix to qemu yourself.
>
> And once you are back from lala land, can you please explain how
> VFIO/PCI/MSIX is supposed to work in reality?
It's part of the spec, there's never been a case of !NORESIZE, assuming
NORESIZE is the safe behavior. Sorry, there's no smoking gun here, NAK
> ---
> --- a/drivers/gpu/drm/i915/gvt/kvmgt.c
> +++ b/drivers/gpu/drm/i915/gvt/kvmgt.c
> @@ -1644,8 +1644,6 @@ static long intel_vgpu_ioctl(struct mdev
> if (info.index == VFIO_PCI_INTX_IRQ_INDEX)
> info.flags |= (VFIO_IRQ_INFO_MASKABLE |
> VFIO_IRQ_INFO_AUTOMASKED);
> - else
> - info.flags |= VFIO_IRQ_INFO_NORESIZE;
>
> return copy_to_user((void __user *)arg, &info, minsz) ?
> -EFAULT : 0;
> --- a/drivers/vfio/pci/vfio_pci.c
> +++ b/drivers/vfio/pci/vfio_pci.c
> @@ -1018,8 +1018,6 @@ static long vfio_pci_ioctl(struct vfio_d
> if (info.index == VFIO_PCI_INTX_IRQ_INDEX)
> info.flags |= (VFIO_IRQ_INFO_MASKABLE |
> VFIO_IRQ_INFO_AUTOMASKED);
> - else
> - info.flags |= VFIO_IRQ_INFO_NORESIZE;
>
> return copy_to_user((void __user *)arg, &info, minsz) ?
> -EFAULT : 0;
> --- a/include/uapi/linux/vfio.h
> +++ b/include/uapi/linux/vfio.h
> @@ -693,16 +693,6 @@ struct vfio_region_info_cap_nvlink2_lnks
> * automatically masked by VFIO and the user needs to unmask the line
> * to receive new interrupts. This is primarily intended to distinguish
> * level triggered interrupts.
> - *
> - * The NORESIZE flag indicates that the interrupt lines within the index
> - * are setup as a set and new subindexes cannot be enabled without first
> - * disabling the entire index. This is used for interrupts like PCI MSI
> - * and MSI-X where the driver may only use a subset of the available
> - * indexes, but VFIO needs to enable a specific number of vectors
> - * upfront. In the case of MSI-X, where the user can enable MSI-X and
> - * then add and unmask vectors, it's up to userspace to make the decision
> - * whether to allocate the maximum supported number of vectors or tear
> - * down setup and incrementally increase the vectors as each is enabled.
> */
> struct vfio_irq_info {
> __u32 argsz;
> @@ -710,7 +700,6 @@ struct vfio_irq_info {
> #define VFIO_IRQ_INFO_EVENTFD (1 << 0)
> #define VFIO_IRQ_INFO_MASKABLE (1 << 1)
> #define VFIO_IRQ_INFO_AUTOMASKED (1 << 2)
> -#define VFIO_IRQ_INFO_NORESIZE (1 << 3)
> __u32 index; /* IRQ index */
> __u32 count; /* Number of IRQs within this index */
> };
> --- a/samples/vfio-mdev/mtty.c
> +++ b/samples/vfio-mdev/mtty.c
> @@ -1092,9 +1092,6 @@ static int mtty_get_irq_info(struct mdev
> if (irq_info->index == VFIO_PCI_INTX_IRQ_INDEX)
> irq_info->flags |= (VFIO_IRQ_INFO_MASKABLE |
> VFIO_IRQ_INFO_AUTOMASKED);
> - else
> - irq_info->flags |= VFIO_IRQ_INFO_NORESIZE;
> -
> return 0;
> }
>
>
next prev parent reply other threads:[~2021-06-24 2:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 10:16 Virtualizing MSI-X on IMS via VFIO Tian, Kevin
2021-06-22 15:50 ` Dave Jiang
2021-06-23 6:16 ` Tian, Kevin
2021-06-22 19:12 ` Alex Williamson
2021-06-22 23:59 ` Thomas Gleixner
2021-06-23 6:12 ` Tian, Kevin
2021-06-23 16:31 ` Thomas Gleixner
2021-06-23 16:41 ` Jason Gunthorpe
2021-06-23 23:41 ` Tian, Kevin
2021-06-23 23:37 ` Tian, Kevin
2021-06-24 1:18 ` Thomas Gleixner
2021-06-24 2:41 ` Tian, Kevin
2021-06-24 15:14 ` Thomas Gleixner
2021-06-24 21:44 ` Alex Williamson
2021-06-25 5:21 ` Tian, Kevin
2021-06-25 8:43 ` Thomas Gleixner
2021-06-25 12:42 ` Thomas Gleixner
2021-06-25 21:19 ` Thomas Gleixner
2021-06-25 8:29 ` Thomas Gleixner
2021-06-24 17:03 ` Jacob Pan
2021-06-23 15:19 ` Alex Williamson
2021-06-24 0:00 ` Tian, Kevin
2021-06-24 1:36 ` Thomas Gleixner
2021-06-24 2:20 ` Thomas Gleixner
2021-06-24 2:48 ` Alex Williamson [this message]
2021-06-24 12:06 ` [PATCH] vfio/pci: Document the MSI[X] resize side effects properly Thomas Gleixner
2021-06-24 22:22 ` Alex Williamson
2021-06-24 17:52 ` Virtualizing MSI-X on IMS via VFIO Alex Williamson
2021-06-24 0:43 ` Thomas Gleixner
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=20210623204828.2bc7e6dc.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=helgaas@kernel.org \
--cc=jacob.jun.pan@intel.com \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=megha.dey@intel.com \
--cc=peterz@infradead.org \
--cc=sanjay.k.kumar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=yi.l.liu@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