From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-17.9 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CBD18C433DB for ; Thu, 4 Feb 2021 14:42:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 98F5C64DFF for ; Thu, 4 Feb 2021 14:42:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236785AbhBDOmH (ORCPT ); Thu, 4 Feb 2021 09:42:07 -0500 Received: from mail.kernel.org ([198.145.29.99]:40470 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236850AbhBDOiN (ORCPT ); Thu, 4 Feb 2021 09:38:13 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 96D7A64F42; Thu, 4 Feb 2021 14:37:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1612449452; bh=eX/1xnMdBH58oq4Cm//d2eH7lZEj/ruuIIGGb0auhuU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=lFUg2MhCGRwGCnWckleg2a585Xz+UPVroJoNasl+l4uT0swGpvGoFDX9tZU3lQU8T /yrQSfPWtuDwynUHzXjcNMRmcL3Hpe9GUojzRx7oLBzcEMnuf5Fugs46AmSYNirHm0 GOMjZtv2zt6lmt5JUCXfTx3Ou8ZLooidFTn5ePcH+jLvp6JlcZ/wq3kED3EeiOTmV8 JEyrlU6Zy1/rze1wxKk2PST5LR1xrcY/gBK6mtU2kGkZssp+m9Yz6Ihgp+3PZWtUtX O386OeZwIL5OOsEzKkiZf9BK0SHUN10bysPQh3rGOM9NhwGiYRKNzb5RJWkLPFQzp3 CLQa41rKVOCfA== Date: Thu, 4 Feb 2021 14:37:26 +0000 From: Will Deacon To: Quentin Perret Cc: Catalin Marinas , Marc Zyngier , James Morse , Julien Thierry , Suzuki K Poulose , Rob Herring , Frank Rowand , devicetree@vger.kernel.org, android-kvm@google.com, linux-kernel@vger.kernel.org, kernel-team@android.com, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org, Fuad Tabba , Mark Rutland , David Brazdil Subject: Re: [RFC PATCH v2 26/26] KVM: arm64: Wrap the host with a stage 2 Message-ID: <20210204143725.GB20815@willie-the-truck> References: <20210108121524.656872-1-qperret@google.com> <20210108121524.656872-27-qperret@google.com> <20210203161146.GJ18974@willie-the-truck> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 04, 2021 at 02:26:35PM +0000, Quentin Perret wrote: > On Wednesday 03 Feb 2021 at 16:11:47 (+0000), Will Deacon wrote: > > On Fri, Jan 08, 2021 at 12:15:24PM +0000, Quentin Perret wrote: > > > When KVM runs in protected nVHE mode, make use of a stage 2 page-table > > > to give the hypervisor some control over the host memory accesses. At > > > the moment all memory aborts from the host will be instantly idmapped > > > RWX at stage 2 in a lazy fashion. Later patches will make use of that > > > infrastructure to implement access control restrictions to e.g. protect > > > guest memory from the host. > > > > > > Signed-off-by: Quentin Perret > > > --- > > > arch/arm64/include/asm/kvm_cpufeature.h | 2 + > > > arch/arm64/kernel/image-vars.h | 3 + > > > arch/arm64/kvm/hyp/include/nvhe/mem_protect.h | 33 +++ > > > arch/arm64/kvm/hyp/nvhe/Makefile | 2 +- > > > arch/arm64/kvm/hyp/nvhe/hyp-init.S | 1 + > > > arch/arm64/kvm/hyp/nvhe/hyp-main.c | 6 + > > > arch/arm64/kvm/hyp/nvhe/mem_protect.c | 191 ++++++++++++++++++ > > > arch/arm64/kvm/hyp/nvhe/setup.c | 6 + > > > arch/arm64/kvm/hyp/nvhe/switch.c | 7 +- > > > arch/arm64/kvm/hyp/nvhe/tlb.c | 4 +- > > > 10 files changed, 248 insertions(+), 7 deletions(-) > > > create mode 100644 arch/arm64/kvm/hyp/include/nvhe/mem_protect.h > > > create mode 100644 arch/arm64/kvm/hyp/nvhe/mem_protect.c > > > > [...] > > > > > +void handle_host_mem_abort(struct kvm_cpu_context *host_ctxt) > > > +{ > > > + enum kvm_pgtable_prot prot; > > > + u64 far, hpfar, esr, ipa; > > > + int ret; > > > + > > > + esr = read_sysreg_el2(SYS_ESR); > > > + if (!__get_fault_info(esr, &far, &hpfar)) > > > + hyp_panic(); > > > + > > > + prot = KVM_PGTABLE_PROT_R | KVM_PGTABLE_PROT_W | KVM_PGTABLE_PROT_X; > > > + ipa = (hpfar & HPFAR_MASK) << 8; > > > + ret = host_stage2_map(ipa, PAGE_SIZE, prot); > > > > Can we try to put down a block mapping if the whole thing falls within > > memory? > > Yes we can! And in fact we can do that outside of memory too. It's > queued for v3 already, so stay tuned ... :) Awesome! The Stage-2 TLB thanks you. Will From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-15.3 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 55127C433E0 for ; Thu, 4 Feb 2021 14:37:38 +0000 (UTC) Received: from mm01.cs.columbia.edu (mm01.cs.columbia.edu [128.59.11.253]) by mail.kernel.org (Postfix) with ESMTP id CBE1364F4D for ; Thu, 4 Feb 2021 14:37:37 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CBE1364F4D Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvmarm-bounces@lists.cs.columbia.edu Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 581A84B1C1; Thu, 4 Feb 2021 09:37:37 -0500 (EST) X-Virus-Scanned: at lists.cs.columbia.edu Authentication-Results: mm01.cs.columbia.edu (amavisd-new); dkim=softfail (fail, message has been altered) header.i=@kernel.org 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 MLjRanU-uiLY; Thu, 4 Feb 2021 09:37:36 -0500 (EST) Received: from mm01.cs.columbia.edu (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 3EAD34B1D0; Thu, 4 Feb 2021 09:37:36 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 641AB4B1A9 for ; Thu, 4 Feb 2021 09:37:34 -0500 (EST) X-Virus-Scanned: at lists.cs.columbia.edu 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 Aua0Pe6RupMm for ; Thu, 4 Feb 2021 09:37:33 -0500 (EST) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by mm01.cs.columbia.edu (Postfix) with ESMTPS id 580924B175 for ; Thu, 4 Feb 2021 09:37:33 -0500 (EST) Received: by mail.kernel.org (Postfix) with ESMTPSA id 96D7A64F42; Thu, 4 Feb 2021 14:37:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1612449452; bh=eX/1xnMdBH58oq4Cm//d2eH7lZEj/ruuIIGGb0auhuU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=lFUg2MhCGRwGCnWckleg2a585Xz+UPVroJoNasl+l4uT0swGpvGoFDX9tZU3lQU8T /yrQSfPWtuDwynUHzXjcNMRmcL3Hpe9GUojzRx7oLBzcEMnuf5Fugs46AmSYNirHm0 GOMjZtv2zt6lmt5JUCXfTx3Ou8ZLooidFTn5ePcH+jLvp6JlcZ/wq3kED3EeiOTmV8 JEyrlU6Zy1/rze1wxKk2PST5LR1xrcY/gBK6mtU2kGkZssp+m9Yz6Ihgp+3PZWtUtX O386OeZwIL5OOsEzKkiZf9BK0SHUN10bysPQh3rGOM9NhwGiYRKNzb5RJWkLPFQzp3 CLQa41rKVOCfA== Date: Thu, 4 Feb 2021 14:37:26 +0000 From: Will Deacon To: Quentin Perret Subject: Re: [RFC PATCH v2 26/26] KVM: arm64: Wrap the host with a stage 2 Message-ID: <20210204143725.GB20815@willie-the-truck> References: <20210108121524.656872-1-qperret@google.com> <20210108121524.656872-27-qperret@google.com> <20210203161146.GJ18974@willie-the-truck> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Cc: devicetree@vger.kernel.org, kernel-team@android.com, android-kvm@google.com, Catalin Marinas , Fuad Tabba , linux-kernel@vger.kernel.org, Rob Herring , linux-arm-kernel@lists.infradead.org, Marc Zyngier , Frank Rowand , kvmarm@lists.cs.columbia.edu X-BeenThere: kvmarm@lists.cs.columbia.edu X-Mailman-Version: 2.1.14 Precedence: list List-Id: Where KVM/ARM decisions are made List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu On Thu, Feb 04, 2021 at 02:26:35PM +0000, Quentin Perret wrote: > On Wednesday 03 Feb 2021 at 16:11:47 (+0000), Will Deacon wrote: > > On Fri, Jan 08, 2021 at 12:15:24PM +0000, Quentin Perret wrote: > > > When KVM runs in protected nVHE mode, make use of a stage 2 page-table > > > to give the hypervisor some control over the host memory accesses. At > > > the moment all memory aborts from the host will be instantly idmapped > > > RWX at stage 2 in a lazy fashion. Later patches will make use of that > > > infrastructure to implement access control restrictions to e.g. protect > > > guest memory from the host. > > > > > > Signed-off-by: Quentin Perret > > > --- > > > arch/arm64/include/asm/kvm_cpufeature.h | 2 + > > > arch/arm64/kernel/image-vars.h | 3 + > > > arch/arm64/kvm/hyp/include/nvhe/mem_protect.h | 33 +++ > > > arch/arm64/kvm/hyp/nvhe/Makefile | 2 +- > > > arch/arm64/kvm/hyp/nvhe/hyp-init.S | 1 + > > > arch/arm64/kvm/hyp/nvhe/hyp-main.c | 6 + > > > arch/arm64/kvm/hyp/nvhe/mem_protect.c | 191 ++++++++++++++++++ > > > arch/arm64/kvm/hyp/nvhe/setup.c | 6 + > > > arch/arm64/kvm/hyp/nvhe/switch.c | 7 +- > > > arch/arm64/kvm/hyp/nvhe/tlb.c | 4 +- > > > 10 files changed, 248 insertions(+), 7 deletions(-) > > > create mode 100644 arch/arm64/kvm/hyp/include/nvhe/mem_protect.h > > > create mode 100644 arch/arm64/kvm/hyp/nvhe/mem_protect.c > > > > [...] > > > > > +void handle_host_mem_abort(struct kvm_cpu_context *host_ctxt) > > > +{ > > > + enum kvm_pgtable_prot prot; > > > + u64 far, hpfar, esr, ipa; > > > + int ret; > > > + > > > + esr = read_sysreg_el2(SYS_ESR); > > > + if (!__get_fault_info(esr, &far, &hpfar)) > > > + hyp_panic(); > > > + > > > + prot = KVM_PGTABLE_PROT_R | KVM_PGTABLE_PROT_W | KVM_PGTABLE_PROT_X; > > > + ipa = (hpfar & HPFAR_MASK) << 8; > > > + ret = host_stage2_map(ipa, PAGE_SIZE, prot); > > > > Can we try to put down a block mapping if the whole thing falls within > > memory? > > Yes we can! And in fact we can do that outside of memory too. It's > queued for v3 already, so stay tuned ... :) Awesome! The Stage-2 TLB thanks you. Will _______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-15.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 74E0CC433E0 for ; Thu, 4 Feb 2021 14:38:36 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 2CDF764DDD for ; Thu, 4 Feb 2021 14:38:36 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2CDF764DDD Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=F1SsmffX1DgMd/exakRLWkhbbyxGjA3Z+PMv3buIGek=; b=vPqD1Lj44d/IHr1jPANppAoGc SwRc4zXZmymyj12elydatVn1uXANo6iMJ9jyK/ucW7jtchvW4zV36wJ0JKMUPvXQsy0jd3FLqk8lQ N1XnnOmEhtL49vn+im/hMN1jpOFG8VNbGJVhWmOsRTfw/7NRYLAfEVRvTmthNrUAJ9JEQbzxrxg8V sxBnNqjkKBAFoGBaColSEtSJnFVhEp7camI7hxz3gTL2CAvPvY+xfdbXvyehtOEXO6Cecw6zowaE9 XlynPOySUEm9C8MbymWAPjzyM1e3OQBCJNipydWK2eRCn5DMH6ECvhH+iDwpxt4GlQV9BUhKZBR7O HsqcFPw5g==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1l7flI-0003nl-62; Thu, 04 Feb 2021 14:37:36 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1l7flF-0003mZ-LQ for linux-arm-kernel@lists.infradead.org; Thu, 04 Feb 2021 14:37:34 +0000 Received: by mail.kernel.org (Postfix) with ESMTPSA id 96D7A64F42; Thu, 4 Feb 2021 14:37:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1612449452; bh=eX/1xnMdBH58oq4Cm//d2eH7lZEj/ruuIIGGb0auhuU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=lFUg2MhCGRwGCnWckleg2a585Xz+UPVroJoNasl+l4uT0swGpvGoFDX9tZU3lQU8T /yrQSfPWtuDwynUHzXjcNMRmcL3Hpe9GUojzRx7oLBzcEMnuf5Fugs46AmSYNirHm0 GOMjZtv2zt6lmt5JUCXfTx3Ou8ZLooidFTn5ePcH+jLvp6JlcZ/wq3kED3EeiOTmV8 JEyrlU6Zy1/rze1wxKk2PST5LR1xrcY/gBK6mtU2kGkZssp+m9Yz6Ihgp+3PZWtUtX O386OeZwIL5OOsEzKkiZf9BK0SHUN10bysPQh3rGOM9NhwGiYRKNzb5RJWkLPFQzp3 CLQa41rKVOCfA== Date: Thu, 4 Feb 2021 14:37:26 +0000 From: Will Deacon To: Quentin Perret Subject: Re: [RFC PATCH v2 26/26] KVM: arm64: Wrap the host with a stage 2 Message-ID: <20210204143725.GB20815@willie-the-truck> References: <20210108121524.656872-1-qperret@google.com> <20210108121524.656872-27-qperret@google.com> <20210203161146.GJ18974@willie-the-truck> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210204_093733_829117_4289A2F8 X-CRM114-Status: GOOD ( 20.30 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , devicetree@vger.kernel.org, kernel-team@android.com, Suzuki K Poulose , android-kvm@google.com, Catalin Marinas , Fuad Tabba , linux-kernel@vger.kernel.org, Rob Herring , James Morse , linux-arm-kernel@lists.infradead.org, Marc Zyngier , David Brazdil , Frank Rowand , kvmarm@lists.cs.columbia.edu, Julien Thierry Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Feb 04, 2021 at 02:26:35PM +0000, Quentin Perret wrote: > On Wednesday 03 Feb 2021 at 16:11:47 (+0000), Will Deacon wrote: > > On Fri, Jan 08, 2021 at 12:15:24PM +0000, Quentin Perret wrote: > > > When KVM runs in protected nVHE mode, make use of a stage 2 page-table > > > to give the hypervisor some control over the host memory accesses. At > > > the moment all memory aborts from the host will be instantly idmapped > > > RWX at stage 2 in a lazy fashion. Later patches will make use of that > > > infrastructure to implement access control restrictions to e.g. protect > > > guest memory from the host. > > > > > > Signed-off-by: Quentin Perret > > > --- > > > arch/arm64/include/asm/kvm_cpufeature.h | 2 + > > > arch/arm64/kernel/image-vars.h | 3 + > > > arch/arm64/kvm/hyp/include/nvhe/mem_protect.h | 33 +++ > > > arch/arm64/kvm/hyp/nvhe/Makefile | 2 +- > > > arch/arm64/kvm/hyp/nvhe/hyp-init.S | 1 + > > > arch/arm64/kvm/hyp/nvhe/hyp-main.c | 6 + > > > arch/arm64/kvm/hyp/nvhe/mem_protect.c | 191 ++++++++++++++++++ > > > arch/arm64/kvm/hyp/nvhe/setup.c | 6 + > > > arch/arm64/kvm/hyp/nvhe/switch.c | 7 +- > > > arch/arm64/kvm/hyp/nvhe/tlb.c | 4 +- > > > 10 files changed, 248 insertions(+), 7 deletions(-) > > > create mode 100644 arch/arm64/kvm/hyp/include/nvhe/mem_protect.h > > > create mode 100644 arch/arm64/kvm/hyp/nvhe/mem_protect.c > > > > [...] > > > > > +void handle_host_mem_abort(struct kvm_cpu_context *host_ctxt) > > > +{ > > > + enum kvm_pgtable_prot prot; > > > + u64 far, hpfar, esr, ipa; > > > + int ret; > > > + > > > + esr = read_sysreg_el2(SYS_ESR); > > > + if (!__get_fault_info(esr, &far, &hpfar)) > > > + hyp_panic(); > > > + > > > + prot = KVM_PGTABLE_PROT_R | KVM_PGTABLE_PROT_W | KVM_PGTABLE_PROT_X; > > > + ipa = (hpfar & HPFAR_MASK) << 8; > > > + ret = host_stage2_map(ipa, PAGE_SIZE, prot); > > > > Can we try to put down a block mapping if the whole thing falls within > > memory? > > Yes we can! And in fact we can do that outside of memory too. It's > queued for v3 already, so stay tuned ... :) Awesome! The Stage-2 TLB thanks you. Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel