From: Wei Huang <wei@redhat.com>
To: Julien Grall <julien.grall@arm.com>, kvmarm@lists.cs.columbia.edu
Cc: christoffer.dall@linaro.org, marc.zyngier@arm.com,
fu.wei@linaro.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, al.stone@linaro.org
Subject: Re: [PATCH v2 0/6] arm64: Add support of KVM with ACPI
Date: Fri, 19 Feb 2016 00:36:15 -0600 [thread overview]
Message-ID: <56C6B7DF.4090606@redhat.com> (raw)
In-Reply-To: <1455204804-31830-1-git-send-email-julien.grall@arm.com>
On 02/11/2016 09:33 AM, Julien Grall wrote:
> Hello,
>
> This small series allows an ARM64 ACPI based platform to use KVM.
>
> Currently the KVM code has to parse the firmware table to get the necessary
> information to setup the virtual timer and virtual GIC.
>
> However the parsing of those tables are already done in the GIC and arch
> timer drivers.
>
> This patch series introduces different helpers to retrieve the information
> from different drivers avoiding to duplicate the parsing code.
>
> Note there is patch series ([1] and [2]) adding support of KVM on ACPI,
> although the approach chosen is completely different. The code to parse
> the firmware tables are duplicated which I think make more complex to
> support new firmware tables.
I backported these patches to my internal tree. It booted on an ARM64
machine. Even though I haven't got the chance to test it on an GICv3
machine (will update later), I think you can add my name as Tested-by if
needed.
-Wei
>
> See the changes since v1 in the different patches.
>
> Regards,
>
> [1] https://lists.cs.columbia.edu/pipermail/kvmarm/2016-February/018482.html
> [2] https://lists.cs.columbia.edu/pipermail/kvmarm/2016-February/018355.html
>
> Julien Grall (6):
> KVM: arm/arm64: arch_timer: Gather KVM specific information in a
> structure
> KVM: arm/arm64: arch_timer: Rely on the arch timer to parse the
> firmware tables
> irqchip/gic-v2: Gather ACPI specific data in a single structure
> irqchip/gic-v2: Parse and export virtual GIC information
> irqchip/gic-v3: Parse and export virtual GIC information
> KVM: arm/arm64: vgic: Rely on the GIC driver to parse the firmware
> tables
>
> drivers/clocksource/arm_arch_timer.c | 11 ++--
> drivers/irqchip/irq-gic-common.c | 13 +++++
> drivers/irqchip/irq-gic-common.h | 3 ++
> drivers/irqchip/irq-gic-v3.c | 36 ++++++++++++++
> drivers/irqchip/irq-gic.c | 91 ++++++++++++++++++++++++++++++++--
> include/clocksource/arm_arch_timer.h | 13 ++---
> include/kvm/arm_vgic.h | 7 +--
> include/linux/irqchip/arm-gic-common.h | 34 +++++++++++++
> virt/kvm/arm/arch_timer.c | 39 ++++-----------
> virt/kvm/arm/vgic-v2.c | 67 +++++++++----------------
> virt/kvm/arm/vgic-v3.c | 45 +++++------------
> virt/kvm/arm/vgic.c | 50 ++++++++++---------
> 12 files changed, 264 insertions(+), 145 deletions(-)
> create mode 100644 include/linux/irqchip/arm-gic-common.h
>
next prev parent reply other threads:[~2016-02-19 6:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 15:33 [PATCH v2 0/6] arm64: Add support of KVM with ACPI Julien Grall
2016-02-11 15:33 ` [PATCH v2 1/6] KVM: arm/arm64: arch_timer: Gather KVM specific information in a structure Julien Grall
2016-02-19 7:24 ` Wei Huang
2016-02-19 10:53 ` Julien Grall
2016-02-19 11:41 ` Julien Grall
2016-02-19 11:54 ` Marc Zyngier
2016-02-11 15:33 ` [PATCH v2 2/6] KVM: arm/arm64: arch_timer: Rely on the arch timer to parse the firmware tables Julien Grall
2016-03-03 19:38 ` Christoffer Dall
2016-03-04 10:32 ` Julien Grall
2016-02-11 15:33 ` [PATCH v2 3/6] irqchip/gic-v2: Gather ACPI specific data in a single structure Julien Grall
2016-02-11 15:33 ` [PATCH v2 4/6] irqchip/gic-v2: Parse and export virtual GIC information Julien Grall
2016-02-11 15:33 ` [PATCH v2 5/6] irqchip/gic-v3: " Julien Grall
2016-02-11 15:33 ` [PATCH v2 6/6] KVM: arm/arm64: vgic: Rely on the GIC driver to parse the firmware tables Julien Grall
2016-02-19 6:36 ` Wei Huang [this message]
2016-02-23 2:31 ` [PATCH v2 0/6] arm64: Add support of KVM with ACPI Huang Shijie
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=56C6B7DF.4090606@redhat.com \
--to=wei@redhat.com \
--cc=al.stone@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=fu.wei@linaro.org \
--cc=julien.grall@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.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;
as well as URLs for NNTP newsgroup(s).