From: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
qemu-s390x@nongnu.org
Cc: cohuck@redhat.com, borntraeger@de.ibm.com,
bjsdjshi@linux.vnet.ibm.com, pasic@linux.vnet.ibm.com,
pmorel@linux.vnet.ibm.com
Subject: [Qemu-devel] [RFC PATCH 0/5] vfio/ccw: basic channel path event handling
Date: Thu, 11 Jan 2018 04:04:54 +0100 [thread overview]
Message-ID: <20180111030459.33757-1-bjsdjshi@linux.vnet.ibm.com> (raw)
Hi Folks,
This is the QEMU couterpart for the "basic channel path event handling" series.
For more information, please refer to the kernel counterpart.
Dong Jia Shi (5):
vfio: linux-headers update for vfio-ccw
vfio/ccw: get schib region info
vfio/ccw: get irq info and set up handler for chp irq
vfio/ccw: update subchanel information block lazily
vfio/ccw: build schib with real schib information
hw/s390x/css.c | 97 ++++----------------
hw/s390x/s390-ccw.c | 32 +++++--
hw/vfio/ccw.c | 199 ++++++++++++++++++++++++++++++++++-------
include/hw/s390x/css.h | 3 +-
include/hw/s390x/s390-ccw.h | 4 +-
linux-headers/linux/vfio.h | 2 +
linux-headers/linux/vfio_ccw.h | 6 ++
target/s390x/ioinst.c | 3 +-
8 files changed, 224 insertions(+), 122 deletions(-)
--
2.13.5
next reply other threads:[~2018-01-11 3:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 3:04 Dong Jia Shi [this message]
2018-01-11 3:04 ` [Qemu-devel] [RFC PATCH 1/5] vfio: linux-headers update for vfio-ccw Dong Jia Shi
2018-01-11 3:04 ` [Qemu-devel] [RFC PATCH 2/5] vfio/ccw: get schib region info Dong Jia Shi
2018-01-11 3:04 ` [Qemu-devel] [RFC PATCH 3/5] vfio/ccw: get irq info and set up handler for chp irq Dong Jia Shi
2018-01-11 3:04 ` [Qemu-devel] [RFC PATCH 4/5] vfio/ccw: update subchanel information block lazily Dong Jia Shi
2018-01-11 3:04 ` [Qemu-devel] [RFC PATCH 5/5] vfio/ccw: build schib with real schib information 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=20180111030459.33757-1-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 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).