From: Eric Auger <eric.auger@linaro.org>
To: Pavel Fedin <p.fedin@samsung.com>,
'Andre Przywara' <andre.przywara@arm.com>,
eric.auger@st.com
Cc: christoffer.dall@linaro.org,
'Marc Zyngier' <Marc.Zyngier@arm.com>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Subject: Re: [RFC 0/6] KVM: arm/arm64: gsi routing support
Date: Tue, 23 Jun 2015 09:50:10 +0200 [thread overview]
Message-ID: <55890FB2.2090609@linaro.org> (raw)
In-Reply-To: <052d01d0ad87$8a2a90e0$9e7fb2a0$@samsung.com>
Hi Pavel,
On 06/23/2015 09:38 AM, Pavel Fedin wrote:
> Hello!
>
>> What is done currently at qemu level for other archs - if I understand
>> it correctly - is there is static GSI routing for standard IRQ.
>
> Yes, this is correct. GSI number = SPI number for ARM. Also something similar for MIPS (haven't
> study that).
>
>> For MSI
>> irqfd setup they use spare gsi number not yet used for GSI routing < max
>> route number.
>
> No.
> On ARM with vGICv2m MSI data is effectively IRQ offset, with base being 32. So, original convention
> works without any change, they simply retrieve SPI number from MSI data and set up irqfd to that
> SPI. No allocation is done.
Yes on ARM we use gsi direct mapping feature. I was talking about what
is done without this "gsi direct mapping" feature. In that case the low
GSI numbers are used by irqchip routing entries. So kvm_irqchip_get_virq
returns a gsi beyond the irqchip routed gsi's.
Eric
> Allocation is done only on x86, with routing. They just allocate GSI numbers starting from zero and
> route them to something (either irqchip or MSI).
>
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
>
>
next prev parent reply other threads:[~2015-06-23 7:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 17:40 [RFC 0/6] KVM: arm/arm64: gsi routing support Eric Auger
2015-06-18 17:40 ` [RFC 1/6] KVM: api: add kvm_irq_routing_extended_msi Eric Auger
2015-06-22 16:32 ` Andre Przywara
2015-06-23 7:36 ` Eric Auger
2015-06-18 17:40 ` [RFC 2/6] KVM: kvm_host: add kvm_extended_msi Eric Auger
2015-06-18 17:40 ` [RFC 3/6] KVM: irqchip: convey devid to kvm_set_msi Eric Auger
2015-06-18 17:40 ` [RFC 4/6] KVM: arm/arm64: enable irqchip routing Eric Auger
2015-06-18 17:53 ` Marc Zyngier
2015-06-18 18:00 ` Eric Auger
2015-06-18 18:07 ` Marc Zyngier
2015-06-18 17:40 ` [RFC 5/6] KVM: arm/arm64: enable MSI routing Eric Auger
2015-06-18 17:40 ` [RFC 6/6] KVM: arm: implement kvm_set_msi by gsi direct mapping Eric Auger
2015-06-19 6:37 ` [RFC 0/6] KVM: arm/arm64: gsi routing support Pavel Fedin
2015-06-22 8:31 ` Eric Auger
2015-06-22 8:40 ` Andre Przywara
2015-06-22 9:21 ` Eric Auger
2015-06-23 7:38 ` Pavel Fedin
2015-06-23 7:50 ` Eric Auger [this message]
2015-06-23 8:50 ` Pavel Fedin
2015-06-23 9:44 ` Eric Auger
2015-06-23 9:03 ` Andre Przywara
2015-06-23 9:33 ` Eric Auger
2015-06-23 12:53 ` Eric Auger
2015-06-24 12:20 ` Pavel Fedin
2015-06-24 13:03 ` Eric Auger
2015-06-25 8:46 ` Pavel Fedin
2015-06-26 16:17 ` 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=55890FB2.2090609@linaro.org \
--to=eric.auger@linaro.org \
--cc=Marc.Zyngier@arm.com \
--cc=andre.przywara@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@st.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=p.fedin@samsung.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.