From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Pierre Morel <pmorel@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, agraf@suse.de, zyimin@linux.vnet.ibm.com,
pasic@linux.vnet.ibm.com, qemu-s390x@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1 0/5][RFC] Refactoring of AIS support
Date: Mon, 30 Oct 2017 13:42:33 +0100 [thread overview]
Message-ID: <20171030134233.6aaa81a1.cohuck@redhat.com> (raw)
In-Reply-To: <feea3ded-fecc-50ff-fe70-09e63966933b@de.ibm.com>
On Mon, 30 Oct 2017 09:28:09 +0100
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> Now I thought about that for a while and I start to think that we cannot implement ais
> in QEMU and cover all cases.
> One aspect was certainly passthrough (like you handled in patch 4).
> Another aspect is that some interrupts might be injected from the kernel - even for
> emulated devices. e.g. virtio-pci together with vhost-net, will inject interrupts via
> the set_irq callback. I think disabling irqfd for these cases is not a good idea.
Is there still a fallback for irqfd emulation?
>
> So what about adding a new KVM capability (for 4.14), fixup the other things in
> QEMU and then bind it to the new capability?
For 4.15, surely?
Probably the only way we can make this work correctly...
next prev parent reply other threads:[~2017-10-30 12:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 13:49 [Qemu-devel] [PATCH v1 0/5][RFC] Refactoring of AIS support Pierre Morel
2017-10-04 13:49 ` [Qemu-devel] [PATCH v1 1/5] s390x/kvm: Enable AIS from CPU model always Pierre Morel
2017-10-09 9:09 ` Cornelia Huck
2017-10-09 13:58 ` Pierre Morel
2017-10-04 13:49 ` [Qemu-devel] [PATCH v1 2/5] s390x/css: Use AIS AIRQ injection only if adapter support AIS Pierre Morel
2017-10-09 8:17 ` Cornelia Huck
2017-10-09 13:55 ` Pierre Morel
2017-10-04 13:49 ` [Qemu-devel] [PATCH v1 3/5] s390x/intc: Emulate Adapter Interrupt Suppression Pierre Morel
2017-10-09 8:42 ` Cornelia Huck
2017-10-09 9:08 ` Cornelia Huck
2017-10-09 14:05 ` Pierre Morel
2017-10-09 14:03 ` Pierre Morel
2017-10-04 13:49 ` [Qemu-devel] [PATCH v1 4/5] s390x/pci: Refuse to realize VFIO-PCI if AIS needed but supported Pierre Morel
2017-10-09 9:06 ` Cornelia Huck
2017-10-09 14:25 ` Pierre Morel
2017-10-09 14:45 ` Alex Williamson
2017-10-09 17:16 ` Pierre Morel
2017-10-10 9:35 ` Cornelia Huck
2017-10-10 16:01 ` Pierre Morel
2017-10-11 12:20 ` Cornelia Huck
2017-10-12 10:12 ` Pierre Morel
2017-10-12 14:48 ` Pierre Morel
2017-10-12 14:54 ` Cornelia Huck
2017-10-04 13:49 ` [Qemu-devel] [PATCH v1 5/5] s390x/intc: AIS is now always migratable Pierre Morel
2017-10-30 8:28 ` [Qemu-devel] [PATCH v1 0/5][RFC] Refactoring of AIS support Christian Borntraeger
2017-10-30 12:42 ` Cornelia Huck [this message]
2017-10-30 12:44 ` Christian Borntraeger
2017-10-30 13:44 ` Pierre Morel
2017-10-30 13:48 ` Christian Borntraeger
2017-10-30 14:02 ` Halil Pasic
2017-10-30 16:59 ` Cornelia Huck
2017-10-30 17:08 ` Christian Borntraeger
2017-10-30 17:38 ` Pierre Morel
2017-10-30 18:58 ` Halil Pasic
2017-11-06 8:52 ` Cornelia Huck
2017-11-06 8:54 ` Christian Borntraeger
2017-11-06 10:05 ` Pierre Morel
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=20171030134233.6aaa81a1.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=zyimin@linux.vnet.ibm.com \
/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.