Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1390151 > unrolled thread

Re: [PATCH v6 00/10] arm64: Add support for KVM with ACPI

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v6 00/10] arm64: Add support for KVM with ACPI Marc Zyngier <marc.zyngier@arm.com> - 2016-04-28 15:20 +0200
    Re: [PATCH v6 00/10] arm64: Add support for KVM with ACPI Jason Cooper <jason@lakedaemon.net> - 2016-05-02 15:20 +0200
      Re: [PATCH v6 00/10] arm64: Add support for KVM with ACPI Christoffer Dall <christoffer.dall@linaro.org> - 2016-05-03 10:30 +0200
        Re: [PATCH v6 00/10] arm64: Add support for KVM with ACPI Jason Cooper <jason@lakedaemon.net> - 2016-05-03 14:50 +0200

#1390151 — Re: [PATCH v6 00/10] arm64: Add support for KVM with ACPI

[+ Thomas, Jason]

Do you have any objection against this going through the KVM tree? The
dependencies are rather intricate, and Daniel gave us his green light
already for the clocksource part.

If you'd rather maintain the usual flow, please let us know and we'll
deal with it.

Thanks,

	M.

On 11/04/16 16:32, Julien Grall wrote:
> Hello,
> 
> This patch series allows KVM to work with ACPI on ARM64.
> 
> Currently, the firmware tables are parsed by the the virtual timer and virtual
> GIC code in order to configure them correctly.
> 
> However the parsing of these tables is already done in the GIC and arch timer
> drivers. This patch series introduces new helpers to retrieve the information
> from the different drivers in order to avoid duplication of the parsing code.
> 
> To make the merge easier via the different trees, each patch modifies a single
> subsystem. The suggested plan to merge the series is divided in 3 steps:
> 
> 1) Patches #1-#2 are merged via the clocksource tree
>    Patches #2-#7 are merged via the irqchip tree
> 2) Patches #8-#9 are merge via the KVM tree
> 3) Patch #10 is merged via the clocksource tree.
> 
> For all the changes see in each patch.
> 
> Regards,
> 
> 
> Julien Grall (10):
>   clocksource: arm_arch_timer: Gather KVM specific information in a
>     structure
>   clocksource: arm_arch_timer: Extend arch_timer_kvm_info to get the
>     virtual IRQ
>   irqchip/gic-v2: Gather ACPI specific data in a single structure
>   irqchip/gic-v2: Parse and export virtual GIC information
>   irqchip/gic-v3: Prefix all pr_* messages by "GICv3: "
>   irqchip/gic-v3: Gather all ACPI specific data in a single structure
>   irqchip/gic-v3: Parse and export virtual GIC information
>   KVM: arm/arm64: arch_timer: Rely on the arch timer to parse the
>     firmware tables
>   KVM: arm/arm64: vgic: Rely on the GIC driver to parse the firmware
>     tables
>   clocksource: arm_arch_timer: Remove arch_timer_get_timecounter
> 
>  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           | 176 +++++++++++++++++++++++++++------
>  drivers/irqchip/irq-gic.c              |  87 +++++++++++++++-
>  include/clocksource/arm_arch_timer.h   |  12 +--
>  include/kvm/arm_vgic.h                 |   7 +-
>  include/linux/irqchip/arm-gic-common.h |  34 +++++++
>  virt/kvm/arm/arch_timer.c              |  40 +++-----
>  virt/kvm/arm/vgic-v2.c                 |  61 +++++-------
>  virt/kvm/arm/vgic-v3.c                 |  47 +++------
>  virt/kvm/arm/vgic.c                    |  50 +++++-----
>  12 files changed, 377 insertions(+), 164 deletions(-)
>  create mode 100644 include/linux/irqchip/arm-gic-common.h
> 


-- 
Jazz is not dead. It just smells funny...

[toc] | [next] | [standalone]

#1392207

On Thu, Apr 28, 2016 at 02:13:23PM +0100, Marc Zyngier wrote:
> [+ Thomas, Jason]
> 
> Do you have any objection against this going through the KVM tree? The
> dependencies are rather intricate, and Daniel gave us his green light
> already for the clocksource part.
> 
> If you'd rather maintain the usual flow, please let us know and we'll
> deal with it.

I've no objection.

Acked-by: Jason Cooper <jason@lakedaemon.net>

thx,

Jason.

[toc] | [prev] | [next] | [standalone]

#1393170

On Mon, May 02, 2016 at 12:54:14PM +0000, Jason Cooper wrote:
> On Thu, Apr 28, 2016 at 02:13:23PM +0100, Marc Zyngier wrote:
> > [+ Thomas, Jason]
> > 
> > Do you have any objection against this going through the KVM tree? The
> > dependencies are rather intricate, and Daniel gave us his green light
> > already for the clocksource part.
> > 
> > If you'd rather maintain the usual flow, please let us know and we'll
> > deal with it.
> 
> I've no objection.
> 
> Acked-by: Jason Cooper <jason@lakedaemon.net>
> 
Just to be clear, that's on all the irqchip patches, right?

Thanks!
-Christoffer

[toc] | [prev] | [next] | [standalone]

#1393393

On Tue, May 03, 2016 at 10:21:24AM +0200, Christoffer Dall wrote:
> On Mon, May 02, 2016 at 12:54:14PM +0000, Jason Cooper wrote:
> > On Thu, Apr 28, 2016 at 02:13:23PM +0100, Marc Zyngier wrote:
> > > [+ Thomas, Jason]
> > > 
> > > Do you have any objection against this going through the KVM tree? The
> > > dependencies are rather intricate, and Daniel gave us his green light
> > > already for the clocksource part.
> > > 
> > > If you'd rather maintain the usual flow, please let us know and we'll
> > > deal with it.
> > 
> > I've no objection.
> > 
> > Acked-by: Jason Cooper <jason@lakedaemon.net>
> > 
> Just to be clear, that's on all the irqchip patches, right?

Correct.

thx,

Jason.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web