From: Pavel Fedin <p.fedin@samsung.com>
To: 'Andre Przywara' <andre.przywara@arm.com>,
'Christoffer Dall' <christoffer.dall@linaro.org>
Cc: 'Marc Zyngier' <Marc.Zyngier@arm.com>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Subject: RE: [PATCH 0/3] KVM: arm: Implement software vGICv2 emulation
Date: Tue, 30 Jun 2015 11:16:03 +0300 [thread overview]
Message-ID: <01c601d0b30d$01cad080$05607180$@samsung.com> (raw)
In-Reply-To: <559151FE.8020701@arm.com>
Hello!
> I wonder if these patches would pave the way to support running GICv2
> guests on GICv3s without compat support?
Yes, it does. I haven't implemented GICv3 bit for this time, but - yes. And it will be a very small
addition.
> Pavel, is this "broken" GIC you are talking about going to appear in a
> publicly available SoC?
In kernel documentation it's known as "FrankenGIC".
First of all, it's Exynos 4 (however i don't know whether it implements virtualization extensions).
Second, it is present in many consumer electronics products (does this count as "publicly
available"? But you can learn this fact from Samsung's opensource releases). I use one of these
boards for my tests because we have lots of them here :)
Third, this code doesn't really depend on hardware GIC, and can be reused on RPi-2 with a little
more hacking.
Fourth, there is at least of one ARM64 machine with broken vGICv3. And you can buy it. I have it
here. And it would also benefit from this code (yes, with GICv3 CPU interface emulation added, which
becomes trivial).
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
prev parent reply other threads:[~2015-06-30 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1435567226.git.p.fedin@samsung.com>
[not found] ` <20150629125213.GK11332@cbox>
2015-06-29 14:11 ` [PATCH 0/3] KVM: arm: Implement software vGICv2 emulation Andre Przywara
2015-06-29 14:15 ` Christoffer Dall
2015-06-29 15:29 ` Marc Zyngier
2015-06-30 8:16 ` Pavel Fedin [this message]
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='01c601d0b30d$01cad080$05607180$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=Marc.Zyngier@arm.com \
--cc=andre.przywara@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
/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).