mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anthony Krowiak <akrowiak@linux.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: alex@shazbot.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH] VFIO: remove dead notifier code
Date: Wed, 8 Apr 2026 10:34:51 -0400	[thread overview]
Message-ID: <6569b8b8-7654-4dbe-a4a6-f1e565451672@linux.ibm.com> (raw)
In-Reply-To: <20260407175934.1602711-1-pbonzini@redhat.com>



On 4/7/26 1:59 PM, Paolo Bonzini wrote:
> group->notifier is dead code. VFIO initializes it and checks it for emptiness on
> teardown, but nobody ever registers on it or triggers it.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

There are two minor review comments about capitalization at the 
beginning of
sentences in the vfio-ap.rst document in the Documentation/arch/s390
directory. Other than that:

Acked-by: Anthony Krowiak <akrowiak@linux.ibm.com>

> ---
>   Documentation/arch/s390/vfio-ap.rst | 18 ++++++------------
>   drivers/vfio/group.c                |  3 ---
>   drivers/vfio/vfio.h                 |  1 -
>   drivers/vfio/vfio_iommu_type1.c     |  1 -
>   4 files changed, 6 insertions(+), 17 deletions(-)
>
> diff --git a/Documentation/arch/s390/vfio-ap.rst b/Documentation/arch/s390/vfio-ap.rst
> index eba1991fbdba..2de0560bd70c 100644
> --- a/Documentation/arch/s390/vfio-ap.rst
> +++ b/Documentation/arch/s390/vfio-ap.rst
> @@ -431,17 +431,14 @@ matrix device.
>   * callback interfaces
>   
>     open_device:
> -    The vfio_ap driver uses this callback to register a
> -    VFIO_GROUP_NOTIFY_SET_KVM notifier callback function for the matrix mdev
> -    devices. The open_device callback is invoked by userspace to connect the
> -    VFIO iommu group for the matrix mdev device to the MDEV bus. Access to the
> -    KVM structure used to configure the KVM guest is provided via this callback.
> -    The KVM structure, is used to configure the guest's access to the AP matrix
> -    defined via the vfio_ap mediated device's sysfs attribute files.
> +    the open_device callback is invoked by userspace to connect the

Capitalization:
s/the open_device callback/The open device callback/

> +    VFIO iommu group for the matrix mdev device to the MDEV bus.  The
> +    callback retrieves the KVM structure used to configure the KVM guest
> +    and configures the guest's access to the AP matrix defined via the
> +    vfio_ap mediated device's sysfs attribute files.
>   
>     close_device:
> -    unregisters the VFIO_GROUP_NOTIFY_SET_KVM notifier callback function for the
> -    matrix mdev device and deconfigures the guest's AP matrix.
> +    this callback deconfigures the guest's AP matrix.

Capitalization:
s/this callback/This callback/

>   
>     ioctl:
>       this callback handles the VFIO_DEVICE_GET_INFO and VFIO_DEVICE_RESET ioctls
> @@ -449,9 +444,8 @@ matrix device.
>   
>   Configure the guest's AP resources
>   ----------------------------------
> -Configuring the AP resources for a KVM guest will be performed when the
> -VFIO_GROUP_NOTIFY_SET_KVM notifier callback is invoked. The notifier
> -function is called when userspace connects to KVM. The guest's AP resources are
> +Configuring the AP resources for a KVM guest will be performed at the
> +time of ``open_device`` and ``close_device``. The guest's AP resources are
>   configured via its APCB by:
>   
>   * Setting the bits in the APM corresponding to the APIDs assigned to the
> diff --git a/drivers/vfio/group.c b/drivers/vfio/group.c
> index 4f15016d2a5f..731dd0dead0d 100644
> --- a/drivers/vfio/group.c
> +++ b/drivers/vfio/group.c
> @@ -456,7 +456,6 @@ static int vfio_group_fops_release(struct inode *inode, struct file *filep)
>   	 * Device FDs hold a group file reference, therefore the group release
>   	 * is only called when there are no open devices.
>   	 */
> -	WARN_ON(group->notifier.head);
>   	if (group->container)
>   		vfio_group_detach_container(group);
>   	if (group->iommufd) {
> @@ -541,7 +540,6 @@ static struct vfio_group *vfio_group_alloc(struct iommu_group *iommu_group,
>   	/* put in vfio_group_release() */
>   	iommu_group_ref_get(iommu_group);
>   	group->type = type;
> -	BLOCKING_INIT_NOTIFIER_HEAD(&group->notifier);
>   
>   	return group;
>   }
> @@ -720,7 +718,6 @@ void vfio_device_remove_group(struct vfio_device *device)
>   	 * properly hold the group reference.
>   	 */
>   	WARN_ON(!list_empty(&group->device_list));
> -	WARN_ON(group->notifier.head);
>   
>   	/*
>   	 * Revoke all users of group->iommu_group. At this point we know there
> diff --git a/drivers/vfio/vfio.h b/drivers/vfio/vfio.h
> index 50128da18bca..0854f3fa1a22 100644
> --- a/drivers/vfio/vfio.h
> +++ b/drivers/vfio/vfio.h
> @@ -90,7 +90,6 @@ struct vfio_group {
>   	struct mutex			group_lock;
>   	struct kvm			*kvm;
>   	struct file			*opened_file;
> -	struct blocking_notifier_head	notifier;
>   	struct iommufd_ctx		*iommufd;
>   	spinlock_t			kvm_ref_lock;
>   	unsigned int			cdev_device_open_cnt;
> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index 03cefdf99a4a..c8151ba54de3 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -36,7 +36,6 @@
>   #include <linux/uaccess.h>
>   #include <linux/vfio.h>
>   #include <linux/workqueue.h>
> -#include <linux/notifier.h>
>   #include <linux/mm_inline.h>
>   #include <linux/overflow.h>
>   #include "vfio.h"


  reply	other threads:[~2026-04-08 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 17:59 Paolo Bonzini
2026-04-08 14:34 ` Anthony Krowiak [this message]
2026-04-08 14:36   ` Paolo Bonzini
2026-04-08 22:00     ` Paolo Bonzini
2026-04-09 11:55       ` Anthony Krowiak
2026-04-10 18:10 ` Jason Gunthorpe
2026-04-10 19:32   ` Alex Williamson
2026-04-13 21:58 ` Alex Williamson

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=6569b8b8-7654-4dbe-a4a6-f1e565451672@linux.ibm.com \
    --to=akrowiak@linux.ibm.com \
    --cc=alex@shazbot.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pbonzini@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

all inboxes | Powered by JetHome®