public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Marc Zyngier <marc.zyngier@arm.com>, 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
Subject: Re: [PATCH V1 0/7] Enable ACPI support for ARM KVM GIC
Date: Mon, 8 Feb 2016 16:39:46 +0000	[thread overview]
Message-ID: <56B8C4D2.3070702@arm.com> (raw)
In-Reply-To: <56B866FD.4070104@arm.com>

Hi,

On 08/02/16 09:59, Marc Zyngier wrote:
> On 05/02/16 17:07, Wei Huang wrote:
>> 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.

I've been working on a patch series which rely on the GIC and arch timer 
drivers to get the necessary information to initialize the different KVM 
components (vGIC + vtimer).

I think this achieves the goal you have in mind. I will post the series 
in a few minutes.

Regards,

-- 
Julien Grall

  parent reply	other threads:[~2016-02-08 16:39 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 ` [PATCH V1 0/7] Enable ACPI support for ARM KVM GIC Marc Zyngier
2016-02-08 16:35   ` Wei Huang
2016-02-08 16:42     ` Marc Zyngier
2016-02-08 16:39   ` Julien Grall [this message]
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=56B8C4D2.3070702@arm.com \
    --to=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=marc.zyngier@arm.com \
    --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