From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoffer Dall Subject: Re: [PATCH v5 0/9] arm64: Add support for KVM with ACPI Date: Wed, 6 Apr 2016 19:28:05 +0200 Message-ID: <20160406172805.GJ8961@cbox> References: <1459769860-6629-1-git-send-email-julien.grall@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 8C54C40B40 for ; Wed, 6 Apr 2016 13:26:34 -0400 (EDT) Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aiRIxS8bLXvf for ; Wed, 6 Apr 2016 13:26:33 -0400 (EDT) Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by mm01.cs.columbia.edu (Postfix) with ESMTPS id 93AED409A2 for ; Wed, 6 Apr 2016 13:26:33 -0400 (EDT) Received: by mail-wm0-f49.google.com with SMTP id u206so55236668wme.1 for ; Wed, 06 Apr 2016 10:27:55 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1459769860-6629-1-git-send-email-julien.grall@arm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu To: Julien Grall Cc: al.stone@linaro.org, kvm@vger.kernel.org, marc.zyngier@arm.com, daniel.lezcano@linaro.org, linux-kernel@vger.kernel.org, fu.wei@linaro.org, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org, gg@slimlogic.co.uk List-Id: kvmarm@lists.cs.columbia.edu 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