linux-kernel - Re: [PATCH v5 0/9] arm64: Add support for KVM with ACPI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160406172805.GJ8961@cbox>
Date:	Wed, 6 Apr 2016 19:28:05 +0200
From:	Christoffer Dall <christoffer.dall@...aro.org>
To:	Julien Grall <julien.grall@....com>
Cc:	kvmarm@...ts.cs.columbia.edu, marc.zyngier@....com,
	fu.wei@...aro.org, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	wei@...hat.com, al.stone@...aro.org, gg@...mlogic.co.uk,
	daniel.lezcano@...aro.org
Subject: Re: [PATCH v5 0/9] arm64: Add support for KVM with ACPI

On Mon, Apr 04, 2016 at 12:37:31PM +0100, 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-#6 are merged via the irqchip tree
> 2) Patches #7-#8 are merge via the KVM tree
> 3) Patch #9 is merged via the clocksource tree.
> 

I'm not a clocksource or irqchip expert, and far from an ACPI expert,
but this series overall looks good to me now.

I guess we'll need to wait until the patches are in the clocksource and
irqchip trees, and then merge that into the kvmarm tree, and apply patch
7 and 8 on top, or is there a simpler way to do this?

Thanks,
-Christoffer