From: Arnd Bergmann <arnd@arndb.de>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, marc.zyngier@arm.com
Subject: Re: [GIT PULL 3/6] KVM: arm: use GIC support unconditionally
Date: Wed, 21 Oct 2015 16:15:43 +0200 [thread overview]
Message-ID: <3759605.BfhMCn7jyL@wuerfel> (raw)
In-Reply-To: <20151021135844.GB13488@cbox>
On Wednesday 21 October 2015 15:58:44 Christoffer Dall wrote:
> On Wed, Oct 21, 2015 at 03:45:20PM +0200, Arnd Bergmann wrote:
> > On Tuesday 20 October 2015 15:51:05 Paolo Bonzini wrote:
> > > Should this be "select" or "depends on"? Not a blocker, can always be fixed in 4.4.
> >
> > We have lots of 'select ARM_GIC' in the tree for platforms that use one, using
> > 'depends on' will limit KVM support to being available only if at least one
> > of them is being used.
> >
> > The only platform I can think of that uses ARMv7ve without actually having
> > a GIC is BCM2836 (Raspberry Pi 2). Can we actually run KVM on a platform
> > like that? If so, 'depends on' might be better, otherwise let's stay with
> > 'select'.
>
> Yes you can, just without the VGIC and the timer - you have to emulate
> that in userspace. Samsung also has a broken platform where they
> integrated things incorrectly, so you cannot use the VGIC, but that
> platform support is out of tree, so I can't see if it uses the GIC in
> general or not.
Ok, my patch should be fine then.
> I'm a bit confused why using 'depends on' in this case helps anythign?
>
> (I know, I suck at dealing with the config system)
Generally speaking, 'select' causes more problems than 'depends on',
in particular when you get conflicting requirements (A selects B,
B depends on C, but A can be enabled without C).
However, symbols that only have 'select' and no 'depends on', and also
are not user-visible, are not problematic. This is the case here.
Arnd
next prev parent reply other threads:[~2015-10-21 14:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 16:19 [GIT PULL 0/6] A handful of fixes for KVM/ARM for v4.3-rc7 Christoffer Dall
2015-10-20 16:19 ` [GIT PULL 1/6] KVM: arm/arm64: Do not inject spurious interrupts Christoffer Dall
2015-10-20 16:19 ` [GIT PULL 2/6] KVM: arm/arm64: Fix memory leak if timer initialization fails Christoffer Dall
2015-10-20 16:19 ` [GIT PULL 3/6] KVM: arm: use GIC support unconditionally Christoffer Dall
2015-10-20 19:51 ` Paolo Bonzini
2015-10-21 13:20 ` Christoffer Dall
2015-10-21 13:45 ` Arnd Bergmann
2015-10-21 13:58 ` Christoffer Dall
2015-10-21 14:15 ` Arnd Bergmann [this message]
2015-10-21 14:50 ` Pavel Fedin
2015-10-20 16:19 ` [GIT PULL 4/6] arm/arm64: KVM: Fix arch timer behavior for disabled interrupts Christoffer Dall
2015-10-20 16:19 ` [GIT PULL 5/6] arm/arm64: KVM: Clear map->active on pend/active clear Christoffer Dall
2015-10-20 16:19 ` [GIT PULL 6/6] arm/arm64: KVM: Fix disabled distributor operation Christoffer Dall
2015-10-21 15:47 ` [GIT PULL 0/6] A handful of fixes for KVM/ARM for v4.3-rc7 Paolo Bonzini
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=3759605.BfhMCn7jyL@wuerfel \
--to=arnd@arndb.de \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox