From: Eric Farman <farman@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>,
Jared Rossi <jrossi@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [RFC PATCH v2 4/9] vfio-ccw: Introduce a new schib region
Date: Fri, 14 Feb 2020 09:29:27 -0500 [thread overview]
Message-ID: <b7beb425-8af2-5db4-5d0d-e2f52a84d37f@linux.ibm.com> (raw)
In-Reply-To: <20200214133218.6841b81e.cohuck@redhat.com>
On 2/14/20 7:32 AM, Cornelia Huck wrote:
> On Thu, 6 Feb 2020 22:38:20 +0100
> Eric Farman <farman@linux.ibm.com> wrote:
>
>> From: Farhan Ali <alifm@linux.ibm.com>
>>
>> The schib region can be used by userspace to get the subchannel-
>> information block (SCHIB) for the passthrough subchannel.
>> This can be useful to get information such as channel path
>> information via the SCHIB.PMCW fields.
>>
>> Signed-off-by: Farhan Ali <alifm@linux.ibm.com>
>> Signed-off-by: Eric Farman <farman@linux.ibm.com>
>> ---
>>
>> Notes:
>> v1->v2:
>> - Add new region info to Documentation/s390/vfio-ccw.rst [CH]
>> - Add a block comment to struct ccw_schib_region [CH]
>>
>> v0->v1: [EF]
>> - Clean up checkpatch (#include, whitespace) errors
>> - Remove unnecessary includes from vfio_ccw_chp.c
>> - Add ret=-ENOMEM in error path for new region
>> - Add call to vfio_ccw_unregister_dev_regions() during error exit
>> path of vfio_ccw_mdev_open()
>> - New info on the module prologue
>> - Reorder cleanup of regions
>>
>> Documentation/s390/vfio-ccw.rst | 16 +++++-
>> drivers/s390/cio/Makefile | 2 +-
>> drivers/s390/cio/vfio_ccw_chp.c | 75 +++++++++++++++++++++++++++++
>> drivers/s390/cio/vfio_ccw_drv.c | 20 ++++++++
>> drivers/s390/cio/vfio_ccw_ops.c | 14 +++++-
>> drivers/s390/cio/vfio_ccw_private.h | 3 ++
>> include/uapi/linux/vfio.h | 1 +
>> include/uapi/linux/vfio_ccw.h | 10 ++++
>> 8 files changed, 137 insertions(+), 4 deletions(-)
>> create mode 100644 drivers/s390/cio/vfio_ccw_chp.c
>>
>> diff --git a/Documentation/s390/vfio-ccw.rst b/Documentation/s390/vfio-ccw.rst
>> index fca9c4f5bd9c..b805dc995fc8 100644
>> --- a/Documentation/s390/vfio-ccw.rst
>> +++ b/Documentation/s390/vfio-ccw.rst
>> @@ -231,6 +231,19 @@ This region is exposed via region type VFIO_REGION_SUBTYPE_CCW_ASYNC_CMD.
>>
>> Currently, CLEAR SUBCHANNEL and HALT SUBCHANNEL use this region.
>>
>> +vfio-ccw schib region
>> +---------------------
>> +
>> +The vfio-ccw schib region is used to return Subchannel-Information
>> +Block (SCHIB) data to userspace::
>> +
>> + struct ccw_schib_region {
>> + #define SCHIB_AREA_SIZE 52
>> + __u8 schib_area[SCHIB_AREA_SIZE];
>> + } __packed;
>> +
>> +This region is exposed via region type VFIO_REGION_SUBTYPE_CCW_SCHIB.
>
> Also mention that reading this triggers a stsch() updating the schib?
Yeah, I tucked that in the uapi header, but it should be mentioned here too.
>
>> +
>> vfio-ccw operation details
>> --------------------------
>>
>
> (...)
>
>> diff --git a/drivers/s390/cio/vfio_ccw_chp.c b/drivers/s390/cio/vfio_ccw_chp.c
>> new file mode 100644
>> index 000000000000..826d08379fe3
>> --- /dev/null
>> +++ b/drivers/s390/cio/vfio_ccw_chp.c
>> @@ -0,0 +1,75 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +/*
>> + * Channel path related status regions for vfio_ccw
>> + *
>> + * Copyright IBM Corp. 2019
>
> Should the year be updated?
Probably. :)
>
>> + *
>> + * Author(s): Farhan Ali <alifm@linux.ibm.com>
>> + */
>
> (...)
>
next prev parent reply other threads:[~2020-02-14 14:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 21:38 [RFC PATCH v2 0/9] s390x/vfio-ccw: Channel Path Handling Eric Farman
2020-02-06 21:38 ` [RFC PATCH v2 1/9] vfio-ccw: Introduce new helper functions to free/destroy regions Eric Farman
2020-02-06 21:38 ` [RFC PATCH v2 2/9] vfio-ccw: Register a chp_event callback for vfio-ccw Eric Farman
2020-02-14 12:11 ` Cornelia Huck
2020-02-14 16:35 ` Eric Farman
2020-03-24 15:58 ` Cornelia Huck
2020-03-26 2:09 ` Eric Farman
2020-03-26 6:47 ` Cornelia Huck
2020-03-26 11:54 ` Eric Farman
2020-02-06 21:38 ` [RFC PATCH v2 3/9] vfio-ccw: Refactor the unregister of the async regions Eric Farman
2020-02-06 21:38 ` [RFC PATCH v2 4/9] vfio-ccw: Introduce a new schib region Eric Farman
2020-02-14 12:32 ` Cornelia Huck
2020-02-14 14:29 ` Eric Farman [this message]
2020-02-06 21:38 ` [RFC PATCH v2 5/9] vfio-ccw: Introduce a new CRW region Eric Farman
2020-04-06 13:40 ` Cornelia Huck
2020-04-06 21:43 ` Eric Farman
2020-04-07 6:30 ` Cornelia Huck
2020-02-06 21:38 ` [RFC PATCH v2 6/9] vfio-ccw: Refactor IRQ handlers Eric Farman
2020-02-06 21:38 ` [RFC PATCH v2 7/9] vfio-ccw: Wire up the CRW irq and CRW region Eric Farman
2020-02-14 13:34 ` Cornelia Huck
2020-02-14 16:24 ` Eric Farman
2020-03-24 16:34 ` Cornelia Huck
2020-03-26 18:51 ` Eric Farman
2020-04-06 13:52 ` Cornelia Huck
2020-04-06 22:11 ` Eric Farman
2020-02-06 21:38 ` [RFC PATCH v2 8/9] vfio-ccw: Add trace for CRW event Eric Farman
2020-02-06 21:38 ` [RFC PATCH v2 9/9] vfio-ccw: Remove inline get_schid() routine Eric Farman
2020-02-14 13:27 ` Cornelia Huck
2020-02-14 14:27 ` Eric Farman
2020-02-07 9:12 ` [RFC PATCH v2 0/9] s390x/vfio-ccw: Channel Path Handling Cornelia Huck
2020-02-07 13:26 ` 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=b7beb425-8af2-5db4-5d0d-e2f52a84d37f@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=jjherne@linux.ibm.com \
--cc=jrossi@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.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