From: Eric Auger <eric.auger@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>, stable@vger.kernel.org
Cc: sashal@kernel.org
Subject: Re: [PATCH 6.6.y 0/4] vfio: Interrupt eventfd hardening for 6.6.y
Date: Thu, 28 Mar 2024 11:03:40 +0100 [thread overview]
Message-ID: <bff69f62-692b-481e-bbad-020148894f7b@redhat.com> (raw)
In-Reply-To: <20240327225444.909882-1-alex.williamson@redhat.com>
Hi Alex,
On 3/27/24 23:54, Alex Williamson wrote:
> These backports only require reverting to the older eventfd_signal()
> API with two parameters, prior to commit 3652117f8548
> ("eventfd: simplify eventfd_signal()"). Thanks,
for the series
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Eric
>
> Alex
>
> Alex Williamson (4):
> vfio: Introduce interface to flush virqfd inject workqueue
> vfio/pci: Create persistent INTx handler
> vfio/platform: Create persistent IRQ handlers
> vfio/fsl-mc: Block calling interrupt handler without trigger
>
> drivers/vfio/fsl-mc/vfio_fsl_mc_intr.c | 7 +-
> drivers/vfio/pci/vfio_pci_intrs.c | 145 ++++++++++++----------
> drivers/vfio/platform/vfio_platform_irq.c | 100 ++++++++++-----
> drivers/vfio/virqfd.c | 21 ++++
> include/linux/vfio.h | 2 +
> 5 files changed, 173 insertions(+), 102 deletions(-)
>
next prev parent reply other threads:[~2024-03-28 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 22:54 [PATCH 6.6.y 0/4] vfio: Interrupt eventfd hardening for 6.6.y Alex Williamson
2024-03-27 22:54 ` [PATCH 6.6.y 1/4] vfio: Introduce interface to flush virqfd inject workqueue Alex Williamson
2024-03-27 22:54 ` [PATCH 6.6.y 2/4] vfio/pci: Create persistent INTx handler Alex Williamson
2024-03-27 22:54 ` [PATCH 6.6.y 3/4] vfio/platform: Create persistent IRQ handlers Alex Williamson
2024-03-27 22:54 ` [PATCH 6.6.y 4/4] vfio/fsl-mc: Block calling interrupt handler without trigger Alex Williamson
2024-03-28 10:03 ` Eric Auger [this message]
2024-03-29 11:53 ` [PATCH 6.6.y 0/4] vfio: Interrupt eventfd hardening for 6.6.y Greg KH
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=bff69f62-692b-481e-bbad-020148894f7b@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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