Message ID | 20221219102452.2860088-1-sumit.garg@linaro.org |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:e747:0:0:0:0:0 with SMTP id c7csp2311828wrn; Mon, 19 Dec 2022 02:40:33 -0800 (PST) X-Google-Smtp-Source: AMrXdXt9TRVYH2a+R0GcqIltZV1GIqejfc1B6KBSmuKsSYjiitAII+k1VGEpWXpZWAM0Ty6dbOM/ X-Received: by 2002:a05:6a20:7a8a:b0:ac:31c7:9d7 with SMTP id u10-20020a056a207a8a00b000ac31c709d7mr10316243pzh.52.1671446433247; Mon, 19 Dec 2022 02:40:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1671446433; cv=none; d=google.com; s=arc-20160816; b=EHKbmMxXzA8MpejaQKZX2etO61bZ0uP2XfHyLqLZqJ51hutOr+fHMei9IQ9436jEsB p/WNYWI/ZjCpKV+58q3W7e/HmnuKfHDPPakJe0HrhnRG0LmcD/mqNvJCB2eGtSpx3rWv q2FNmPsvc044ZRIxwp7KOyaFCe6U8wkQztKvmgKDclFXkb3l6LG97csSB5KB3Gj1uRTL rlO9Gja1KxKTLpngLDhmwSlE9G71i/aNWXuw1WxQSvj9vjLDBtm1c8gxEzNQbfkvqkdW 1WlqLvocl3hquD6VZWfNGAKrFk5hEltk/xdEYcRaXDnCQY4TWr4DpqGnZUpsfBax7hG+ 7gNA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=K37gbY5Dl8sWIrBCYlNI70CebPhvB+1SPLpodhsI8Ls=; b=UcIdrPwWTS6FIqsaI9/3/NXFJVw9BsIbNgJfsOwUtjR5XoWpeO1pdn3NkMsgytRxyc W5oSPBQa4743sUkDpzSALAm37ridQzX1xRVdtd+813StBeyFod9Csn1mF7pHtOiVTDBM ai5KPhQzryl7x/4AE3EjEO9j7anyki+I5PJMLM/nonf44D/W2WNSbH/LFe6I3Pk4kI8E 5y03g02mgFj8hNjgJqqMpeZbFxbCbZV716AXe9NrqT+PiKCpyGqwyg4SdpMSfGyAwWYm 9Rm4duON4jMh4DoD0RuKYWJVgSDqgl1fsTakbv+pWpIxCsoavXVqeMdzDxpcSC+IMguQ Pqng== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=DcGzl2I7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k11-20020aa788cb000000b00557eeba9fa4si11219839pff.91.2022.12.19.02.40.20; Mon, 19 Dec 2022 02:40:33 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=DcGzl2I7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231693AbiLSKZI (ORCPT <rfc822;peekingduck44@gmail.com> + 99 others); Mon, 19 Dec 2022 05:25:08 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41042 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231419AbiLSKZG (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 19 Dec 2022 05:25:06 -0500 Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4FAA5DF8A for <linux-kernel@vger.kernel.org>; Mon, 19 Dec 2022 02:25:04 -0800 (PST) Received: by mail-pj1-x102d.google.com with SMTP id z8-20020a17090abd8800b00219ed30ce47so12506056pjr.3 for <linux-kernel@vger.kernel.org>; Mon, 19 Dec 2022 02:25:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=K37gbY5Dl8sWIrBCYlNI70CebPhvB+1SPLpodhsI8Ls=; b=DcGzl2I7MILyelixxwuz25J4rmnqa0G05scGyE3bfVtF35zCpUdcXHKrHcTbkPtiWj uPESG1PUqJ5wcR/57uEmhY7NnCFerUH6JMg/H6cFqtGuoMb6/cpmtXsW/VgER7a879Ni x2a+GxGWSNfheBBY6goh9bbjNVlsgw8eADhqbtPJuWoO5n2XJHBY0OwhzmQla2/bXL76 Gj7FY+puAIgDNJvZkf9JNFhUFIyIHYMhdo4ldIOOYXQkIJNaM4zJrGf8f0SQtmmynCPC gfDgQYf/qsupgOQIBlO33r10WosIT/5HDtvC/2985dDY446pjpfDDOufQcjr5kGNCHyg 0RTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=K37gbY5Dl8sWIrBCYlNI70CebPhvB+1SPLpodhsI8Ls=; b=5lhiFAfyghUg8wEO4c41R/bJzwD51PdfMMplkSddEzDWt7xKjt2GegdrjevjNWHxfh rA54IEaN6xB/+96WpTC6f3bTEGATicWP/W8rZynyIUN0OzRq/ChqJ3q2Ku1+cXqWhu8Y D31CLGHd38mPrhIUhFOMJm0ns+C0tkyNG7qKH9V1PHLZh3M6/8TDwrTiiTrHwq5Qd2Kj 8m4NAdf5UlKVrfLUiFZh75lV0Nu6GPqg7JxsNkjhJuhCJd+Z18NDo58DJOYV0R+ahSWs IxRZB2aO/fMTNNYX1jtFlG76dSL9LUKAwcrA6COEwsv/4mBla+spdWJhqiWm/453X4t+ 1PDA== X-Gm-Message-State: AFqh2krwGDfziPFuIU4/LZ6nlCZmdYHerzttrsJrF3uAEsOWt2vfBQdf keq6tcFOc7h6YAQQCXhnhjsJtw== X-Received: by 2002:a17:90a:6acd:b0:221:684a:d05d with SMTP id b13-20020a17090a6acd00b00221684ad05dmr9251001pjm.45.1671445503842; Mon, 19 Dec 2022 02:25:03 -0800 (PST) Received: from sumit-X1.. ([223.178.213.5]) by smtp.gmail.com with ESMTPSA id 89-20020a17090a0fe200b0020087d7e778sm8832731pjz.37.2022.12.19.02.25.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 19 Dec 2022 02:25:03 -0800 (PST) From: Sumit Garg <sumit.garg@linaro.org> To: will@kernel.org, catalin.marinas@arm.com, mark.rutland@arm.com, daniel.thompson@linaro.org, dianders@chromium.org Cc: liwei391@huawei.com, mhiramat@kernel.org, maz@kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Sumit Garg <sumit.garg@linaro.org> Subject: [PATCH v5 0/2] arm64: Fix pending single-step debugging issues Date: Mon, 19 Dec 2022 15:54:50 +0530 Message-Id: <20221219102452.2860088-1-sumit.garg@linaro.org> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1752638615175181724?= X-GMAIL-MSGID: =?utf-8?q?1752638615175181724?= |
Series |
arm64: Fix pending single-step debugging issues
|
|
Message
Sumit Garg
Dec. 19, 2022, 10:24 a.m. UTC
This patch-set reworks pending fixes from Wei's series [1] to make single-step debugging via kgdb/kdb on arm64 work as expected. There was a prior discussion on ML [2] regarding if we should keep the interrupts enabled during single-stepping. So patch #1 follows suggestion from Will [3] to not disable interrupts during single stepping but rather skip single stepping within interrupt handler. [1] https://lore.kernel.org/all/20200509214159.19680-1-liwei391@huawei.com/ [2] https://lore.kernel.org/all/CAD=FV=Voyfq3Qz0T3RY+aYWYJ0utdH=P_AweB=13rcV8GDBeyQ@mail.gmail.com/ [3] https://lore.kernel.org/all/20200626095551.GA9312@willie-the-truck/ Changes in v5: - Incorporated misc. comments from Mark. Changes in v4: - Rebased to the tip of mainline. - Picked up Doug's Tested-by tag. Changes in v3: - Reword commit descriptions as per Daniel's suggestions. Changes in v2: - Replace patch #1 to rather follow Will's suggestion. Sumit Garg (2): arm64: entry: Skip single stepping into interrupt handlers arm64: kgdb: Set PSTATE.SS to 1 to re-enable single-step arch/arm64/include/asm/debug-monitors.h | 1 + arch/arm64/kernel/debug-monitors.c | 5 +++++ arch/arm64/kernel/entry-common.c | 22 ++++++++++++++++++++-- arch/arm64/kernel/kgdb.c | 2 ++ 4 files changed, 28 insertions(+), 2 deletions(-)
Comments
Hi Will, Catalin, On Mon, 19 Dec 2022 at 15:55, Sumit Garg <sumit.garg@linaro.org> wrote: > > This patch-set reworks pending fixes from Wei's series [1] to make > single-step debugging via kgdb/kdb on arm64 work as expected. There was > a prior discussion on ML [2] regarding if we should keep the interrupts > enabled during single-stepping. So patch #1 follows suggestion from Will > [3] to not disable interrupts during single stepping but rather skip > single stepping within interrupt handler. > > [1] https://lore.kernel.org/all/20200509214159.19680-1-liwei391@huawei.com/ > [2] https://lore.kernel.org/all/CAD=FV=Voyfq3Qz0T3RY+aYWYJ0utdH=P_AweB=13rcV8GDBeyQ@mail.gmail.com/ > [3] https://lore.kernel.org/all/20200626095551.GA9312@willie-the-truck/ > > Changes in v5: > - Incorporated misc. comments from Mark. > Since patch #1 has already been reviewed/acked by Mark and the complete patchset has been tested by Doug, would it be fine for you to pick up this patchset? It fixes a real single stepping problem for kgdb on arm64. -Sumit > Changes in v4: > - Rebased to the tip of mainline. > - Picked up Doug's Tested-by tag. > > Changes in v3: > - Reword commit descriptions as per Daniel's suggestions. > > Changes in v2: > - Replace patch #1 to rather follow Will's suggestion. > > Sumit Garg (2): > arm64: entry: Skip single stepping into interrupt handlers > arm64: kgdb: Set PSTATE.SS to 1 to re-enable single-step > > arch/arm64/include/asm/debug-monitors.h | 1 + > arch/arm64/kernel/debug-monitors.c | 5 +++++ > arch/arm64/kernel/entry-common.c | 22 ++++++++++++++++++++-- > arch/arm64/kernel/kgdb.c | 2 ++ > 4 files changed, 28 insertions(+), 2 deletions(-) > > -- > 2.34.1 >
On Thu, Jan 12, 2023 at 02:52:49PM +0530, Sumit Garg wrote: > Hi Will, Catalin, > > On Mon, 19 Dec 2022 at 15:55, Sumit Garg <sumit.garg@linaro.org> wrote: > > > > This patch-set reworks pending fixes from Wei's series [1] to make > > single-step debugging via kgdb/kdb on arm64 work as expected. There was > > a prior discussion on ML [2] regarding if we should keep the interrupts > > enabled during single-stepping. So patch #1 follows suggestion from Will > > [3] to not disable interrupts during single stepping but rather skip > > single stepping within interrupt handler. > > > > [1] https://lore.kernel.org/all/20200509214159.19680-1-liwei391@huawei.com/ > > [2] https://lore.kernel.org/all/CAD=FV=Voyfq3Qz0T3RY+aYWYJ0utdH=P_AweB=13rcV8GDBeyQ@mail.gmail.com/ > > [3] https://lore.kernel.org/all/20200626095551.GA9312@willie-the-truck/ > > > > Changes in v5: > > - Incorporated misc. comments from Mark. > > > > Since patch #1 has already been reviewed/acked by Mark and the > complete patchset has been tested by Doug, would it be fine for you to > pick up this patchset? It fixes a real single stepping problem for > kgdb on arm64. Sorry to be quiet for so long. Testing this patch set has proven to be a little difficult. It certainly fixes the single step tests in the kgdbtest suite. That's a good start. Unfortunately when testing using qemu/KVM (hosted on NXP 2k/Solidrun Honeycomb) the patch set is resulting in instability running the built-in self tests (specifically this one: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/misc/kgdbts.c#n74 ). Running this test using the kgdbtest harness results in the test failing roughly a third of the time. The error reported is that the trap handler tried to unlock a spinlock that isn't currently locked. To be honest I suspect this is a generic problem that the new feature happens to tickle (this test has historically been unreliable on x86 too... and x86 is noteworthy for being the only other platform I test using KVM rather than pure qemu). Of course the only way to prove that would be to find and fix the problem in the trap handler (which probably involves rewriting it) and I haven't managed to do that yet. In short, I think the debugger is more useful with this patchset than without so, although it is caveated by the above, I'd call this: Acked-by: Daniel Thompson <daniel.thompson@linaro.org> Tested-by: Daniel Thompson <daniel.thompson@linaro.org> Daniel.
Hi, Is this expected to change single-stepping operation in usespace for debuggers (gdb/lldb)? If so, it would be nice to at least test it a little to make sure it works. On 1/24/23 18:04, Daniel Thompson wrote: > On Thu, Jan 12, 2023 at 02:52:49PM +0530, Sumit Garg wrote: >> Hi Will, Catalin, >> >> On Mon, 19 Dec 2022 at 15:55, Sumit Garg <sumit.garg@linaro.org> wrote: >>> >>> This patch-set reworks pending fixes from Wei's series [1] to make >>> single-step debugging via kgdb/kdb on arm64 work as expected. There was >>> a prior discussion on ML [2] regarding if we should keep the interrupts >>> enabled during single-stepping. So patch #1 follows suggestion from Will >>> [3] to not disable interrupts during single stepping but rather skip >>> single stepping within interrupt handler. >>> >>> [1] https://lore.kernel.org/all/20200509214159.19680-1-liwei391@huawei.com/ >>> [2] https://lore.kernel.org/all/CAD=FV=Voyfq3Qz0T3RY+aYWYJ0utdH=P_AweB=13rcV8GDBeyQ@mail.gmail.com/ >>> [3] https://lore.kernel.org/all/20200626095551.GA9312@willie-the-truck/ >>> >>> Changes in v5: >>> - Incorporated misc. comments from Mark. >>> >> >> Since patch #1 has already been reviewed/acked by Mark and the >> complete patchset has been tested by Doug, would it be fine for you to >> pick up this patchset? It fixes a real single stepping problem for >> kgdb on arm64. > > Sorry to be quiet for so long. > > Testing this patch set has proven to be a little difficult. > > It certainly fixes the single step tests in the kgdbtest suite. > That's a good start. > > Unfortunately when testing using qemu/KVM (hosted on NXP > 2k/Solidrun Honeycomb) the patch set is resulting in instability > running the built-in self tests (specifically this one: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/misc/kgdbts.c#n74 ). Running this test using the kgdbtest harness > results in the test failing roughly a third of the time. > > The error reported is that the trap handler tried to unlock a spinlock > that isn't currently locked. To be honest I suspect this is a generic > problem that the new feature happens to tickle (this test has > historically been unreliable on x86 too... and x86 is noteworthy for > being the only other platform I test using KVM rather than pure qemu). > Of course the only way to prove that would be to find and fix the > problem in the trap handler (which probably involves rewriting it) and I > haven't managed to do that yet. > > In short, I think the debugger is more useful with this patchset than > without so, although it is caveated by the above, I'd call this: > > Acked-by: Daniel Thompson <daniel.thompson@linaro.org> > Tested-by: Daniel Thompson <daniel.thompson@linaro.org> > > > Daniel. > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
On Tue, 24 Jan 2023 at 23:34, Daniel Thompson <daniel.thompson@linaro.org> wrote: > > On Thu, Jan 12, 2023 at 02:52:49PM +0530, Sumit Garg wrote: > > Hi Will, Catalin, > > > > On Mon, 19 Dec 2022 at 15:55, Sumit Garg <sumit.garg@linaro.org> wrote: > > > > > > This patch-set reworks pending fixes from Wei's series [1] to make > > > single-step debugging via kgdb/kdb on arm64 work as expected. There was > > > a prior discussion on ML [2] regarding if we should keep the interrupts > > > enabled during single-stepping. So patch #1 follows suggestion from Will > > > [3] to not disable interrupts during single stepping but rather skip > > > single stepping within interrupt handler. > > > > > > [1] https://lore.kernel.org/all/20200509214159.19680-1-liwei391@huawei.com/ > > > [2] https://lore.kernel.org/all/CAD=FV=Voyfq3Qz0T3RY+aYWYJ0utdH=P_AweB=13rcV8GDBeyQ@mail.gmail.com/ > > > [3] https://lore.kernel.org/all/20200626095551.GA9312@willie-the-truck/ > > > > > > Changes in v5: > > > - Incorporated misc. comments from Mark. > > > > > > > Since patch #1 has already been reviewed/acked by Mark and the > > complete patchset has been tested by Doug, would it be fine for you to > > pick up this patchset? It fixes a real single stepping problem for > > kgdb on arm64. > > Sorry to be quiet for so long. > > Testing this patch set has proven to be a little difficult. > > It certainly fixes the single step tests in the kgdbtest suite. > That's a good start. > > Unfortunately when testing using qemu/KVM (hosted on NXP > 2k/Solidrun Honeycomb) the patch set is resulting in instability > running the built-in self tests (specifically this one: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/misc/kgdbts.c#n74 ). Running this test using the kgdbtest harness > results in the test failing roughly a third of the time. > > The error reported is that the trap handler tried to unlock a spinlock > that isn't currently locked. To be honest I suspect this is a generic > problem that the new feature happens to tickle (this test has > historically been unreliable on x86 too... and x86 is noteworthy for > being the only other platform I test using KVM rather than pure qemu). > Of course the only way to prove that would be to find and fix the > problem in the trap handler (which probably involves rewriting it) and I > haven't managed to do that yet. > > In short, I think the debugger is more useful with this patchset than > without so, although it is caveated by the above, I'd call this: > > Acked-by: Daniel Thompson <daniel.thompson@linaro.org> > Tested-by: Daniel Thompson <daniel.thompson@linaro.org> > Thanks Daniel for the in-depth testing. -Sumit > > Daniel.
Hi Luis, On Wed, 25 Jan 2023 at 14:48, Luis Machado <luis.machado@arm.com> wrote: > > Hi, > > Is this expected to change single-stepping operation in usespace for debuggers (gdb/lldb)? No it won't affect user-space debuggers as we are only touching the interrupt path in EL1 mode. -Sumit > If so, it would be nice to at least > test it a little to make sure it works. > > On 1/24/23 18:04, Daniel Thompson wrote: > > On Thu, Jan 12, 2023 at 02:52:49PM +0530, Sumit Garg wrote: > >> Hi Will, Catalin, > >> > >> On Mon, 19 Dec 2022 at 15:55, Sumit Garg <sumit.garg@linaro.org> wrote: > >>> > >>> This patch-set reworks pending fixes from Wei's series [1] to make > >>> single-step debugging via kgdb/kdb on arm64 work as expected. There was > >>> a prior discussion on ML [2] regarding if we should keep the interrupts > >>> enabled during single-stepping. So patch #1 follows suggestion from Will > >>> [3] to not disable interrupts during single stepping but rather skip > >>> single stepping within interrupt handler. > >>> > >>> [1] https://lore.kernel.org/all/20200509214159.19680-1-liwei391@huawei.com/ > >>> [2] https://lore.kernel.org/all/CAD=FV=Voyfq3Qz0T3RY+aYWYJ0utdH=P_AweB=13rcV8GDBeyQ@mail.gmail.com/ > >>> [3] https://lore.kernel.org/all/20200626095551.GA9312@willie-the-truck/ > >>> > >>> Changes in v5: > >>> - Incorporated misc. comments from Mark. > >>> > >> > >> Since patch #1 has already been reviewed/acked by Mark and the > >> complete patchset has been tested by Doug, would it be fine for you to > >> pick up this patchset? It fixes a real single stepping problem for > >> kgdb on arm64. > > > > Sorry to be quiet for so long. > > > > Testing this patch set has proven to be a little difficult. > > > > It certainly fixes the single step tests in the kgdbtest suite. > > That's a good start. > > > > Unfortunately when testing using qemu/KVM (hosted on NXP > > 2k/Solidrun Honeycomb) the patch set is resulting in instability > > running the built-in self tests (specifically this one: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/misc/kgdbts.c#n74 ). Running this test using the kgdbtest harness > > results in the test failing roughly a third of the time. > > > > The error reported is that the trap handler tried to unlock a spinlock > > that isn't currently locked. To be honest I suspect this is a generic > > problem that the new feature happens to tickle (this test has > > historically been unreliable on x86 too... and x86 is noteworthy for > > being the only other platform I test using KVM rather than pure qemu). > > Of course the only way to prove that would be to find and fix the > > problem in the trap handler (which probably involves rewriting it) and I > > haven't managed to do that yet. > > > > In short, I think the debugger is more useful with this patchset than > > without so, although it is caveated by the above, I'd call this: > > > > Acked-by: Daniel Thompson <daniel.thompson@linaro.org> > > Tested-by: Daniel Thompson <daniel.thompson@linaro.org> > > > > > > Daniel. > > > > _______________________________________________ > > linux-arm-kernel mailing list > > linux-arm-kernel@lists.infradead.org > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >