From: Kirti Wankhede <kwankhede@nvidia.com>
To: "Ricardo B. Marliere" <ricardo@marliere.net>,
Alex Williamson <alex.williamson@redhat.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: RE: [PATCH] vfio: mdev: make mdev_bus_type const
Date: Mon, 12 Feb 2024 17:35:10 +0000 [thread overview]
Message-ID: <MN2PR12MB42064DF281EBAAE82852F2C4DC482@MN2PR12MB4206.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240208-bus_cleanup-vfio-v1-1-ed5da3019949@marliere.net>
> -----Original Message-----
> From: Ricardo B. Marliere <ricardo@marliere.net>
> Sent: Friday, February 9, 2024 1:32 AM
> To: Kirti Wankhede <kwankhede@nvidia.com>; Alex Williamson
> <alex.williamson@redhat.com>
> Cc: kvm@vger.kernel.org; linux-kernel@vger.kernel.org; Greg Kroah-Hartman
> <gregkh@linuxfoundation.org>; Ricardo B. Marliere <ricardo@marliere.net>
> Subject: [PATCH] vfio: mdev: make mdev_bus_type const
>
> Now that the driver core can properly handle constant struct bus_type,
> move the mdev_bus_type variable to be a constant structure as well,
> placing it into read-only memory which can not be modified at runtime.
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Suggested-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Ricardo B. Marliere <ricardo@marliere.net>
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
> ---
> drivers/vfio/mdev/mdev_driver.c | 2 +-
> drivers/vfio/mdev/mdev_private.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/vfio/mdev/mdev_driver.c b/drivers/vfio/mdev/mdev_driver.c
> index 7825d83a55f8..b98322966b3e 100644
> --- a/drivers/vfio/mdev/mdev_driver.c
> +++ b/drivers/vfio/mdev/mdev_driver.c
> @@ -40,7 +40,7 @@ static int mdev_match(struct device *dev, struct
> device_driver *drv)
> return 0;
> }
>
> -struct bus_type mdev_bus_type = {
> +const struct bus_type mdev_bus_type = {
> .name = "mdev",
> .probe = mdev_probe,
> .remove = mdev_remove,
> diff --git a/drivers/vfio/mdev/mdev_private.h
> b/drivers/vfio/mdev/mdev_private.h
> index af457b27f607..63a1316b08b7 100644
> --- a/drivers/vfio/mdev/mdev_private.h
> +++ b/drivers/vfio/mdev/mdev_private.h
> @@ -13,7 +13,7 @@
> int mdev_bus_register(void);
> void mdev_bus_unregister(void);
>
> -extern struct bus_type mdev_bus_type;
> +extern const struct bus_type mdev_bus_type;
> extern const struct attribute_group *mdev_device_groups[];
>
> #define to_mdev_type_attr(_attr) \
>
> ---
> base-commit: 78f70c02bdbccb5e9b0b0c728185d4aeb7044ace
> change-id: 20240208-bus_cleanup-vfio-75a6180b5efe
>
> Best regards,
> --
> Ricardo B. Marliere <ricardo@marliere.net>
next prev parent reply other threads:[~2024-02-12 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 20:02 Ricardo B. Marliere
2024-02-09 10:32 ` Greg Kroah-Hartman
2024-02-12 13:44 ` Jason Gunthorpe
2024-02-12 17:35 ` Kirti Wankhede [this message]
2024-02-22 21:37 ` 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=MN2PR12MB42064DF281EBAAE82852F2C4DC482@MN2PR12MB4206.namprd12.prod.outlook.com \
--to=kwankhede@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ricardo@marliere.net \
/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®