qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: Pierre Morel <pmorel@linux.ibm.com>,
	linux-s390@vger.kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, qemu-devel@nongnu.org,
	qemu-s390x@nongnu.org, Dong Jia Shi <bjsdjshi@linux.ibm.com>
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH RFC 2/2] vfio-ccw: support for halt/clear subchannel
Date: Mon, 11 Jun 2018 13:12:41 +0200	[thread overview]
Message-ID: <20180611131241.06100c12.cohuck@redhat.com> (raw)
In-Reply-To: <0c1e1b26-0c6a-fdc2-0c1a-2e2d58c2cb73@linux.ibm.com>

On Fri, 8 Jun 2018 22:40:39 +0200
Halil Pasic <pasic@linux.ibm.com> wrote:

> Your welcome. The discussion is kind of taking place all over the
> place. I'm actively trying to find the best place to answer, and avoid
> overtalking topics -- but it does not seem to work. Please bear with me.

To help with this discussion (and with vfio-ccw design and development
in general), I've created
https://wiki.qemu.org/ToDo/Channel_I/O_Passthrough to collect some
things. Let me know if any of you folks still needs a wiki account.

  reply	other threads:[~2018-06-11 11:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 ` [Qemu-devel] [PATCH RFC 1/2] s390/cio: export hsch to modules Cornelia Huck
2018-05-11  9:36   ` Pierre Morel
2018-05-09 15:48 ` [Qemu-devel] [PATCH RFC 2/2] vfio-ccw: support for halt/clear subchannel Cornelia Huck
2018-05-11  9:33   ` Pierre Morel
2018-05-15 16:10     ` Cornelia Huck
2018-05-16 13:32       ` Pierre Morel
2018-05-22 12:52         ` Cornelia Huck
2018-05-22 15:10           ` Pierre Morel
2018-06-05 13:14             ` Cornelia Huck
2018-06-05 15:23               ` Pierre Morel
2018-06-05 15:36                 ` Cornelia Huck
2018-06-06 12:21                 ` Cornelia Huck
2018-06-06 14:15                   ` Pierre Morel
2018-06-07  9:54                     ` Cornelia Huck
2018-06-07 16:17                       ` [Qemu-devel] [qemu-s390x] " Halil Pasic
2018-06-07 16:34                         ` Cornelia Huck
2018-06-08 20:40                           ` Halil Pasic
2018-06-11 11:12                             ` Cornelia Huck [this message]
2018-06-11 16:00                             ` Cornelia Huck
2018-06-07 16:37                       ` [Qemu-devel] " Pierre Morel
2018-06-08 12:20                         ` Cornelia Huck
2018-06-08 13:13                           ` Halil Pasic
2018-06-08 14:45                             ` Cornelia Huck
2018-06-08 15:51                               ` Pierre Morel
2018-06-12  9:59                                 ` Cornelia Huck
2018-06-12 13:56                                   ` Pierre Morel
2018-06-12 14:08                                     ` Halil Pasic
2018-06-12 15:25                                       ` 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=20180611131241.06100c12.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: 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;
as well as URLs for NNTP newsgroup(s).