From: David Hildenbrand <david@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>, borntraeger@de.ibm.com
Cc: cohuck@redhat.com, agraf@suse.de, rth@twiddle.net,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
peter.maydell@linaro.org, pbonzini@redhat.com, mst@redhat.com,
eric.auger@redhat.com, akrowiak@linux.ibm.com,
pasic@linux.ibm.com
Subject: Re: [Qemu-devel] [PATCH v1 0/5] s390x/vfio: VFIO-AP interrupt control interception
Date: Fri, 2 Nov 2018 13:53:52 +0100 [thread overview]
Message-ID: <9d08961f-a29c-67e5-4ed4-3014d603b169@redhat.com> (raw)
In-Reply-To: <1541154621-22423-1-git-send-email-pmorel@linux.ibm.com>
On 02.11.18 11:30, Pierre Morel wrote:
> The S390 APQP/AQIC instruction can be intercepted by the host
> to configure the AP queues interruption handling for and handle
> the ISC used by the host and the guest and the indicator address.
>
> This patch series define the AQIC feature in the cpumodel,
> extend the APDevice type for per queue interrupt handling,
> intercept the APQP/AQIC instruction, uses the S390 adapter interface
> to setup the adapter and use a VFIO ioctl to let the VFIO-AP
> driver handle the host instruction associated with the intercepted
> guest instruction.
>
> This patch serie can be tested with the Linux/KVM patch series
> for the VFIO-AP driver: "s390: vfio: ap: Using GISA for AP Interrupt"
>
> Pierre Morel (5):
> s390x/vfio: ap: Linux uapi VFIO place holder
> s390x/cpumodel: Set up CPU model for AQIC interception
> s390x/vfio: ap: Definition for AP Adapter type
> s390x/vfio: ap: Intercepting AP Queue Interrupt Control
> s390x/vfio: ap: Implementing AP Queue Interrupt Control
>
> hw/vfio/ap.c | 100 ++++++++++++++++++++++++++++++++
> include/hw/s390x/ap-device.h | 55 ++++++++++++++++++
> include/hw/s390x/css.h | 1 +
> linux-headers/linux/vfio.h | 22 +++++++
> target/s390x/cpu_features.c | 1 +
> target/s390x/cpu_features_def.h | 1 +
> target/s390x/cpu_models.c | 1 +
> target/s390x/kvm.c | 20 +++++++
> 8 files changed, 201 insertions(+)
>
I had a very quick high level look at it and it seems to be in general fine.
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2018-11-02 12:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 10:30 [Qemu-devel] [PATCH v1 0/5] s390x/vfio: VFIO-AP interrupt control interception Pierre Morel
2018-11-02 10:30 ` [Qemu-devel] [PATCH v1 1/5] s390x/vfio: ap: Linux uapi VFIO place holder Pierre Morel
2018-11-02 10:30 ` [Qemu-devel] [PATCH v1 2/5] s390x/cpumodel: Set up CPU model for AQIC interception Pierre Morel
2018-11-02 10:30 ` [Qemu-devel] [PATCH v1 3/5] s390x/vfio: ap: Definition for AP Adapter type Pierre Morel
2018-11-02 10:30 ` [Qemu-devel] [PATCH v1 4/5] s390x/vfio: ap: Intercepting AP Queue Interrupt Control Pierre Morel
2018-11-07 12:40 ` Cornelia Huck
2018-11-07 22:44 ` Pierre Morel
2018-11-02 10:30 ` [Qemu-devel] [PATCH v1 5/5] s390x/vfio: ap: Implementing " Pierre Morel
2018-11-07 13:39 ` Cornelia Huck
2018-11-07 23:02 ` Pierre Morel
2018-11-02 12:53 ` David Hildenbrand [this message]
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=9d08961f-a29c-67e5-4ed4-3014d603b169@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=eric.auger@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
/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).