2016-11-17 04:46:13 +08:00
|
|
|
/*
|
|
|
|
* Mediated device Core Driver
|
|
|
|
*
|
|
|
|
* Copyright (c) 2016, NVIDIA CORPORATION. All rights reserved.
|
|
|
|
* Author: Neo Jia <cjia@nvidia.com>
|
|
|
|
* Kirti Wankhede <kwankhede@nvidia.com>
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License version 2 as
|
|
|
|
* published by the Free Software Foundation.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/device.h>
|
|
|
|
#include <linux/slab.h>
|
|
|
|
#include <linux/uuid.h>
|
|
|
|
#include <linux/sysfs.h>
|
|
|
|
#include <linux/mdev.h>
|
|
|
|
|
|
|
|
#include "mdev_private.h"
|
|
|
|
|
|
|
|
#define DRIVER_VERSION "0.1"
|
|
|
|
#define DRIVER_AUTHOR "NVIDIA Corporation"
|
|
|
|
#define DRIVER_DESC "Mediated device Core Driver"
|
|
|
|
|
|
|
|
static LIST_HEAD(parent_list);
|
|
|
|
static DEFINE_MUTEX(parent_list_lock);
|
|
|
|
static struct class_compat *mdev_bus_compat_class;
|
|
|
|
|
2016-12-30 23:13:33 +08:00
|
|
|
static LIST_HEAD(mdev_list);
|
|
|
|
static DEFINE_MUTEX(mdev_list_lock);
|
|
|
|
|
2016-12-30 23:13:41 +08:00
|
|
|
struct device *mdev_parent_dev(struct mdev_device *mdev)
|
|
|
|
{
|
|
|
|
return mdev->parent->dev;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mdev_parent_dev);
|
|
|
|
|
2016-12-30 23:13:44 +08:00
|
|
|
void *mdev_get_drvdata(struct mdev_device *mdev)
|
|
|
|
{
|
|
|
|
return mdev->driver_data;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mdev_get_drvdata);
|
|
|
|
|
|
|
|
void mdev_set_drvdata(struct mdev_device *mdev, void *data)
|
|
|
|
{
|
|
|
|
mdev->driver_data = data;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mdev_set_drvdata);
|
|
|
|
|
|
|
|
struct device *mdev_dev(struct mdev_device *mdev)
|
|
|
|
{
|
|
|
|
return &mdev->dev;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mdev_dev);
|
|
|
|
|
|
|
|
struct mdev_device *mdev_from_dev(struct device *dev)
|
|
|
|
{
|
|
|
|
return dev_is_mdev(dev) ? to_mdev_device(dev) : NULL;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mdev_from_dev);
|
|
|
|
|
2019-01-11 03:00:27 +08:00
|
|
|
const guid_t *mdev_uuid(struct mdev_device *mdev)
|
2016-12-30 23:13:44 +08:00
|
|
|
{
|
2019-01-11 03:00:27 +08:00
|
|
|
return &mdev->uuid;
|
2016-12-30 23:13:44 +08:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mdev_uuid);
|
|
|
|
|
2016-11-17 04:46:13 +08:00
|
|
|
/* Should be called holding parent_list_lock */
|
2016-12-30 23:13:38 +08:00
|
|
|
static struct mdev_parent *__find_parent_device(struct device *dev)
|
2016-11-17 04:46:13 +08:00
|
|
|
{
|
2016-12-30 23:13:38 +08:00
|
|
|
struct mdev_parent *parent;
|
2016-11-17 04:46:13 +08:00
|
|
|
|
|
|
|
list_for_each_entry(parent, &parent_list, next) {
|
|
|
|
if (parent->dev == dev)
|
|
|
|
return parent;
|
|
|
|
}
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void mdev_release_parent(struct kref *kref)
|
|
|
|
{
|
2016-12-30 23:13:38 +08:00
|
|
|
struct mdev_parent *parent = container_of(kref, struct mdev_parent,
|
|
|
|
ref);
|
2016-11-17 04:46:13 +08:00
|
|
|
struct device *dev = parent->dev;
|
|
|
|
|
|
|
|
kfree(parent);
|
|
|
|
put_device(dev);
|
|
|
|
}
|
|
|
|
|
2019-01-11 03:00:27 +08:00
|
|
|
static inline struct mdev_parent *mdev_get_parent(struct mdev_parent *parent)
|
2016-11-17 04:46:13 +08:00
|
|
|
{
|
|
|
|
if (parent)
|
|
|
|
kref_get(&parent->ref);
|
|
|
|
|
|
|
|
return parent;
|
|
|
|
}
|
|
|
|
|
2016-12-30 23:13:38 +08:00
|
|
|
static inline void mdev_put_parent(struct mdev_parent *parent)
|
2016-11-17 04:46:13 +08:00
|
|
|
{
|
|
|
|
if (parent)
|
|
|
|
kref_put(&parent->ref, mdev_release_parent);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int mdev_device_create_ops(struct kobject *kobj,
|
|
|
|
struct mdev_device *mdev)
|
|
|
|
{
|
2016-12-30 23:13:38 +08:00
|
|
|
struct mdev_parent *parent = mdev->parent;
|
2016-11-17 04:46:13 +08:00
|
|
|
int ret;
|
|
|
|
|
|
|
|
ret = parent->ops->create(kobj, mdev);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
ret = sysfs_create_groups(&mdev->dev.kobj,
|
|
|
|
parent->ops->mdev_attr_groups);
|
|
|
|
if (ret)
|
|
|
|
parent->ops->remove(mdev);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* mdev_device_remove_ops gets called from sysfs's 'remove' and when parent
|
|
|
|
* device is being unregistered from mdev device framework.
|
|
|
|
* - 'force_remove' is set to 'false' when called from sysfs's 'remove' which
|
|
|
|
* indicates that if the mdev device is active, used by VMM or userspace
|
|
|
|
* application, vendor driver could return error then don't remove the device.
|
|
|
|
* - 'force_remove' is set to 'true' when called from mdev_unregister_device()
|
|
|
|
* which indicate that parent device is being removed from mdev device
|
|
|
|
* framework so remove mdev device forcefully.
|
|
|
|
*/
|
|
|
|
static int mdev_device_remove_ops(struct mdev_device *mdev, bool force_remove)
|
|
|
|
{
|
2016-12-30 23:13:38 +08:00
|
|
|
struct mdev_parent *parent = mdev->parent;
|
2016-11-17 04:46:13 +08:00
|
|
|
int ret;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Vendor driver can return error if VMM or userspace application is
|
|
|
|
* using this mdev device.
|
|
|
|
*/
|
|
|
|
ret = parent->ops->remove(mdev);
|
|
|
|
if (ret && !force_remove)
|
|
|
|
return -EBUSY;
|
|
|
|
|
|
|
|
sysfs_remove_groups(&mdev->dev.kobj, parent->ops->mdev_attr_groups);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int mdev_device_remove_cb(struct device *dev, void *data)
|
|
|
|
{
|
|
|
|
if (!dev_is_mdev(dev))
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
return mdev_device_remove(dev, data ? *(bool *)data : true);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* mdev_register_device : Register a device
|
|
|
|
* @dev: device structure representing parent device.
|
|
|
|
* @ops: Parent device operation structure to be registered.
|
|
|
|
*
|
|
|
|
* Add device to list of registered parent devices.
|
|
|
|
* Returns a negative value on error, otherwise 0.
|
|
|
|
*/
|
2016-12-30 23:13:38 +08:00
|
|
|
int mdev_register_device(struct device *dev, const struct mdev_parent_ops *ops)
|
2016-11-17 04:46:13 +08:00
|
|
|
{
|
|
|
|
int ret;
|
2016-12-30 23:13:38 +08:00
|
|
|
struct mdev_parent *parent;
|
2016-11-17 04:46:13 +08:00
|
|
|
|
|
|
|
/* check for mandatory ops */
|
|
|
|
if (!ops || !ops->create || !ops->remove || !ops->supported_type_groups)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
dev = get_device(dev);
|
|
|
|
if (!dev)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
mutex_lock(&parent_list_lock);
|
|
|
|
|
|
|
|
/* Check for duplicate */
|
|
|
|
parent = __find_parent_device(dev);
|
|
|
|
if (parent) {
|
|
|
|
ret = -EEXIST;
|
|
|
|
goto add_dev_err;
|
|
|
|
}
|
|
|
|
|
|
|
|
parent = kzalloc(sizeof(*parent), GFP_KERNEL);
|
|
|
|
if (!parent) {
|
|
|
|
ret = -ENOMEM;
|
|
|
|
goto add_dev_err;
|
|
|
|
}
|
|
|
|
|
|
|
|
kref_init(&parent->ref);
|
|
|
|
|
|
|
|
parent->dev = dev;
|
|
|
|
parent->ops = ops;
|
|
|
|
|
|
|
|
if (!mdev_bus_compat_class) {
|
|
|
|
mdev_bus_compat_class = class_compat_register("mdev_bus");
|
|
|
|
if (!mdev_bus_compat_class) {
|
|
|
|
ret = -ENOMEM;
|
|
|
|
goto add_dev_err;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
ret = parent_create_sysfs_files(parent);
|
|
|
|
if (ret)
|
|
|
|
goto add_dev_err;
|
|
|
|
|
|
|
|
ret = class_compat_create_link(mdev_bus_compat_class, dev, NULL);
|
|
|
|
if (ret)
|
|
|
|
dev_warn(dev, "Failed to create compatibility class link\n");
|
|
|
|
|
|
|
|
list_add(&parent->next, &parent_list);
|
|
|
|
mutex_unlock(&parent_list_lock);
|
|
|
|
|
|
|
|
dev_info(dev, "MDEV: Registered\n");
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
add_dev_err:
|
|
|
|
mutex_unlock(&parent_list_lock);
|
|
|
|
if (parent)
|
|
|
|
mdev_put_parent(parent);
|
|
|
|
else
|
|
|
|
put_device(dev);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mdev_register_device);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* mdev_unregister_device : Unregister a parent device
|
|
|
|
* @dev: device structure representing parent device.
|
|
|
|
*
|
|
|
|
* Remove device from list of registered parent devices. Give a chance to free
|
|
|
|
* existing mediated devices for given device.
|
|
|
|
*/
|
|
|
|
|
|
|
|
void mdev_unregister_device(struct device *dev)
|
|
|
|
{
|
2016-12-30 23:13:38 +08:00
|
|
|
struct mdev_parent *parent;
|
2016-11-17 04:46:13 +08:00
|
|
|
bool force_remove = true;
|
|
|
|
|
|
|
|
mutex_lock(&parent_list_lock);
|
|
|
|
parent = __find_parent_device(dev);
|
|
|
|
|
|
|
|
if (!parent) {
|
|
|
|
mutex_unlock(&parent_list_lock);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
dev_info(dev, "MDEV: Unregistering\n");
|
|
|
|
|
|
|
|
list_del(&parent->next);
|
|
|
|
class_compat_remove_link(mdev_bus_compat_class, dev, NULL);
|
|
|
|
|
|
|
|
device_for_each_child(dev, (void *)&force_remove,
|
|
|
|
mdev_device_remove_cb);
|
|
|
|
|
|
|
|
parent_remove_sysfs_files(parent);
|
|
|
|
|
|
|
|
mutex_unlock(&parent_list_lock);
|
|
|
|
mdev_put_parent(parent);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(mdev_unregister_device);
|
|
|
|
|
|
|
|
static void mdev_device_release(struct device *dev)
|
|
|
|
{
|
|
|
|
struct mdev_device *mdev = to_mdev_device(dev);
|
|
|
|
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
mutex_lock(&mdev_list_lock);
|
|
|
|
list_del(&mdev->next);
|
|
|
|
mutex_unlock(&mdev_list_lock);
|
|
|
|
|
2016-11-17 04:46:13 +08:00
|
|
|
dev_dbg(&mdev->dev, "MDEV: destroying\n");
|
|
|
|
kfree(mdev);
|
|
|
|
}
|
|
|
|
|
2019-01-11 03:00:27 +08:00
|
|
|
int mdev_device_create(struct kobject *kobj,
|
|
|
|
struct device *dev, const guid_t *uuid)
|
2016-11-17 04:46:13 +08:00
|
|
|
{
|
|
|
|
int ret;
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
struct mdev_device *mdev, *tmp;
|
2016-12-30 23:13:38 +08:00
|
|
|
struct mdev_parent *parent;
|
2016-11-17 04:46:13 +08:00
|
|
|
struct mdev_type *type = to_mdev_type(kobj);
|
|
|
|
|
|
|
|
parent = mdev_get_parent(type->parent);
|
|
|
|
if (!parent)
|
|
|
|
return -EINVAL;
|
|
|
|
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
mutex_lock(&mdev_list_lock);
|
2016-11-17 04:46:13 +08:00
|
|
|
|
|
|
|
/* Check for duplicate */
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
list_for_each_entry(tmp, &mdev_list, next) {
|
2019-01-11 03:00:27 +08:00
|
|
|
if (guid_equal(&tmp->uuid, uuid)) {
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
mutex_unlock(&mdev_list_lock);
|
|
|
|
ret = -EEXIST;
|
|
|
|
goto mdev_fail;
|
|
|
|
}
|
2016-11-17 04:46:13 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
mdev = kzalloc(sizeof(*mdev), GFP_KERNEL);
|
|
|
|
if (!mdev) {
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
mutex_unlock(&mdev_list_lock);
|
2016-11-17 04:46:13 +08:00
|
|
|
ret = -ENOMEM;
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
goto mdev_fail;
|
2016-11-17 04:46:13 +08:00
|
|
|
}
|
|
|
|
|
2019-01-11 03:00:27 +08:00
|
|
|
guid_copy(&mdev->uuid, uuid);
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
list_add(&mdev->next, &mdev_list);
|
|
|
|
mutex_unlock(&mdev_list_lock);
|
|
|
|
|
2016-11-17 04:46:13 +08:00
|
|
|
mdev->parent = parent;
|
|
|
|
kref_init(&mdev->ref);
|
|
|
|
|
|
|
|
mdev->dev.parent = dev;
|
|
|
|
mdev->dev.bus = &mdev_bus_type;
|
|
|
|
mdev->dev.release = mdev_device_release;
|
2019-01-11 03:00:27 +08:00
|
|
|
dev_set_name(&mdev->dev, "%pUl", uuid);
|
2016-11-17 04:46:13 +08:00
|
|
|
|
|
|
|
ret = device_register(&mdev->dev);
|
|
|
|
if (ret) {
|
|
|
|
put_device(&mdev->dev);
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
goto mdev_fail;
|
2016-11-17 04:46:13 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
ret = mdev_device_create_ops(kobj, mdev);
|
|
|
|
if (ret)
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
goto create_fail;
|
2016-11-17 04:46:13 +08:00
|
|
|
|
|
|
|
ret = mdev_create_sysfs_files(&mdev->dev, type);
|
|
|
|
if (ret) {
|
|
|
|
mdev_device_remove_ops(mdev, true);
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
goto create_fail;
|
2016-11-17 04:46:13 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
mdev->type_kobj = kobj;
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
mdev->active = true;
|
2016-11-17 04:46:13 +08:00
|
|
|
dev_dbg(&mdev->dev, "MDEV: created\n");
|
|
|
|
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
return 0;
|
2016-11-17 04:46:13 +08:00
|
|
|
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
create_fail:
|
2016-11-17 04:46:13 +08:00
|
|
|
device_unregister(&mdev->dev);
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
mdev_fail:
|
2016-11-17 04:46:13 +08:00
|
|
|
mdev_put_parent(parent);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
int mdev_device_remove(struct device *dev, bool force_remove)
|
|
|
|
{
|
2016-12-30 23:13:33 +08:00
|
|
|
struct mdev_device *mdev, *tmp;
|
2016-12-30 23:13:38 +08:00
|
|
|
struct mdev_parent *parent;
|
2016-11-17 04:46:13 +08:00
|
|
|
struct mdev_type *type;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
mdev = to_mdev_device(dev);
|
2016-12-30 23:13:33 +08:00
|
|
|
|
|
|
|
mutex_lock(&mdev_list_lock);
|
|
|
|
list_for_each_entry(tmp, &mdev_list, next) {
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
if (tmp == mdev)
|
2016-12-30 23:13:33 +08:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
if (tmp != mdev) {
|
|
|
|
mutex_unlock(&mdev_list_lock);
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
2016-12-30 23:13:33 +08:00
|
|
|
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
if (!mdev->active) {
|
|
|
|
mutex_unlock(&mdev_list_lock);
|
|
|
|
return -EAGAIN;
|
|
|
|
}
|
2016-12-30 23:13:33 +08:00
|
|
|
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
mdev->active = false;
|
|
|
|
mutex_unlock(&mdev_list_lock);
|
2016-12-30 23:13:33 +08:00
|
|
|
|
2016-11-17 04:46:13 +08:00
|
|
|
type = to_mdev_type(mdev->type_kobj);
|
|
|
|
parent = mdev->parent;
|
|
|
|
|
|
|
|
ret = mdev_device_remove_ops(mdev, force_remove);
|
|
|
|
if (ret) {
|
vfio/mdev: Check globally for duplicate devices
When we create an mdev device, we check for duplicates against the
parent device and return -EEXIST if found, but the mdev device
namespace is global since we'll link all devices from the bus. We do
catch this later in sysfs_do_create_link_sd() to return -EEXIST, but
with it comes a kernel warning and stack trace for trying to create
duplicate sysfs links, which makes it an undesirable response.
Therefore we should really be looking for duplicates across all mdev
parent devices, or as implemented here, against our mdev device list.
Using mdev_list to prevent duplicates means that we can remove
mdev_parent.lock, but in order not to serialize mdev device creation
and removal globally, we add mdev_device.active which allows UUIDs to
be reserved such that we can drop the mdev_list_lock before the mdev
device is fully in place.
Two behavioral notes; first, mdev_parent.lock had the side-effect of
serializing mdev create and remove ops per parent device. This was
an implementation detail, not an intentional guarantee provided to
the mdev vendor drivers. Vendor drivers can trivially provide this
serialization internally if necessary. Second, review comments note
the new -EAGAIN behavior when the device, and in particular the remove
attribute, becomes visible in sysfs. If a remove is triggered prior
to completion of mdev_device_create() the user will see a -EAGAIN
error. While the errno is different, receiving an error during this
period is not, the previous implementation returned -ENODEV for the
same condition. Furthermore, the consistency to the user is improved
in the case where mdev_device_remove_ops() returns error. Previously
concurrent calls to mdev_device_remove() could see the device
disappear with -ENODEV and return in the case of error. Now a user
would see -EAGAIN while the device is in this transitory state.
Reviewed-by: Kirti Wankhede <kwankhede@nvidia.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Acked-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
2018-05-16 03:53:55 +08:00
|
|
|
mdev->active = true;
|
2016-11-17 04:46:13 +08:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
mdev_remove_sysfs_files(dev, type);
|
|
|
|
device_unregister(dev);
|
|
|
|
mdev_put_parent(parent);
|
2016-12-30 23:13:33 +08:00
|
|
|
|
|
|
|
return 0;
|
2016-11-17 04:46:13 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static int __init mdev_init(void)
|
|
|
|
{
|
2017-02-09 04:13:25 +08:00
|
|
|
return mdev_bus_register();
|
2016-11-17 04:46:13 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static void __exit mdev_exit(void)
|
|
|
|
{
|
|
|
|
if (mdev_bus_compat_class)
|
|
|
|
class_compat_unregister(mdev_bus_compat_class);
|
|
|
|
|
|
|
|
mdev_bus_unregister();
|
|
|
|
}
|
|
|
|
|
|
|
|
module_init(mdev_init)
|
|
|
|
module_exit(mdev_exit)
|
|
|
|
|
|
|
|
MODULE_VERSION(DRIVER_VERSION);
|
|
|
|
MODULE_LICENSE("GPL v2");
|
|
|
|
MODULE_AUTHOR(DRIVER_AUTHOR);
|
|
|
|
MODULE_DESCRIPTION(DRIVER_DESC);
|
2017-02-09 04:13:25 +08:00
|
|
|
MODULE_SOFTDEP("post: vfio_mdev");
|