From: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
qemu-s390x@nongnu.org, cohuck@redhat.com, borntraeger@de.ibm.com,
pmorel@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC PATCH 0/3] vfio: ccw: basic channel path event handling
Date: Mon, 15 Jan 2018 16:59:45 +0800 [thread overview]
Message-ID: <20180115085945.GC12499@bjsdjshi@linux.vnet.ibm.com> (raw)
In-Reply-To: <f9224bba-08fb-589e-ed6e-d8e967a8fe67@linux.vnet.ibm.com>
* Halil Pasic <pasic@linux.vnet.ibm.com> [2018-01-12 19:10:20 +0100]:
>
>
> On 01/11/2018 04:04 AM, Dong Jia Shi wrote:
> > What are still missing, thus need to be offered in the next version are:
> > - I/O termination and FSM state handling if currently we have I/O on the status
> > switched path.
> > - Vary on/off event is not sensible to a guest.
>
> I don't see a doc update. We do have documentation (in
> Documentation/s390/vfio-ccw.txt) in which the uapi interface with the
> regions and their purpose/usage is at least kind of explained. You are
> changing this interface without updating the doc.
>
> I would like to see documentation on this because I'm under the
> impression either the design is pretty convoluted or I did not
> get it at all.
Ah, I missed the documentation part. Thanks for pointing out. I will add
it in the next cycle.
--
Dong Jia Shi
next prev parent reply other threads:[~2018-01-15 8:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 3:04 [RFC PATCH 0/3] vfio: ccw: basic channel path event handling Dong Jia Shi
2018-01-11 3:04 ` [Qemu-devel] " Dong Jia Shi
2018-01-11 3:04 ` [RFC PATCH 1/3] vfio: ccw: introduce schib region Dong Jia Shi
2018-01-11 3:04 ` [Qemu-devel] " Dong Jia Shi
2018-01-11 14:16 ` Cornelia Huck
2018-01-11 14:16 ` [Qemu-devel] " Cornelia Huck
2018-01-15 6:43 ` Dong Jia Shi
2018-01-15 10:24 ` Cornelia Huck
2018-01-15 10:24 ` [Qemu-devel] " Cornelia Huck
2018-01-15 9:50 ` Pierre Morel
2018-01-15 9:50 ` [Qemu-devel] " Pierre Morel
2018-01-15 12:24 ` Cornelia Huck
2018-01-15 12:24 ` [Qemu-devel] " Cornelia Huck
2018-01-16 3:03 ` Dong Jia Shi
2018-01-11 3:04 ` [RFC PATCH 2/3] vfio: ccw: introduce channel path irq Dong Jia Shi
2018-01-11 3:04 ` [Qemu-devel] " Dong Jia Shi
2018-01-11 3:04 ` [RFC PATCH 3/3] vfio: ccw: handle chp event Dong Jia Shi
2018-01-11 3:04 ` [Qemu-devel] " Dong Jia Shi
2018-01-11 10:54 ` [RFC PATCH 0/3] vfio: ccw: basic channel path event handling Cornelia Huck
2018-01-11 10:54 ` [Qemu-devel] " Cornelia Huck
2018-01-15 8:57 ` Dong Jia Shi
2018-01-15 10:21 ` Pierre Morel
2018-01-15 10:21 ` [Qemu-devel] " Pierre Morel
2018-01-16 3:16 ` Dong Jia Shi
2018-01-16 15:53 ` Cornelia Huck
2018-01-16 15:53 ` [Qemu-devel] " Cornelia Huck
2018-01-12 18:10 ` Halil Pasic
2018-01-15 8:59 ` Dong Jia Shi [this message]
2018-01-16 15:57 ` Halil Pasic
2018-01-23 6:23 ` Dong Jia Shi
2018-01-25 11:12 ` Cornelia Huck
2018-01-25 12:56 ` Halil Pasic
2018-01-25 12:56 ` Halil Pasic
2018-01-30 3:37 ` Dong Jia Shi
2018-01-30 3:44 ` Dong Jia Shi
2018-01-30 3:44 ` [Qemu-devel] " Dong Jia Shi
2018-01-30 5:27 ` Dong Jia Shi
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=20180115085945.GC12499@bjsdjshi@linux.vnet.ibm.com \
--to=bjsdjshi@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.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 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.