From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: virtio@lists.oasis-open.org, virtio-comment@lists.oasis-open.org,
Jason Wang <jasowang@redhat.com>,
Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [virtio] Re: [PATCH] ccw: clarify device reset
Date: Mon, 25 Oct 2021 09:34:02 +0200 [thread overview]
Message-ID: <87czntsglx.fsf@redhat.com> (raw)
In-Reply-To: <20211022013520.1a92ebfe.pasic@linux.ibm.com>
On Fri, Oct 22 2021, Halil Pasic <pasic@linux.ibm.com> wrote:
> On Thu, 21 Oct 2021 18:23:51 +0200
> Cornelia Huck <cohuck@redhat.com> wrote:
>
>> >
>> > Halil, do you know if this has moved somewhere else? If yes, we need to
>> > update the link.
>>
>
> I can't remember they told me about moving it ;)
>
> I've found this one, and my guess is it works form the outside:
>
> https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=SA22720401
Hm, this one is accessible; however, the 'view' link leads to the same
500 again, and the 'download' link does not seem to do anything for me...
>
>
>> Also, do you have any feedback on this patch?
>
> I didn't see anything obviously wrong.
>
> """
> +The device signals completion of the reset operation by making the subchannel
> +status pending to indicate successful completion of the channel command.
> """
>
> may be little ambiguous. IMHO the point we should make is that the
> successful completion of the virtio reset happens before the
> successful completion of the ccw that requested the operation. "Status
> pending" is a little broad. We could get status pending with something
> like alert status, at least in theory. And if somebody silly would put
> the reset command with more commands following it in a channel program,
> we would not have to wait for the channel to complete and to see a status pending
> indicated at the subchannel.
Right, chaining something else to reset was not something that I had
considered. I basically wanted a condition that says "the device has
finished processing the reset ccw, and the driver has a way of knowing
about this." The driver can find out by looking at the ccw address in
the scsw, but has to keep the complicated rules for validity of that
field in mind; that might be too esoteric for the virtio spec. Maybe
"If the reset command is the last or only channel command in the command
chain, the device signals completion..."
Or is simply enough to note that reset is done once the device has
processed the reset ccw? We should not need to explain the fine details
of channel I/O processing in the spec.
>
> Another interesting question for the reset is system boundary. I.e. what
> exactly is reset. Some publications describe possible electric
> signaling interfaces, and I doubt this kind of a reset would be a
> complete reset of the device from that perspective. But that question is
> not what this patch is about. It just came to my mind.
As Jason noted in his mail, that's just virtio-specific reset.
>
> Sorry guys I'm already with one foot in vacation. This is the extent to
> which I can contribute right now.
Enjoy your vacation!
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
next prev parent reply other threads:[~2021-10-25 7:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 11:38 [PATCH] ccw: clarify device reset Cornelia Huck
2021-10-12 2:54 ` Jason Wang
2021-10-12 11:16 ` [virtio] " Cornelia Huck
2021-10-13 6:20 ` Jason Wang
2021-10-13 7:01 ` [virtio] " Cornelia Huck
2021-10-21 16:23 ` Cornelia Huck
2021-10-21 23:35 ` Halil Pasic
2021-10-25 1:29 ` Jason Wang
2021-10-25 7:36 ` Cornelia Huck
2021-10-25 7:34 ` Cornelia Huck [this message]
2021-10-27 7:58 ` Halil Pasic
2021-10-27 8:02 ` Jason Wang
2021-10-27 9:16 ` Cornelia Huck
2021-10-27 22:25 ` Halil Pasic
2021-10-28 6:55 ` [virtio-comment] " Cornelia Huck
2021-11-26 12:07 ` Cornelia Huck
2021-11-26 17:11 ` Halil Pasic
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=87czntsglx.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.