From: Eric Auger <eric.auger@linaro.org>
To: Alexander Graf <agraf@suse.de>,
Antonios Motakis <a.motakis@virtualopensystems.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
Marc Zyngier <marc.zyngier@arm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: Coupling between KVM_IRQFD and KVM_SET_GSI_ROUTING?
Date: Thu, 19 Jun 2014 16:02:46 +0200 [thread overview]
Message-ID: <53A2ED86.5040507@linaro.org> (raw)
In-Reply-To: <53A0290B.8040301@linaro.org>
Hi,
If I am not wrong I did not get any reply to this question. Can anyone
share his/her experience/knowledge on this gsi routing/irqfd use case?
Thank you in advance
Best Regards
Eric
On 06/17/2014 01:39 PM, Eric Auger wrote:
> Hello,
>
> I have a question related to KVM_IRQFD and KVM_SET_GSI_ROUTING ioctl
> relationship.
>
> When reading the KVM API documentation I do not understand there is any
> dependency between KVM_IRQFD and KVM_SET_GSI_ROUTING. According to the
> text it seems only the gsi field is used and interpreted as the irqchip pin.
>
> However irqchip.c kvm_set_irq code relies on an existing and not dummy
> routing table.
>
> My question is: does anyone agree on the fact the user-side must set a
> consistent routing table using KVM_SET_GSI_ROUTING before using
> KVM_IRQFD? The other alternative would have been to build a default
> identity GSI routing table in the kernel (gsi = irqchip.pin).
>
> In the positive, shouldn't we clarify the KVM API documentation?
>
> Thank you in advance
>
> Best Regards
>
> Eric
>
next prev parent reply other threads:[~2014-06-19 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 11:39 Coupling between KVM_IRQFD and KVM_SET_GSI_ROUTING? Eric Auger
2014-06-19 14:02 ` Eric Auger [this message]
2014-06-23 16:47 ` Alexander Graf
2014-06-24 9:47 ` Paul Mackerras
2014-06-24 10:40 ` Alexander Graf
2014-06-24 15:05 ` Eric Auger
2014-06-24 15:47 ` Alexander Graf
2014-06-24 16:11 ` Eric Auger
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=53A2ED86.5040507@linaro.org \
--to=eric.auger@linaro.org \
--cc=a.motakis@virtualopensystems.com \
--cc=agraf@suse.de \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.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).