Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932920AbcDNQDa (ORCPT ); Thu, 14 Apr 2016 12:03:30 -0400 Received: from mail-wm0-f48.google.com ([74.125.82.48]:37311 "EHLO mail-wm0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932394AbcDNQD2 (ORCPT ); Thu, 14 Apr 2016 12:03:28 -0400 Date: Thu, 14 Apr 2016 18:03:48 +0200 From: Christoffer Dall To: Suzuki K Poulose Cc: linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org, marc.zyngier@arm.com, mark.rutland@arm.com, will.deacon@arm.com, catalin.marinas@arm.com, linux-kernel@vger.kernel.org, kvmarm@lists.cs.columbia.edu Subject: Re: [PATCH v2 00/17] kvm-arm: Add stage2 page table walker Message-ID: <20160414160348.GQ30804@cbox> References: <1460640065-27658-1-git-send-email-suzuki.poulose@arm.com> <570F9B32.9090106@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <570F9B32.9090106@arm.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1276 Lines: 32 On Thu, Apr 14, 2016 at 02:29:22PM +0100, Suzuki K Poulose wrote: > On 14/04/16 14:20, Suzuki K Poulose wrote: > >This series adds support for stage2 page table helpers and makes > >the core kvm-arm MMU code make use of it. At the moment we assume > >that the host/hyp and the stage2 page tables have same number of > >levels and hence use the host level accessors (except for some > >hooks, e.g kvm_p.d_addr_end) and shares the routines for unmapping > >the page table ranges. > > >The tree is available at : > > git://linux-arm.org/linux-skp.git kvm-stage2/v2 > > Please note that the tree above contains one additional patch on top of kvmarm/master : > commit 91ad0db16a42a7d3("arm64/sunxi: 4.6-rc1: Add dependency on generic irq chip"), > which is there to fix a build break with ARCH_SUNXI selected on 4.6-rc1. > ok, but I can just build/test this without ARCH_SUNXI and pick the remains of this series only for kvmarm/next, as far as I can tell, right? Marc, seems like you're happy with this series as well? Will/Catalin: How do we attack this for the arm64 specific parts? Do you want to ack this patches and I queue this as a whole or do you want to apply patches 1, 2, and 3 and provide me a stable branch that I can base this on? Thanks, -Christoffer