From: Pavel Fedin <p.fedin@samsung.com>
To: 'Marc Zyngier' <marc.zyngier@arm.com>, kvm@vger.kernel.org
Cc: 'Christoffer Dall' <christoffer.dall@linaro.org>,
'Andre Przywara' <andre.przywara@arm.com>
Subject: RE: [PATCH 3/3] KVM: arm: Enable vGICv2 software emulation
Date: Mon, 29 Jun 2015 15:37:17 +0300 [thread overview]
Message-ID: <050501d0b268$56097e30$021c7a90$@samsung.com> (raw)
In-Reply-To: <55913758.4020805@arm.com>
Hello!
> Hold on a second. In your cover letter, your saying "RPi-2". The RPi-2
> doesn't have a GIC at all, so I'd really like to know *how* you end-up
> in the GICv2 probe function?
I'm not on RPi-2. I am on some Samsung's proprietary hardware which suffers from this problem.
Actually it has "weird GIC", similar to Exynos-4 (every CPU accesses GIC at its own base), thus
hardware vGIC is unusable.
I learned about RPi-2 when i was discussing some related things earlier with Andre over private
mail and we suggested that it could be useful there.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-06-29 12:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 9:53 [PATCH 0/3] KVM: arm: Implement software vGICv2 emulation Pavel Fedin
2015-06-29 9:53 ` [PATCH 1/3] KVM: arm: Add basic infrastructure for software vGIC emulation Pavel Fedin
2015-06-29 9:53 ` [PATCH 2/3] KVM: arm: Introduce software emulation of vGICv2 CPU interface Pavel Fedin
2015-06-29 9:53 ` [PATCH 3/3] KVM: arm: Enable vGICv2 software emulation Pavel Fedin
2015-06-29 12:17 ` Marc Zyngier
2015-06-29 12:37 ` Pavel Fedin [this message]
2015-06-29 12:48 ` Marc Zyngier
2015-06-29 12:13 ` [PATCH 0/3] KVM: arm: Implement software vGICv2 emulation Marc Zyngier
2015-06-29 12:52 ` Christoffer Dall
2015-06-29 14:11 ` Andre Przywara
2015-06-29 14:15 ` Christoffer Dall
2015-06-29 15:29 ` Marc Zyngier
2015-06-30 8:16 ` 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='050501d0b268$56097e30$021c7a90$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=andre.przywara@arm.com \
--cc=christoffer.dall@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.