All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Quentin Perret <qperret@google.com>, Fuad Tabba <tabba@google.com>
Cc: catalin.marinas@arm.com, will@kernel.org, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v4 4/4] KVM: arm64: Clean up kvm makefiles
Date: Mon, 04 May 2020 16:27:09 +0100	[thread overview]
Message-ID: <654f7d7260004e4959f0d0bd31800ac2@kernel.org> (raw)
In-Reply-To: <20200504132648.GA65651@google.com>

Hi all,

On 2020-05-04 14:26, Quentin Perret wrote:
> Hi Fuad,
> 
> On Tuesday 21 Apr 2020 at 14:17:34 (+0100), Fuad Tabba wrote:
>> Consolidate references to the CONFIG_KVM configuration item to 
>> encompass
>> entire folders rather than per line.
>> 
>> Signed-off-by: Fuad Tabba <tabba@google.com>
>> ---
>>  arch/arm64/kvm/Makefile     | 40 
>> ++++++++++++-------------------------
>>  arch/arm64/kvm/hyp/Makefile | 15 ++++----------
>>  2 files changed, 17 insertions(+), 38 deletions(-)
>> 
>> diff --git a/arch/arm64/kvm/Makefile b/arch/arm64/kvm/Makefile
>> index 419696e615b3..5354ca1b1bfb 100644
>> --- a/arch/arm64/kvm/Makefile
>> +++ b/arch/arm64/kvm/Makefile
>> @@ -10,30 +10,16 @@ KVM=../../../virt/kvm
>>  obj-$(CONFIG_KVM) += kvm.o
>>  obj-$(CONFIG_KVM) += hyp/
>> 
>> -kvm-$(CONFIG_KVM) += $(KVM)/kvm_main.o $(KVM)/coalesced_mmio.o
>> -kvm-$(CONFIG_KVM) += $(KVM)/eventfd.o $(KVM)/vfio.o $(KVM)/irqchip.o
>> -kvm-$(CONFIG_KVM) += arm.o mmu.o mmio.o
>> -kvm-$(CONFIG_KVM) += psci.o perf.o
>> -kvm-$(CONFIG_KVM) += hypercalls.o
>> -kvm-$(CONFIG_KVM) += pvtime.o
>> -
>> -kvm-$(CONFIG_KVM) += inject_fault.o regmap.o va_layout.o
>> -kvm-$(CONFIG_KVM) += hyp.o hyp-init.o handle_exit.o
>> -kvm-$(CONFIG_KVM) += guest.o debug.o reset.o sys_regs.o 
>> sys_regs_generic_v8.o
>> -kvm-$(CONFIG_KVM) += vgic-sys-reg-v3.o fpsimd.o pmu.o
>> -kvm-$(CONFIG_KVM) += aarch32.o
>> -kvm-$(CONFIG_KVM) += arch_timer.o
>> -kvm-$(CONFIG_KVM_ARM_PMU)  += pmu-emul.o
>> -
>> -kvm-$(CONFIG_KVM) += vgic/vgic.o
>> -kvm-$(CONFIG_KVM) += vgic/vgic-init.o
>> -kvm-$(CONFIG_KVM) += vgic/vgic-irqfd.o
>> -kvm-$(CONFIG_KVM) += vgic/vgic-v2.o
>> -kvm-$(CONFIG_KVM) += vgic/vgic-v3.o
>> -kvm-$(CONFIG_KVM) += vgic/vgic-v4.o
>> -kvm-$(CONFIG_KVM) += vgic/vgic-mmio.o
>> -kvm-$(CONFIG_KVM) += vgic/vgic-mmio-v2.o
>> -kvm-$(CONFIG_KVM) += vgic/vgic-mmio-v3.o
>> -kvm-$(CONFIG_KVM) += vgic/vgic-kvm-device.o
>> -kvm-$(CONFIG_KVM) += vgic/vgic-its.o
>> -kvm-$(CONFIG_KVM) += vgic/vgic-debug.o
>> +kvm-y := $(KVM)/kvm_main.o $(KVM)/coalesced_mmio.o $(KVM)/eventfd.o \
>> +	 $(KVM)/vfio.o $(KVM)/irqchip.o \
>> +	 arm.o mmu.o mmio.o psci.o perf.o hypercalls.o pvtime.o \
>> +	 inject_fault.o regmap.o va_layout.o hyp.o hyp-init.o handle_exit.o 
>> \
>> +	 guest.o debug.o reset.o sys_regs.o sys_regs_generic_v8.o \
>> +	 vgic-sys-reg-v3.o fpsimd.o pmu.o pmu-emul.o \
> 
> Should we keep pmu-emul.o conditional on CONFIG_KVM_ARM_PMU?

Good point. KVM_ARM_PMU depends on HW_PERF_EVENTS, which depends
on ARM_PMU. Without the above condition being present, you can
try and build the kernel with the KVM PMU emulation, and not
the host CPU PMU. It stops building very quickly.

I guess we should clean this up now that 32 bit is gone. But
for the sake of this series, it would be better to keep the
dependency in place and sort out the PMU mess at a later stage.

Thanks,

        M.
-- 
Jazz is not dead. It just smells funny...
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

  reply	other threads:[~2020-05-04 15:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 13:17 [PATCH v4 0/4] KVM: arm64: Tidy up arch Kconfig and Makefiles Fuad Tabba
2020-04-21 13:17 ` [PATCH v4 1/4] KVM: arm64: Kill off CONFIG_KVM_ARM_HOST Fuad Tabba
2020-05-01  9:16   ` Suzuki K Poulose
2020-04-21 13:17 ` [PATCH v4 2/4] KVM: arm64: Update help text Fuad Tabba
2020-05-01  8:56   ` Suzuki K Poulose
2020-04-21 13:17 ` [PATCH v4 3/4] KVM: arm64: Change CONFIG_KVM to a menuconfig entry Fuad Tabba
2020-05-01  9:18   ` Suzuki K Poulose
2020-04-21 13:17 ` [PATCH v4 4/4] KVM: arm64: Clean up kvm makefiles Fuad Tabba
2020-04-30 20:25   ` Will Deacon
2020-05-04 13:26   ` Quentin Perret
2020-05-04 15:27     ` Marc Zyngier [this message]
2020-05-04 15:29       ` Fuad Tabba

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=654f7d7260004e4959f0d0bd31800ac2@kernel.org \
    --to=maz@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=qperret@google.com \
    --cc=tabba@google.com \
    --cc=will@kernel.org \
    /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.