From: Eric Farman <farman@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>,
Halil Pasic <pasic@linux.ibm.com>,
Farhan Ali <alifm@linux.ibm.com>,
Pierre Morel <pmorel@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 4/6] vfio-ccw: add capabilities chain
Date: Fri, 15 Feb 2019 10:46:08 -0500 [thread overview]
Message-ID: <2da327e8-d6cd-2350-31e1-d99edb0f2980@linux.ibm.com> (raw)
In-Reply-To: <20190130132212.7376-5-cohuck@redhat.com>
On 01/30/2019 08:22 AM, Cornelia Huck wrote:
> Allow to extend the regions used by vfio-ccw. The first user will be
> handling of halt and clear subchannel.
>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
> drivers/s390/cio/vfio_ccw_ops.c | 181 ++++++++++++++++++++++++----
> drivers/s390/cio/vfio_ccw_private.h | 38 ++++++
> include/uapi/linux/vfio.h | 2 +
> 3 files changed, 195 insertions(+), 26 deletions(-)
>
> diff --git a/drivers/s390/cio/vfio_ccw_ops.c b/drivers/s390/cio/vfio_ccw_ops.c
> index 025c8a832bc8..48b2d7930ea8 100644
> --- a/drivers/s390/cio/vfio_ccw_ops.c
> +++ b/drivers/s390/cio/vfio_ccw_ops.c
> @@ -3,9 +3,11 @@
> * Physical device callbacks for vfio_ccw
> *
> * Copyright IBM Corp. 2017
> + * Copyright Red Hat, Inc. 2019
> *
> * Author(s): Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
> * Xiao Feng Ren <renxiaof@linux.vnet.ibm.com>
> + * Cornelia Huck <cohuck@redhat.com>
> */
>
> #include <linux/vfio.h>
> @@ -157,27 +159,33 @@ static void vfio_ccw_mdev_release(struct mdev_device *mdev)
> {
> struct vfio_ccw_private *private =
> dev_get_drvdata(mdev_parent_dev(mdev));
> + int i;
>
> vfio_unregister_notifier(mdev_dev(mdev), VFIO_IOMMU_NOTIFY,
> &private->nb);
> +
> + for (i = 0; i < private->num_regions; i++)
> + private->region[i].ops->release(private, &private->region[i]);
> +
> + private->num_regions = 0;
> + kfree(private->region);
> + private->region = NULL;
> }
>
> -static ssize_t vfio_ccw_mdev_read(struct mdev_device *mdev,
> - char __user *buf,
> - size_t count,
> - loff_t *ppos)
> +static ssize_t vfio_ccw_mdev_read_io_region(struct vfio_ccw_private *private,
> + char __user *buf, size_t count,
> + loff_t *ppos)
> {
> - struct vfio_ccw_private *private;
> + loff_t pos = *ppos & VFIO_CCW_OFFSET_MASK;
> struct ccw_io_region *region;
> int ret;
>
> - if (*ppos + count > sizeof(*region))
> + if (pos + count > sizeof(*region))
> return -EINVAL;
>
> - private = dev_get_drvdata(mdev_parent_dev(mdev));
> mutex_lock(&private->io_mutex);
> region = private->io_region;
> - if (copy_to_user(buf, (void *)region + *ppos, count))
> + if (copy_to_user(buf, (void *)region + pos, count))
> ret = -EFAULT;
> else
> ret = count;
> @@ -185,24 +193,47 @@ static ssize_t vfio_ccw_mdev_read(struct mdev_device *mdev,
> return ret;
> }
>
> -static ssize_t vfio_ccw_mdev_write(struct mdev_device *mdev,
> - const char __user *buf,
> - size_t count,
> - loff_t *ppos)
> +static ssize_t vfio_ccw_mdev_read(struct mdev_device *mdev,
> + char __user *buf,
> + size_t count,
> + loff_t *ppos)
> {
> + unsigned int index = VFIO_CCW_OFFSET_TO_INDEX(*ppos);
> struct vfio_ccw_private *private;
> +
> + private = dev_get_drvdata(mdev_parent_dev(mdev));
> +
> + if (index >= VFIO_CCW_NUM_REGIONS + private->num_regions)
> + return -EINVAL;
> +
> + switch (index) {
> + case VFIO_CCW_CONFIG_REGION_INDEX:
> + return vfio_ccw_mdev_read_io_region(private, buf, count, ppos);
> + default:
> + index -= VFIO_CCW_NUM_REGIONS;
> + return private->region[index].ops->read(private, buf, count,
> + ppos);
> + }
> +
> + return -EINVAL;
> +}
> +
> +static ssize_t vfio_ccw_mdev_write_io_region(struct vfio_ccw_private *private,
> + const char __user *buf,
> + size_t count, loff_t *ppos)
> +{
> + loff_t pos = *ppos & VFIO_CCW_OFFSET_MASK;
> struct ccw_io_region *region;
> int ret;
>
> - if (*ppos + count > sizeof(*region))
> + if (pos + count > sizeof(*region))
> return -EINVAL;
>
> - private = dev_get_drvdata(mdev_parent_dev(mdev));
> if (!mutex_trylock(&private->io_mutex))
> return -EAGAIN;
>
> region = private->io_region;
> - if (copy_from_user((void *)region + *ppos, buf, count)) {
> + if (copy_from_user((void *)region + pos, buf, count)) {
> ret = -EFAULT;
> goto out_unlock;
> }
> @@ -217,19 +248,52 @@ static ssize_t vfio_ccw_mdev_write(struct mdev_device *mdev,
> return ret;
> }
>
> -static int vfio_ccw_mdev_get_device_info(struct vfio_device_info *info)
> +static ssize_t vfio_ccw_mdev_write(struct mdev_device *mdev,
> + const char __user *buf,
> + size_t count,
> + loff_t *ppos)
> +{
> + unsigned int index = VFIO_CCW_OFFSET_TO_INDEX(*ppos);
> + struct vfio_ccw_private *private;
> +
> + private = dev_get_drvdata(mdev_parent_dev(mdev));
> +
> + if (index >= VFIO_CCW_NUM_REGIONS + private->num_regions)
> + return -EINVAL;
> +
> + switch (index) {
> + case VFIO_CCW_CONFIG_REGION_INDEX:
> + return vfio_ccw_mdev_write_io_region(private, buf, count, ppos);
> + default:
> + index -= VFIO_CCW_NUM_REGIONS;
> + return private->region[index].ops->write(private, buf, count,
> + ppos);
> + }
> +
> + return -EINVAL;
> +}
> +
> +static int vfio_ccw_mdev_get_device_info(struct vfio_device_info *info,
> + struct mdev_device *mdev)
> {
> + struct vfio_ccw_private *private;
> +
> + private = dev_get_drvdata(mdev_parent_dev(mdev));
> info->flags = VFIO_DEVICE_FLAGS_CCW | VFIO_DEVICE_FLAGS_RESET;
> - info->num_regions = VFIO_CCW_NUM_REGIONS;
> + info->num_regions = VFIO_CCW_NUM_REGIONS + private->num_regions;
> info->num_irqs = VFIO_CCW_NUM_IRQS;
>
> return 0;
> }
>
> static int vfio_ccw_mdev_get_region_info(struct vfio_region_info *info,
> - u16 *cap_type_id,
> - void **cap_type)
> + struct mdev_device *mdev,
> + unsigned long arg)
> {
> + struct vfio_ccw_private *private;
> + int i;
> +
> + private = dev_get_drvdata(mdev_parent_dev(mdev));
> switch (info->index) {
> case VFIO_CCW_CONFIG_REGION_INDEX:
> info->offset = 0;
> @@ -237,9 +301,51 @@ static int vfio_ccw_mdev_get_region_info(struct vfio_region_info *info,
> info->flags = VFIO_REGION_INFO_FLAG_READ
> | VFIO_REGION_INFO_FLAG_WRITE;
> return 0;
> - default:
> - return -EINVAL;
> + default: /* all other regions are handled via capability chain */
> + {
> + struct vfio_info_cap caps = { .buf = NULL, .size = 0 };
> + struct vfio_region_info_cap_type cap_type = {
> + .header.id = VFIO_REGION_INFO_CAP_TYPE,
> + .header.version = 1 };
> + int ret;
> +
> + if (info->index >=
> + VFIO_CCW_NUM_REGIONS + private->num_regions)
> + return -EINVAL;
I notice the similarity of this hunk to drivers/vfio/pci/vfio_pci.c ...
While I was trying to discern the likelihood/possibility/usefulness of
combining the two, I noticed that there is one difference at this point
in the other file, which was added by commit 0e714d27786c ("vfio/pci:
Fix potential Spectre v1")
This got me off on a tangent of setting up smatch in my environment, and
sure enough it flags this point [1] as being problematic:
drivers/s390/cio/vfio_ccw_ops.c:328 vfio_ccw_mdev_get_region_info()
warn: potential spectre issue 'private->region' [r]
Might need to consider the same? (And lends credence to my concern
about the capability chain code being duplicated.)
> +
> + i = info->index - VFIO_CCW_NUM_REGIONS;
> +
> + info->offset = VFIO_CCW_INDEX_TO_OFFSET(info->index);
> + info->size = private->region[i].size;
[1] smatch actually points to this line, though the referenced commit
inserts a line up there.
> + info->flags = private->region[i].flags;
> +
> + cap_type.type = private->region[i].type;
> + cap_type.subtype = private->region[i].subtype;
> +
> + ret = vfio_info_add_capability(&caps, &cap_type.header,
> + sizeof(cap_type));
> + if (ret)
> + return ret;
> +
> + info->flags |= VFIO_REGION_INFO_FLAG_CAPS;
> + if (info->argsz < sizeof(*info) + caps.size) {
> + info->argsz = sizeof(*info) + caps.size;
> + info->cap_offset = 0;
> + } else {
> + vfio_info_cap_shift(&caps, sizeof(*info));
> + if (copy_to_user((void __user *)arg + sizeof(*info),
> + caps.buf, caps.size)) {
> + kfree(caps.buf);
> + return -EFAULT;
> + }
> + info->cap_offset = sizeof(*info);
> + }
> +
> + kfree(caps.buf);
> +
> + }
> }
> + return 0;
> }
>
> static int vfio_ccw_mdev_get_irq_info(struct vfio_irq_info *info)
> @@ -316,6 +422,32 @@ static int vfio_ccw_mdev_set_irqs(struct mdev_device *mdev,
> }
> }
>
> +int vfio_ccw_register_dev_region(struct vfio_ccw_private *private,
> + unsigned int subtype,
> + const struct vfio_ccw_regops *ops,
> + size_t size, u32 flags, void *data)
> +{
> + struct vfio_ccw_region *region;
> +
> + region = krealloc(private->region,
> + (private->num_regions + 1) * sizeof(*region),
> + GFP_KERNEL);
> + if (!region)
> + return -ENOMEM;
> +
> + private->region = region;
> + private->region[private->num_regions].type = VFIO_REGION_TYPE_CCW;
> + private->region[private->num_regions].subtype = subtype;
> + private->region[private->num_regions].ops = ops;
> + private->region[private->num_regions].size = size;
> + private->region[private->num_regions].flags = flags;
> + private->region[private->num_regions].data = data;
> +
> + private->num_regions++;
> +
> + return 0;
> +}
> +
> static ssize_t vfio_ccw_mdev_ioctl(struct mdev_device *mdev,
> unsigned int cmd,
> unsigned long arg)
> @@ -336,7 +468,7 @@ static ssize_t vfio_ccw_mdev_ioctl(struct mdev_device *mdev,
> if (info.argsz < minsz)
> return -EINVAL;
>
> - ret = vfio_ccw_mdev_get_device_info(&info);
> + ret = vfio_ccw_mdev_get_device_info(&info, mdev);
> if (ret)
> return ret;
>
> @@ -345,8 +477,6 @@ static ssize_t vfio_ccw_mdev_ioctl(struct mdev_device *mdev,
> case VFIO_DEVICE_GET_REGION_INFO:
> {
> struct vfio_region_info info;
> - u16 cap_type_id = 0;
> - void *cap_type = NULL;
>
> minsz = offsetofend(struct vfio_region_info, offset);
>
> @@ -356,8 +486,7 @@ static ssize_t vfio_ccw_mdev_ioctl(struct mdev_device *mdev,
> if (info.argsz < minsz)
> return -EINVAL;
>
> - ret = vfio_ccw_mdev_get_region_info(&info, &cap_type_id,
> - &cap_type);
> + ret = vfio_ccw_mdev_get_region_info(&info, mdev, arg);
> if (ret)
> return ret;
>
> diff --git a/drivers/s390/cio/vfio_ccw_private.h b/drivers/s390/cio/vfio_ccw_private.h
> index 32173cbd838d..c979eb32fb1c 100644
> --- a/drivers/s390/cio/vfio_ccw_private.h
> +++ b/drivers/s390/cio/vfio_ccw_private.h
> @@ -3,9 +3,11 @@
> * Private stuff for vfio_ccw driver
> *
> * Copyright IBM Corp. 2017
> + * Copyright Red Hat, Inc. 2019
> *
> * Author(s): Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
> * Xiao Feng Ren <renxiaof@linux.vnet.ibm.com>
> + * Cornelia Huck <cohuck@redhat.com>
> */
>
> #ifndef _VFIO_CCW_PRIVATE_H_
> @@ -19,6 +21,38 @@
> #include "css.h"
> #include "vfio_ccw_cp.h"
>
> +#define VFIO_CCW_OFFSET_SHIFT 40
> +#define VFIO_CCW_OFFSET_TO_INDEX(off) (off >> VFIO_CCW_OFFSET_SHIFT)
> +#define VFIO_CCW_INDEX_TO_OFFSET(index) ((u64)(index) << VFIO_CCW_OFFSET_SHIFT)
> +#define VFIO_CCW_OFFSET_MASK (((u64)(1) << VFIO_CCW_OFFSET_SHIFT) - 1)
I know Farhan asked this back in v1, but I'd still love a better answer
than "vfio-pci did this" to what this is. There's a lot more regions
prior to the capability chain in vfio-pci than here (9 versus 1), so I'd
like to be certain it's not related to that.
> +
> +/* capability chain handling similar to vfio-pci */
> +struct vfio_ccw_private;
> +struct vfio_ccw_region;
> +
> +struct vfio_ccw_regops {
> + ssize_t (*read)(struct vfio_ccw_private *private, char __user *buf,
> + size_t count, loff_t *ppos);
> + ssize_t (*write)(struct vfio_ccw_private *private,
> + const char __user *buf, size_t count, loff_t *ppos);
> + void (*release)(struct vfio_ccw_private *private,
> + struct vfio_ccw_region *region);
> +};
> +
> +struct vfio_ccw_region {
> + u32 type;
> + u32 subtype;
> + const struct vfio_ccw_regops *ops;
> + void *data;
> + size_t size;
> + u32 flags;
> +};
> +
> +int vfio_ccw_register_dev_region(struct vfio_ccw_private *private,
> + unsigned int subtype,
> + const struct vfio_ccw_regops *ops,
> + size_t size, u32 flags, void *data);
> +
> /**
> * struct vfio_ccw_private
> * @sch: pointer to the subchannel
> @@ -29,6 +63,8 @@
> * @nb: notifier for vfio events
> * @io_region: MMIO region to input/output I/O arguments/results
> * @io_mutex: protect against concurrent update of I/O regions
> + * @region: additional regions for other subchannel operations
> + * @num_regions: number of additional regions
> * @cp: channel program for the current I/O operation
> * @irb: irb info received from interrupt
> * @scsw: scsw info
> @@ -44,6 +80,8 @@ struct vfio_ccw_private {
> struct notifier_block nb;
> struct ccw_io_region *io_region;
> struct mutex io_mutex;
> + struct vfio_ccw_region *region;
> + int num_regions;
>
> struct channel_program cp;
> struct irb irb;
> diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
> index 02bb7ad6e986..56e2413d3e00 100644
> --- a/include/uapi/linux/vfio.h
> +++ b/include/uapi/linux/vfio.h
> @@ -353,6 +353,8 @@ struct vfio_region_gfx_edid {
> #define VFIO_DEVICE_GFX_LINK_STATE_DOWN 2
> };
>
> +#define VFIO_REGION_TYPE_CCW (2)
> +
I'm not sure if this should be here to keep it in its own area (esp. for
when patch 6 comes along), or with VFIO_REGION_TYPE_GFX to make it
noticeable where we are in the list without grepping for
VFIO_REGION_TYPE. I guess it's just what it is, even if I'm not
thrilled about it.
> /*
> * 10de vendor sub-type
> *
>
This generally looks sane to me, even though I can't get past the idea
that there's opportunities for improvement between the two. Maybe
that's refactoring for a day when someone is bored. ;-)
- Eric
next prev parent reply other threads:[~2019-02-15 15:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 13:22 [Qemu-devel] [PATCH v3 0/6] vfio-ccw: support hsch/csch (kernel part) Cornelia Huck
2019-01-30 13:22 ` [Qemu-devel] [PATCH v3 1/6] vfio-ccw: make it safe to access channel programs Cornelia Huck
2019-01-30 18:51 ` Halil Pasic
2019-01-31 11:52 ` Cornelia Huck
2019-01-31 12:34 ` Halil Pasic
2019-02-04 15:31 ` Cornelia Huck
2019-02-05 11:52 ` Halil Pasic
2019-02-05 12:35 ` Cornelia Huck
2019-02-05 14:48 ` Eric Farman
2019-02-05 15:14 ` Farhan Ali
2019-02-05 16:13 ` Cornelia Huck
2019-02-04 19:25 ` Eric Farman
2019-02-05 12:03 ` Cornelia Huck
2019-02-05 14:41 ` Eric Farman
2019-02-05 16:29 ` Cornelia Huck
2019-01-30 13:22 ` [Qemu-devel] [PATCH v3 2/6] vfio-ccw: rework ssch state handling Cornelia Huck
2019-02-04 21:29 ` Eric Farman
2019-02-05 12:10 ` Cornelia Huck
2019-02-05 14:31 ` Eric Farman
2019-02-05 16:32 ` Cornelia Huck
2019-01-30 13:22 ` [Qemu-devel] [PATCH v3 3/6] vfio-ccw: protect the I/O region Cornelia Huck
2019-02-08 21:26 ` Eric Farman
2019-02-11 15:57 ` Cornelia Huck
2019-01-30 13:22 ` [Qemu-devel] [PATCH v3 4/6] vfio-ccw: add capabilities chain Cornelia Huck
2019-02-15 15:46 ` Eric Farman [this message]
2019-02-19 11:06 ` Cornelia Huck
2019-01-30 13:22 ` [Qemu-devel] [PATCH v3 5/6] s390/cio: export hsch to modules Cornelia Huck
2019-01-30 13:22 ` [Qemu-devel] [PATCH v3 6/6] vfio-ccw: add handling for async channel instructions Cornelia Huck
2019-01-30 17:00 ` Halil Pasic
2019-01-30 17:09 ` Halil Pasic
2019-01-31 11:53 ` Cornelia Huck
2019-02-06 14:00 ` [Qemu-devel] [PATCH v3 0/6] vfio-ccw: support hsch/csch (kernel part) Cornelia Huck
2019-02-08 21:19 ` Eric Farman
2019-02-11 16:13 ` Cornelia Huck
2019-02-11 17:37 ` Eric Farman
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=2da327e8-d6cd-2350-31e1-d99edb0f2980@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.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;
as well as URLs for NNTP newsgroup(s).