From: Pavel Fedin <p.fedin@samsung.com>
To: 'Cornelia Huck' <cornelia.huck@de.ibm.com>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
'Marc Zyngier' <marc.zyngier@arm.com>,
'Christoffer Dall' <christoffer.dall@linaro.org>,
'Gleb Natapov' <gleb@kernel.org>,
'Paolo Bonzini' <pbonzini@redhat.com>
Subject: RE: [PATCH v5 2/2] KVM: Make KVM_CAP_IRQFD dependent on KVM_CAP_IRQCHIP
Date: Mon, 30 Nov 2015 17:45:18 +0300 [thread overview]
Message-ID: <019e01d12b7d$bc084520$3418cf60$@samsung.com> (raw)
In-Reply-To: <20151130153807.1a2668e5.cornelia.huck@de.ibm.com>
Hello!
> > b) I simply drop it as it is, because current qemu knows about the dependency and does not
> try to use irqfd without irqchip,
> > because there's simply no use for them. But, well, perhaps there would be an exception in
> vhost, i don't remember testing it.
>
> Wouldn't an irqfd emulation cover vhost?
Of course it would. At least it should, but perhaps will need some minor tweaks.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-11-30 14:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 9:40 [PATCH v5 0/2] KVM: arm/arm64: Allow to use KVM without in-kernel irqchip Pavel Fedin
2015-11-30 9:40 ` [PATCH v5 1/2] arm/arm64: KVM: Detect vGIC presence at runtime Pavel Fedin
2016-04-21 21:41 ` Alexander Graf
2016-04-21 22:04 ` Peter Maydell
2016-04-21 22:35 ` Alexander Graf
2016-04-21 22:41 ` Peter Maydell
2016-04-22 7:50 ` Marc Zyngier
2015-11-30 9:40 ` [PATCH v5 2/2] KVM: Make KVM_CAP_IRQFD dependent on KVM_CAP_IRQCHIP Pavel Fedin
2015-11-30 11:26 ` Cornelia Huck
2015-11-30 11:56 ` Pavel Fedin
2015-11-30 12:13 ` Cornelia Huck
2015-11-30 12:41 ` Pavel Fedin
2015-11-30 14:38 ` Cornelia Huck
2015-11-30 14:45 ` Pavel Fedin [this message]
2015-12-01 11:07 ` Pavel Fedin
2015-12-01 16:00 ` Paolo Bonzini
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='019e01d12b7d$bc084520$3418cf60$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=christoffer.dall@linaro.org \
--cc=cornelia.huck@de.ibm.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.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 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).