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 3/6] KVM: s390: Add GISA support
Date: Fri, 05 Sep 2014 10:29:26 +0200 [thread overview]
Message-ID: <54097466.2090502@suse.de> (raw)
In-Reply-To: <20140904105337.081387456@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 adds GISA (Guest Interrupt State Area) support
> to s390 kvm. GISA can be used for exitless interrupts. The
> patch provides a set of functions for GISA related operations
> like accessing GISA fields or registering ISCs for alert.
> Exploiters of GISA will follow with additional patches.
>
> Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
That's a nice feature. However, please make sure that you maintain the
abstraction levels.
What should happen is that you request an irqfd from FLIC. Then you
associate that irqfd with the PCI device.
Thanks to that association, both parties can now talk to each other and
negotiate their GISA number space and make sure things are connected.
However, it should always be possible to do things without this direct
IRQ injection.
So you should be able to receive an irqfd event when an IRQ happened, so
that VFIO user space applications can also handle interrupts for example.
And the same applies for interrupt injection. We also need to be able to
inject an adapter interrupt from QEMU for emulated devices ;).
Alex
next prev parent reply other threads:[~2014-09-05 8:29 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 [this message]
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
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=54097466.2090502@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).