From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Zyngier Subject: Re: [PATCH v4 21/32] arm64: KVM: Build system integration Date: Tue, 21 May 2013 17:14:07 +0100 Message-ID: <519B9D4F.9030308@arm.com> References: <1368540840-26750-1-git-send-email-marc.zyngier@arm.com> <1368540840-26750-22-git-send-email-marc.zyngier@arm.com> <20130521154227.GM27002@arm.com> <850310439.5245685.1369152587054.JavaMail.root@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Catalin Marinas , "linux-arm-kernel@lists.infradead.org" , "kvmarm@lists.cs.columbia.edu" , "kvm@vger.kernel.org" , Will Deacon , "gleb@redhat.com" , Christopher Covington To: Paolo Bonzini Return-path: Received: from service87.mimecast.com ([91.220.42.44]:43004 "EHLO service87.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754272Ab3EUQOM convert rfc822-to-8bit (ORCPT ); Tue, 21 May 2013 12:14:12 -0400 In-Reply-To: <850310439.5245685.1369152587054.JavaMail.root@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 21/05/13 17:09, Paolo Bonzini wrote: >=20 >=20 > ----- Messaggio originale ----- >> Da: "Catalin Marinas" >> A: "Marc Zyngier" >> Cc: linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.e= du, kvm@vger.kernel.org, "Will Deacon" >> , pbonzini@redhat.com, gleb@redhat.com, "Christ= opher Covington" >> Inviato: Marted=C3=AC, 21 maggio 2013 17:42:27 >> Oggetto: Re: [PATCH v4 21/32] arm64: KVM: Build system integration >> >> On Tue, May 14, 2013 at 03:13:49PM +0100, Marc Zyngier wrote: >>> --- /dev/null >>> +++ b/arch/arm64/kvm/Kconfig >> ... >>> +config KVM_ARM_VGIC >>> + bool >>> + depends on KVM_ARM_HOST && OF >>> + select HAVE_KVM_IRQCHIP >>> + ---help--- >>> + Adds support for a hardware assisted, in-kernel GIC emulation. >>> + >>> +config KVM_ARM_TIMER >>> + bool >>> + depends on KVM_ARM_VGIC >>> + select HAVE_KVM_IRQCHIP >>> + ---help--- >>> + Adds support for the Architected Timers in virtual machines >>> + >>> +source drivers/virtio/Kconfig >> >> Shouldn't the above configs go to drivers/virtio/Kconfig as well (or >> drivers/virtio/arm/Kconfig)? >=20 > virtio doesn't mean "virtual versions of devices that also exist in > hardware"; those are indeed in arch/ARCH/kvm. virtio is a specific b= us > for paravirtualized devices. It is not KVM-specific and the code run= s > in the guest (whereas arch/arm64/kvm/Kconfig is host code). >=20 > That said, drivers/virtio/Kconfig is already sourced by drivers/Kconf= ig. > Why do you need to source it again here? Probably some brain fart on my side. I'll get rid of it. Thanks, M. --=20 Jazz is not dead. It just smells funny...