From: Kirti Wankhede <kwankhede@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>
Subject: Re: [PATCH v2] vfio/mdev: Use a module softdep for vfio_mdev
Date: Fri, 10 Feb 2017 00:35:46 +0530 [thread overview]
Message-ID: <73aaa70c-e56a-2713-410b-9a492571fa76@nvidia.com> (raw)
In-Reply-To: <20170208221526.19509.30858.stgit@gimli.home>
On 2/9/2017 3:46 AM, Alex Williamson wrote:
> Use an explicit module softdep rather than a request module call such
> that the dependency is exposed to userspace. This allows us to more
> easily support modules loaded at initrd time.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
>
Looks good to me.
Reviewed by: Kirti Wankhede <kwankhede@nvidia.com>
Thanks,
Kirti
> v2: Remove request_module call as well, update description.
>
> drivers/vfio/mdev/mdev_core.c | 14 ++------------
> 1 file changed, 2 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/vfio/mdev/mdev_core.c b/drivers/vfio/mdev/mdev_core.c
> index 36d75c367d22..126991046eb7 100644
> --- a/drivers/vfio/mdev/mdev_core.c
> +++ b/drivers/vfio/mdev/mdev_core.c
> @@ -422,18 +422,7 @@ int mdev_device_remove(struct device *dev, bool force_remove)
>
> static int __init mdev_init(void)
> {
> - int ret;
> -
> - ret = mdev_bus_register();
> -
> - /*
> - * Attempt to load known vfio_mdev. This gives us a working environment
> - * without the user needing to explicitly load vfio_mdev driver.
> - */
> - if (!ret)
> - request_module_nowait("vfio_mdev");
> -
> - return ret;
> + return mdev_bus_register();
> }
>
> static void __exit mdev_exit(void)
> @@ -451,3 +440,4 @@ static void __exit mdev_exit(void)
> MODULE_LICENSE("GPL v2");
> MODULE_AUTHOR(DRIVER_AUTHOR);
> MODULE_DESCRIPTION(DRIVER_DESC);
> +MODULE_SOFTDEP("post: vfio_mdev");
>
prev parent reply other threads:[~2017-02-09 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 22:16 Alex Williamson
2017-02-09 19:05 ` Kirti Wankhede [this message]
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=73aaa70c-e56a-2713-410b-9a492571fa76@nvidia.com \
--to=kwankhede@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®