From: Farhan Ali <alifm@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: farman@linux.ibm.com, pasic@linux.ibm.com,
linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [RFC v2 5/5] vfio-ccw: Update documentation for csch/hsch
Date: Tue, 9 Jul 2019 08:47:38 -0400 [thread overview]
Message-ID: <58ece8ce-a155-3353-71f1-26e242db5c55@linux.ibm.com> (raw)
In-Reply-To: <20190709121445.1d7bf8ed.cohuck@redhat.com>
On 07/09/2019 06:14 AM, Cornelia Huck wrote:
> On Mon, 8 Jul 2019 16:10:38 -0400
> Farhan Ali <alifm@linux.ibm.com> wrote:
>
>> We now support CLEAR SUBCHANNEL and HALT SUBCHANNEL
>> via ccw_cmd_region.
>>
>
> Thanks, I forgot about this.
>
> Fixes: d5afd5d135c8 ("vfio-ccw: add handling for async channel instructions")
>
I don't know if this warranted a fixes tag but I will add it.
>> Signed-off-by: Farhan Ali <alifm@linux.ibm.com>
>> ---
>> Documentation/s390/vfio-ccw.rst | 31 ++++++++++++++++++++++++++++---
>> 1 file changed, 28 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/s390/vfio-ccw.rst b/Documentation/s390/vfio-ccw.rst
>> index 1f6d0b5..40e4110 100644
>> --- a/Documentation/s390/vfio-ccw.rst
>> +++ b/Documentation/s390/vfio-ccw.rst
>> @@ -180,6 +180,13 @@ The process of how these work together.
>> add it to an iommu_group and a vfio_group. Then we could pass through
>> the mdev to a guest.
>>
>> +
>> +VFIO-CCW Regions
>> +----------------
>> +
>> +The vfio-ccw driver exposes MMIO regions to accept requests from and return
>> +results to userspace.
>> +
>> vfio-ccw I/O region
>> -------------------
>>
>> @@ -205,6 +212,25 @@ irb_area stores the I/O result.
>>
>> ret_code stores a return code for each access of the region.
>>
>> +This region is always available.
>> +
>> +vfio-ccw cmd region
>> +-------------------
>> +
>> +The vfio-ccw cmd region is used to accept asynchronous instructions
>> +from userspace.
>> +
>> +#define VFIO_CCW_ASYNC_CMD_HSCH (1 << 0)
>> +#define VFIO_CCW_ASYNC_CMD_CSCH (1 << 1)
>> +struct ccw_cmd_region {
>> + __u32 command;
>> + __u32 ret_code;
>> +} __packed;
>> +
>> +This region is exposed via region type VFIO_REGION_SUBTYPE_CCW_ASYNC_CMD.
>> +
>> +CLEAR SUBCHANNEL and HALT SUBCHANNEL currently uses this region.
>
> "Currently, CLEAR SUBCHANNEL and HALT SUBCHANNEL use this region". ?
>
This sounds better to me :)
>> +
>> vfio-ccw operation details
>> --------------------------
>>
>> @@ -306,9 +332,8 @@ Together with the corresponding work in QEMU, we can bring the passed
>> through DASD/ECKD device online in a guest now and use it as a block
>> device.
>>
>> -While the current code allows the guest to start channel programs via
>> -START SUBCHANNEL, support for HALT SUBCHANNEL or CLEAR SUBCHANNEL is
>> -not yet implemented.
>> +The current code allows the guest to start channel programs via
>> +START SUBCHANNEL, and supports HALT SUBCHANNEL or CLEAR SUBCHANNEL.
>
> "The current code allows the guest to start channel programs via START
> SUBCHANNEL, and to issue HALT SUBCHANNEL and CLEAR SUBCHANNEL." ?
>
Same. I will update with the changes you requested.
>>
>> vfio-ccw supports classic (command mode) channel I/O only. Transport
>> mode (HPF) is not supported.
>
>
Thanks for taking a look.
Thanks
Farhan
prev parent reply other threads:[~2019-07-09 12:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 20:10 [RFC v2 0/5] Some vfio-ccw fixes Farhan Ali
2019-07-08 20:10 ` [RFC v2 1/5] vfio-ccw: Fix misleading comment when setting orb.cmd.c64 Farhan Ali
2019-07-09 9:57 ` Cornelia Huck
2019-07-08 20:10 ` [RFC v2 2/5] vfio-ccw: Fix memory leak and don't call cp_free in cp_init Farhan Ali
2019-07-09 10:06 ` Cornelia Huck
2019-07-09 14:07 ` Farhan Ali
2019-07-09 14:18 ` Cornelia Huck
2019-07-08 20:10 ` [RFC v2 3/5] vfio-ccw: Set pa_nr to 0 if memory allocation fails for pa_iova_pfn Farhan Ali
2019-07-09 10:08 ` Cornelia Huck
2019-07-08 20:10 ` [RFC v2 4/5] vfio-ccw: Don't call cp_free if we are processing a channel program Farhan Ali
2019-07-09 10:16 ` Cornelia Huck
2019-07-09 13:46 ` Farhan Ali
2019-07-09 14:21 ` Halil Pasic
2019-07-09 21:27 ` Farhan Ali
2019-07-10 13:45 ` Cornelia Huck
2019-07-10 16:10 ` Farhan Ali
2019-07-11 12:28 ` Eric Farman
2019-07-11 14:57 ` Halil Pasic
2019-07-11 20:09 ` Eric Farman
2019-07-12 13:59 ` Halil Pasic
2019-07-08 20:10 ` [RFC v2 5/5] vfio-ccw: Update documentation for csch/hsch Farhan Ali
2019-07-09 10:14 ` Cornelia Huck
2019-07-09 12:47 ` Farhan Ali [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=58ece8ce-a155-3353-71f1-26e242db5c55@linux.ibm.com \
--to=alifm@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=farman@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