From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>,
Frank Blaschka <blaschka@linux.vnet.ibm.com>
Cc: frank.blaschka@de.ibm.com, qemu-devel@nongnu.org,
linux-s390@vger.kernel.org, kvm@vger.kernel.org, aik@ozlabs.ru,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [RFC][patch 0/6] pci pass-through support for qemu/KVM on s390
Date: Mon, 08 Sep 2014 11:20:57 +0200 [thread overview]
Message-ID: <540D74F9.50903@redhat.com> (raw)
In-Reply-To: <540A44F2.3040803@suse.de>
Il 06/09/2014 01:19, Alexander Graf ha scritto:
>> > 1) interpretive execution of pci load/store instruction. If we use this function
>> > pci access does not get intercepted (no SIE exit) but is handled via microcode.
>> > To enable this we have to disable zpci device and enable it again with information
>> > from the SIE control block.
> Hrm. So how about you create a special vm ioctl for KVM that allows you
> to attach a VFIO device fd into the KVM VM context? Then the default
> would stay "accessible by mmap traps", but we could accelerate it with KVM.
There is already KVM_DEV_VFIO_GROUP_ADD and KVM_DEV_VFIO_GROUP_DEL.
Right now, they result in a call to kvm_arch_register_noncoherent_dma or
kvm_arch_unregister_noncoherent_dma, but you can add more hooks.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>,
Frank Blaschka <blaschka@linux.vnet.ibm.com>
Cc: linux-s390@vger.kernel.org, frank.blaschka@de.ibm.com,
kvm@vger.kernel.org, aik@ozlabs.ru, qemu-devel@nongnu.org,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [Qemu-devel] [RFC][patch 0/6] pci pass-through support for qemu/KVM on s390
Date: Mon, 08 Sep 2014 11:20:57 +0200 [thread overview]
Message-ID: <540D74F9.50903@redhat.com> (raw)
In-Reply-To: <540A44F2.3040803@suse.de>
Il 06/09/2014 01:19, Alexander Graf ha scritto:
>> > 1) interpretive execution of pci load/store instruction. If we use this function
>> > pci access does not get intercepted (no SIE exit) but is handled via microcode.
>> > To enable this we have to disable zpci device and enable it again with information
>> > from the SIE control block.
> Hrm. So how about you create a special vm ioctl for KVM that allows you
> to attach a VFIO device fd into the KVM VM context? Then the default
> would stay "accessible by mmap traps", but we could accelerate it with KVM.
There is already KVM_DEV_VFIO_GROUP_ADD and KVM_DEV_VFIO_GROUP_DEL.
Right now, they result in a call to kvm_arch_register_noncoherent_dma or
kvm_arch_unregister_noncoherent_dma, but you can add more hooks.
Paolo
next prev parent reply other threads:[~2014-09-08 9:20 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 10:52 [RFC][patch 0/6] pci pass-through support for qemu/KVM on s390 frank.blaschka
2014-09-04 10:52 ` [Qemu-devel] " frank.blaschka
2014-09-04 10:52 ` [RFC][patch 1/6] s390: cio: chsc function to register GIB frank.blaschka
2014-09-04 10:52 ` [Qemu-devel] " frank.blaschka
2014-09-04 10:52 ` [RFC][patch 2/6] s390: pci: export pci functions for pass-through usage frank.blaschka
2014-09-04 10:52 ` [Qemu-devel] " frank.blaschka
2014-09-04 10:52 ` [RFC][patch 3/6] KVM: s390: Add GISA support frank.blaschka
2014-09-04 10:52 ` [Qemu-devel] " frank.blaschka
2014-09-04 14:19 ` Heiko Carstens
2014-09-04 14:19 ` [Qemu-devel] " Heiko Carstens
2014-09-05 8:29 ` Alexander Graf
2014-09-05 8:29 ` [Qemu-devel] " Alexander Graf
2014-09-05 10:52 ` Frank Blaschka
2014-09-05 10:52 ` [Qemu-devel] " Frank Blaschka
2014-09-04 10:52 ` [RFC][patch 4/6] KVM: s390: Add PCI pass-through support frank.blaschka
2014-09-04 10:52 ` [Qemu-devel] " frank.blaschka
2014-09-05 8:37 ` Alexander Graf
2014-09-05 8:37 ` [Qemu-devel] " Alexander Graf
2014-09-04 10:52 ` [RFC][patch 5/6] s390: Add PCI bus support frank.blaschka
2014-09-04 10:52 ` [Qemu-devel] " frank.blaschka
2014-09-04 10:52 ` [RFC][patch 6/6] s390: Add PCI pass-through device support frank.blaschka
2014-09-04 10:52 ` [Qemu-devel] " frank.blaschka
2014-09-04 13:16 ` [RFC][patch 0/6] pci pass-through support for qemu/KVM on s390 Alex Williamson
2014-09-04 13:16 ` [Qemu-devel] " Alex Williamson
2014-09-05 7:46 ` Frank Blaschka
2014-09-05 7:46 ` [Qemu-devel] " Frank Blaschka
2014-09-05 8:35 ` Alexander Graf
2014-09-05 8:35 ` [Qemu-devel] " Alexander Graf
2014-09-05 11:55 ` Frank Blaschka
2014-09-05 11:55 ` [Qemu-devel] " Frank Blaschka
2014-09-05 23:03 ` Alexander Graf
2014-09-05 23:03 ` [Qemu-devel] " Alexander Graf
2014-09-05 8:21 ` Alexander Graf
2014-09-05 8:21 ` [Qemu-devel] " Alexander Graf
2014-09-05 11:39 ` Frank Blaschka
2014-09-05 11:39 ` [Qemu-devel] " Frank Blaschka
2014-09-05 23:19 ` Alexander Graf
2014-09-05 23:19 ` [Qemu-devel] " Alexander Graf
2014-09-08 9:20 ` Paolo Bonzini [this message]
2014-09-08 9:20 ` Paolo Bonzini
2014-09-08 14:19 ` Alex Williamson
2014-09-08 14:19 ` [Qemu-devel] " 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=540D74F9.50903@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=blaschka@linux.vnet.ibm.com \
--cc=frank.blaschka@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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 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.