Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Jason Wang <jasowang@redhat.com>, Halil Pasic <pasic@linux.ibm.com>
Cc: virtio@lists.oasis-open.org, virtio-comment@lists.oasis-open.org
Subject: Re: [virtio] Re: [PATCH] ccw: clarify device reset
Date: Mon, 25 Oct 2021 09:36:56 +0200	[thread overview]
Message-ID: <87a6ixsgh3.fsf@redhat.com> (raw)
In-Reply-To: <CACGkMEvD1yihytUSarjqD2NjrUv_=YsM82pvG0OnhaqRqq1iWg@mail.gmail.com>

On Mon, Oct 25 2021, Jason Wang <jasowang@redhat.com> wrote:

> On Fri, Oct 22, 2021 at 7:35 AM Halil Pasic <pasic@linux.ibm.com> wrote:
>> 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.
>
> Since virtio is built on top of the transport. I think the lower level
> (transport) reset implies a virtio reset.

...ok, maybe I misrepresented your reply in my reply to Halil (should
not write before the first coffee). But I would indeed expect a
low-level reset (e.g. a channel subsystem reset) to imply that the
virtio structures are reset as well.


---------------------------------------------------------------------
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 


  reply	other threads:[~2021-10-25  7:36 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 [this message]
2021-10-25  7:34             ` Cornelia Huck
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=87a6ixsgh3.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox