From: Cornelia Huck <cohuck@redhat.com> To: Dong Jia Shi <bjsdjshi@linux.ibm.com>, Halil Pasic <pasic@linux.ibm.com>, Pierre Morel <pmorel@linux.ibm.com> Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, qemu-s390x@nongnu.org, qemu-devel@nongnu.org, Cornelia Huck <cohuck@redhat.com> Subject: [PATCH RFC 0/2] vfio-ccw: support for {halt,clear} subchannel Date: Wed, 9 May 2018 17:48:20 +0200 [thread overview] Message-ID: <20180509154822.23510-1-cohuck@redhat.com> (raw) Hi, this (RFC) is an initial stab at passing the halt and clear subchannel operations to the host device. Today, host userspace is emulating those two operations, but we really want to execute them on the host device (e.g. for error recovery situations). The nice thing about this approach is that is independent from userspace changes: Unless userspace forwards halt/clear requests, we behave as before. Conversely, userspace can simply try to submit halt/clear, and old kernels will simply indicate that it is not supported. This survives triggering clear subchannel in the guest (hacked in by myself) together with an update QEMU (to be posted in a moment). Obviously, this needs some more work. Better support for async handling comes to mind. We probably also want to support other channel I/O instructions. Cornelia Huck (2): s390/cio: export hsch to modules vfio-ccw: support for halt/clear subchannel drivers/s390/cio/ioasm.c | 1 + drivers/s390/cio/vfio_ccw_drv.c | 10 ++++- drivers/s390/cio/vfio_ccw_fsm.c | 94 ++++++++++++++++++++++++++++++++++++----- 3 files changed, 93 insertions(+), 12 deletions(-) -- 2.14.3
WARNING: multiple messages have this Message-ID (diff)
From: Cornelia Huck <cohuck@redhat.com> To: Dong Jia Shi <bjsdjshi@linux.ibm.com>, Halil Pasic <pasic@linux.ibm.com>, Pierre Morel <pmorel@linux.ibm.com> Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, qemu-s390x@nongnu.org, qemu-devel@nongnu.org, Cornelia Huck <cohuck@redhat.com> Subject: [Qemu-devel] [PATCH RFC 0/2] vfio-ccw: support for {halt, clear} subchannel Date: Wed, 9 May 2018 17:48:20 +0200 [thread overview] Message-ID: <20180509154822.23510-1-cohuck@redhat.com> (raw) Hi, this (RFC) is an initial stab at passing the halt and clear subchannel operations to the host device. Today, host userspace is emulating those two operations, but we really want to execute them on the host device (e.g. for error recovery situations). The nice thing about this approach is that is independent from userspace changes: Unless userspace forwards halt/clear requests, we behave as before. Conversely, userspace can simply try to submit halt/clear, and old kernels will simply indicate that it is not supported. This survives triggering clear subchannel in the guest (hacked in by myself) together with an update QEMU (to be posted in a moment). Obviously, this needs some more work. Better support for async handling comes to mind. We probably also want to support other channel I/O instructions. Cornelia Huck (2): s390/cio: export hsch to modules vfio-ccw: support for halt/clear subchannel drivers/s390/cio/ioasm.c | 1 + drivers/s390/cio/vfio_ccw_drv.c | 10 ++++- drivers/s390/cio/vfio_ccw_fsm.c | 94 ++++++++++++++++++++++++++++++++++++----- 3 files changed, 93 insertions(+), 12 deletions(-) -- 2.14.3
next reply other threads:[~2018-05-09 15:48 UTC|newest] Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-09 15:48 Cornelia Huck [this message] 2018-05-09 15:48 ` [Qemu-devel] [PATCH RFC 0/2] vfio-ccw: support for {halt, clear} subchannel Cornelia Huck 2018-05-09 15:48 ` [PATCH RFC 1/2] s390/cio: export hsch to modules Cornelia Huck 2018-05-09 15:48 ` [Qemu-devel] " Cornelia Huck 2018-05-11 9:36 ` Pierre Morel 2018-05-11 9:36 ` [Qemu-devel] " Pierre Morel 2018-05-09 15:48 ` [PATCH RFC 2/2] vfio-ccw: support for halt/clear subchannel Cornelia Huck 2018-05-09 15:48 ` [Qemu-devel] " Cornelia Huck 2018-05-11 9:33 ` Pierre Morel 2018-05-11 9:33 ` [Qemu-devel] " Pierre Morel 2018-05-15 16:10 ` Cornelia Huck 2018-05-15 16:10 ` [Qemu-devel] " Cornelia Huck 2018-05-16 13:32 ` Pierre Morel 2018-05-16 13:32 ` [Qemu-devel] " Pierre Morel 2018-05-22 12:52 ` Cornelia Huck 2018-05-22 12:52 ` [Qemu-devel] " Cornelia Huck 2018-05-22 15:10 ` Pierre Morel 2018-05-22 15:10 ` [Qemu-devel] " Pierre Morel 2018-06-05 13:14 ` Cornelia Huck 2018-06-05 13:14 ` [Qemu-devel] " Cornelia Huck 2018-06-05 15:23 ` Pierre Morel 2018-06-05 15:23 ` [Qemu-devel] " Pierre Morel 2018-06-05 15:36 ` Cornelia Huck 2018-06-05 15:36 ` [Qemu-devel] " Cornelia Huck 2018-06-06 12:21 ` Cornelia Huck 2018-06-06 12:21 ` [Qemu-devel] " Cornelia Huck 2018-06-06 14:15 ` Pierre Morel 2018-06-06 14:15 ` [Qemu-devel] " Pierre Morel 2018-06-07 9:54 ` Cornelia Huck 2018-06-07 9:54 ` [Qemu-devel] " Cornelia Huck 2018-06-07 16:17 ` [qemu-s390x] " Halil Pasic 2018-06-07 16:17 ` [Qemu-devel] " Halil Pasic 2018-06-07 16:34 ` Cornelia Huck 2018-06-07 16:34 ` [Qemu-devel] " Cornelia Huck 2018-06-08 20:40 ` Halil Pasic 2018-06-08 20:40 ` [Qemu-devel] " Halil Pasic 2018-06-11 11:12 ` Cornelia Huck 2018-06-11 11:12 ` [Qemu-devel] " Cornelia Huck 2018-06-11 16:00 ` Cornelia Huck 2018-06-11 16:00 ` [Qemu-devel] " Cornelia Huck 2018-06-07 16:37 ` Pierre Morel 2018-06-07 16:37 ` [Qemu-devel] " Pierre Morel 2018-06-08 12:20 ` Cornelia Huck 2018-06-08 12:20 ` [Qemu-devel] " Cornelia Huck 2018-06-08 13:13 ` Halil Pasic 2018-06-08 13:13 ` [Qemu-devel] " Halil Pasic 2018-06-08 14:45 ` Cornelia Huck 2018-06-08 14:45 ` [Qemu-devel] " Cornelia Huck 2018-06-08 15:51 ` Pierre Morel 2018-06-08 15:51 ` [Qemu-devel] " Pierre Morel 2018-06-12 9:59 ` Cornelia Huck 2018-06-12 9:59 ` [Qemu-devel] " Cornelia Huck 2018-06-12 13:56 ` Pierre Morel 2018-06-12 13:56 ` [Qemu-devel] " Pierre Morel 2018-06-12 14:08 ` Halil Pasic 2018-06-12 14:08 ` [Qemu-devel] " Halil Pasic 2018-06-12 15:25 ` Cornelia Huck 2018-06-12 15:25 ` [Qemu-devel] " Cornelia Huck 2018-06-08 21:10 ` 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=20180509154822.23510-1-cohuck@redhat.com \ --to=cohuck@redhat.com \ --cc=bjsdjshi@linux.ibm.com \ --cc=kvm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-s390@vger.kernel.org \ --cc=pasic@linux.ibm.com \ --cc=pmorel@linux.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: linkBe 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.