From: Pavel Fedin <p.fedin@samsung.com>
To: 'Marc Zyngier' <marc.zyngier@arm.com>,
'Eric Auger' <eric.auger@linaro.org>,
'Andre Przywara' <Andre.Przywara@arm.com>,
christoffer.dall@linaro.org
Cc: kvm@vger.kernel.org
Subject: RE: IRQFD support with GICv3 ITS (WAS: RE: [PATCH 00/13] arm64: KVM: GICv3 ITS emulation)
Date: Wed, 17 Jun 2015 13:00:13 +0300 [thread overview]
Message-ID: <014301d0a8e4$683db9f0$38b92dd0$@samsung.com> (raw)
In-Reply-To: <55813F2A.9060102@arm.com>
Hello!
> Hmmm. You may not have noticed it, but we're actually all are quite busy
> at the moment (hint, we're at -rc8, and the next merge window is about
> to open).
Ok ok, i do not mind of course. :) Just i expected at least some, quick reply. It's like
talking to a person while he/she suddenly starts ignoring you and turns away without any
ACK/NAK. I simply do not know what is wrong.
> This feels just wrong. The LPI number is under complete control of the
> guest, and can be changed at any time. You can never rely on it to be
> stable.
Heh... Then i'm afraid the only option is the second one: GSI routing. It would allow to
associate an irqfd with MSI bunch (data + address + devID) as it is.
I'm also currently busy with some strange vhost-net performance issues, so i'll make
another RFC later, after i redo my implementation using routing.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-06-17 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 8:31 IRQFD support with GICv3 ITS (WAS: RE: [PATCH 00/13] arm64: KVM: GICv3 ITS emulation) Pavel Fedin
2015-06-10 8:31 ` Pavel Fedin
2015-06-10 13:58 ` Eric Auger
2015-06-10 13:58 ` Eric Auger
2015-06-10 15:30 ` Pavel Fedin
2015-06-10 15:30 ` Pavel Fedin
2015-06-17 9:21 ` Pavel Fedin
2015-06-17 9:34 ` Marc Zyngier
2015-06-17 10:00 ` Pavel Fedin [this message]
2015-06-17 11:02 ` Andre Przywara
2015-06-17 11:46 ` Pavel Fedin
2015-06-18 6:35 ` Eric Auger
2015-06-18 14:19 ` Pavel Fedin
2015-06-10 15:38 ` Pavel Fedin
2015-06-10 15:38 ` Pavel Fedin
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='014301d0a8e4$683db9f0$38b92dd0$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=Andre.Przywara@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@linaro.org \
--cc=kvm@vger.kernel.org \
--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 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.