From: Marc Zyngier <marc.zyngier@arm.com>
To: Wei Huang <wei@redhat.com>, kvmarm@lists.cs.columbia.edu
Cc: christoffer.dall@linaro.org, kvm@vger.kernel.org,
hanjun.guo@linaro.org, fu.wei@linaro.org, drjones@redhat.com,
al.stone@linaro.org, Julien Grall <Julien.Grall@arm.com>
Subject: Re: [PATCH V1 0/7] Enable ACPI support for ARM KVM GIC
Date: Mon, 8 Feb 2016 09:59:25 +0000 [thread overview]
Message-ID: <56B866FD.4070104@arm.com> (raw)
In-Reply-To: <1454692054-8984-1-git-send-email-wei@redhat.com>
Wei,
On 05/02/16 17:07, Wei Huang wrote:
> This patch set enables ACPI support for KVM GIC. Note that the patches
> are in fact the V3 of previously submitted patches (search "Enable ACPI
> support for KVM ARM"). But because Fu Wei includes the arch_timer part
> in his series [1] and I have substantially re-written the GIC code in this
> revision, the version number is reset to v1.
>
> By following Marc's prior comments, the main design idea is to let DT or
> ACPI code to fill out the "struct vgic_params" which are extended to
> include all GIC related info.
I think you misread the comments I gave back in June (!), where I said:
<quote>
[...]
Simply making available a global structure containing the base addresses
and interrupt should be enough, and could be shared with both DT and
ACPI. You could start your series by letting both GIC drivers expose
that information obtained through DT, convert KVM to use this structure,
and later on let ACPI fill in this structure too.
> Anyway the difficulty is to find a common place to store and share info
> between other modules & KVM.
Indeed. As a rule of thumb, I want to minimize the amount of gratuitous
divergence between DT and ACPI. So the sooner we extract the required
information from whatever firmware we have, the better.
</quote>
>
> [1] https://lkml.org/lkml/2016/2/1/658
>
> Thanks,
> -Wei
>
> Wei Huang (7):
> KVM: GIC: Move GIC DT probing code to GICv2 and GICv3 files
> KVM: GIC: Add extra fields to store GICH and GICV resource info
> KVM: GIC: Create a common probe function for GIC
> KVM: GICv2: Extract the common code from DT
> KVM: GICv2: Add ACPI probing function
> KVM: GICv3: Extract the common code from DT
> KVM: GICv3: Add ACPI probing function
>
> include/kvm/arm_vgic.h | 14 ++--
> virt/kvm/arm/vgic-v2-emul.c | 4 +-
> virt/kvm/arm/vgic-v2.c | 186 +++++++++++++++++++++++++++++++++-----------
> virt/kvm/arm/vgic-v3.c | 159 ++++++++++++++++++++++++++++---------
> virt/kvm/arm/vgic.c | 22 +-----
> 5 files changed, 277 insertions(+), 108 deletions(-)
>
So when I see this diffstat and the patches that follow, I cannot help
but think that we do have a disconnect here. You do add a bunch of ACPI
probing in KVM, to which I've already said no.
I want to see the probing code in the GIC drivers, exported through a
common structure that KVM can then use. That's it. Nothing else.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2016-02-08 9:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 17:07 [PATCH V1 0/7] Enable ACPI support for ARM KVM GIC Wei Huang
2016-02-05 17:07 ` [PATCH V1 1/7] KVM: GIC: Move GIC DT probing code to GICv2 and GICv3 files Wei Huang
2016-02-05 17:07 ` [PATCH V1 2/7] KVM: GIC: Add extra fields to store GICH and GICV resource info Wei Huang
2016-02-05 17:07 ` [PATCH V1 3/7] KVM: GIC: Create a common probe function for GIC Wei Huang
2016-02-05 17:07 ` [PATCH V1 4/7] KVM: GICv2: Extract the common code from DT Wei Huang
2016-02-05 17:07 ` [PATCH V1 5/7] KVM: GICv2: Add ACPI probing function Wei Huang
2016-02-05 17:07 ` [PATCH V1 6/7] KVM: GICv3: Extract the common code from DT Wei Huang
2016-02-05 17:07 ` [PATCH V1 7/7] KVM: GICv3: Add ACPI probing function Wei Huang
2016-02-08 9:59 ` Marc Zyngier [this message]
2016-02-08 16:35 ` [PATCH V1 0/7] Enable ACPI support for ARM KVM GIC Wei Huang
2016-02-08 16:42 ` Marc Zyngier
2016-02-08 16:39 ` Julien Grall
2016-02-08 16:47 ` Wei Huang
2016-02-08 16:56 ` Marc Zyngier
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=56B866FD.4070104@arm.com \
--to=marc.zyngier@arm.com \
--cc=Julien.Grall@arm.com \
--cc=al.stone@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=drjones@redhat.com \
--cc=fu.wei@linaro.org \
--cc=hanjun.guo@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=wei@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