All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Christoffer Dall <christoffer.dall@linaro.org>,
	Pavel Fedin <p.fedin@samsung.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Marc Zyngier <Marc.Zyngier@arm.com>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [PATCH 0/3] KVM: arm: Implement software vGICv2 emulation
Date: Mon, 29 Jun 2015 15:11:10 +0100	[thread overview]
Message-ID: <559151FE.8020701@arm.com> (raw)
In-Reply-To: <20150629125213.GK11332@cbox>

Hi,

On 29/06/15 13:52, Christoffer Dall wrote:
> Hi Pavel,
> 
> [Please cc the kvm/arm list for such patches according to the
> MAINTAINERS file in the future]
> 
> On Mon, Jun 29, 2015 at 12:53:46PM +0300, Pavel Fedin wrote:
>> Some hardware (like Raspberry Pi 2) is capable of running KVM, however lacks
>> functional vGIC registers. This series introduces software vGIC emulation for
>> such machines, allowing to fully use virtualization capabilities
> 
> Is this rather esoteric use case really worth the extra code in the
> kernel? 

I wonder if these patches would pave the way to support running GICv2
guests on GICv3s without compat support? Admittedly not a really
compelling use case either, but at least worth discussing, I think.

Also if this will make the hack needed to enable KVM on RPi2 smaller,
I'd rather embrace this one than letting any random hacks appear on that
RPi kernel tree (patches which I have seen already on some other repo).
If I get this correctly, there are some efforts currently to get closer
to mainline with the RPi tree.

Pavel, is this "broken" GIC you are talking about going to appear in a
publicly available SoC? If yes, you could either state this right now or
send it later once you can talk publicly.

Marc, Christoffer:
So is this GICv2 CPU interface emulation totally out of question for us
or is it worth at least commenting on the patches?

Cheers,
Andre.

> I really feel that pure emulation should happen in userspace
> unless there's a very good reason for doing it in the kernel, such as a
> clearly measureable difference in performance, etc.
> 
> I would much rather see a version of this where a userspace provided GIC
> works with the in-kernel arch timers support.
> 
> -Christoffer
> 

  reply	other threads:[~2015-06-29 14:11 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
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 [this message]
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=559151FE.8020701@arm.com \
    --to=andre.przywara@arm.com \
    --cc=Marc.Zyngier@arm.com \
    --cc=christoffer.dall@linaro.org \
    --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.