From: Alexander Graf <agraf@suse.de>
To: frank.blaschka@de.ibm.com, qemu-devel@nongnu.org,
linux-s390@vger.kernel.org, kvm@vger.kernel.org
Cc: aik@ozlabs.ru, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [RFC][patch 4/6] KVM: s390: Add PCI pass-through support
Date: Fri, 05 Sep 2014 10:37:23 +0200 [thread overview]
Message-ID: <54097643.30507@suse.de> (raw)
In-Reply-To: <20140904105337.202077766@de.ibm.com>
On 04.09.14 12:52, frank.blaschka@de.ibm.com wrote:
> From: Frank Blaschka <frank.blaschka@de.ibm.com>
>
> This patch implemets PCI pass-through kernel support for s390.
> Design approach is very similar to the x86 device assignment.
> User space executes the KVM_ASSIGN_PCI_DEVICE ioctl to create
> a proxy instance in the kernel KVM and connect this instance to the
> host pci device. s390 pci instructions are intercepted in kernel and
> operations are passed directly to the assigned pci device.
> To take advantage of all system z specific virtualization features
> we need to access the SIE control block residing in KVM. Also we have to
> enable z pci devices with special configuration information coming
> form the SIE block as well.
>
> Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
> ---
> arch/s390/include/asm/kvm_host.h | 1
> arch/s390/kvm/Makefile | 2
> arch/s390/kvm/intercept.c | 1
> arch/s390/kvm/kvm-s390.c | 33
> arch/s390/kvm/kvm-s390.h | 17
> arch/s390/kvm/pci.c | 2130 +++++++++++++++++++++++++++++++++++++++
> arch/s390/kvm/priv.c | 21
> 7 files changed, 2202 insertions(+), 3 deletions(-)
I would love to review this patch, but in its current form it's
impossible to do. I can't possibly keep > 2000 lines of code in my head.
Alex
next prev parent reply other threads:[~2014-09-05 8:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 10:52 [Qemu-devel] [RFC][patch 0/6] pci pass-through support for qemu/KVM on s390 frank.blaschka
2014-09-04 10:52 ` [Qemu-devel] [RFC][patch 1/6] s390: cio: chsc function to register GIB frank.blaschka
2014-09-04 10:52 ` [Qemu-devel] [RFC][patch 2/6] s390: pci: export pci functions for pass-through usage frank.blaschka
2014-09-04 10:52 ` [Qemu-devel] [RFC][patch 3/6] KVM: s390: Add GISA support frank.blaschka
2014-09-04 14:19 ` Heiko Carstens
2014-09-05 8:29 ` Alexander Graf
2014-09-05 10:52 ` Frank Blaschka
2014-09-04 10:52 ` [Qemu-devel] [RFC][patch 4/6] KVM: s390: Add PCI pass-through support frank.blaschka
2014-09-05 8:37 ` Alexander Graf [this message]
2014-09-04 10:52 ` [Qemu-devel] [RFC][patch 5/6] s390: Add PCI bus support frank.blaschka
2014-09-04 10:52 ` [Qemu-devel] [RFC][patch 6/6] s390: Add PCI pass-through device support frank.blaschka
2014-09-04 13:16 ` [Qemu-devel] [RFC][patch 0/6] pci pass-through support for qemu/KVM on s390 Alex Williamson
2014-09-05 7:46 ` Frank Blaschka
2014-09-05 8:35 ` Alexander Graf
2014-09-05 11:55 ` Frank Blaschka
2014-09-05 23:03 ` Alexander Graf
2014-09-05 8:21 ` Alexander Graf
2014-09-05 11:39 ` Frank Blaschka
2014-09-05 23:19 ` Alexander Graf
2014-09-08 9:20 ` Paolo Bonzini
2014-09-08 14:19 ` Alex Williamson
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=54097643.30507@suse.de \
--to=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=frank.blaschka@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).