From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Leo Yan <leo.yan@linaro.org>
Cc: John Garry <john.garry@huawei.com>,
peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
jolsa@kernel.org, namhyung@kernel.org, elver@google.com,
dvyukov@google.com, will@kernel.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux@armlinux.org.uk,
tmricht@linux.ibm.com, irogers@google.com
Subject: Re: [PATCH v2] perf test: Skip Sigtrap test for arm+aarch64
Date: Fri, 18 Feb 2022 09:56:58 -0300 [thread overview]
Message-ID: <Yg+Xmt27POS2y2LI@kernel.org> (raw)
In-Reply-To: <20220218104611.GD56419@leoy-ThinkPad-X240s>
Em Fri, Feb 18, 2022 at 06:46:11PM +0800, Leo Yan escreveu:
> On Fri, Feb 18, 2022 at 05:33:33PM +0800, John Garry wrote:
> > Skip the Sigtrap test for arm + arm64, same as was done for s390 in
> > commit a840974e96fd ("perf test: Test 73 Sig_trap fails on s390"). For
> > this, reuse BP_SIGNAL_IS_SUPPORTED - meaning that the arch can use BP to
> > generate signals - instead of BP_ACCOUNT_IS_SUPPORTED, which is
> > appropriate.
> >
> > As described by Will at [0], in the test we get stuck in a loop of handling
> > the HW breakpoint exception and never making progress. GDB handles this
> > by stepping over the faulting instruction, but with perf the kernel is
> > expected to handle the step (which it doesn't for arm).
> >
> > Dmitry made an attempt to get this work, also mentioned in the same thread
> > as [0], which was appreciated. But the best thing to do is skip the test
> > for now.
> >
> > [0] https://lore.kernel.org/linux-perf-users/20220118124343.GC98966@leoy-ThinkPad-X240s/T/#m13b06c39d2a5100d340f009435df6f4d8ee57b5a
> >
> > Fixes: Fixes: 5504f67944484 ("perf test sigtrap: Add basic stress test for sigtrap handling")
> > Signed-off-by: John Garry <john.garry@huawei.com>
>
> I tested this patch on my Juno board:
>
> root@Juno:# ./perf test 73
> 73: Sigtrap : Skip
>
> Tested-by: Leo Yan <leo.yan@linaro.org>
Thanks, applied.
- Arnaldo
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Leo Yan <leo.yan@linaro.org>
Cc: John Garry <john.garry@huawei.com>,
peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
jolsa@kernel.org, namhyung@kernel.org, elver@google.com,
dvyukov@google.com, will@kernel.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux@armlinux.org.uk,
tmricht@linux.ibm.com, irogers@google.com
Subject: Re: [PATCH v2] perf test: Skip Sigtrap test for arm+aarch64
Date: Fri, 18 Feb 2022 09:56:58 -0300 [thread overview]
Message-ID: <Yg+Xmt27POS2y2LI@kernel.org> (raw)
In-Reply-To: <20220218104611.GD56419@leoy-ThinkPad-X240s>
Em Fri, Feb 18, 2022 at 06:46:11PM +0800, Leo Yan escreveu:
> On Fri, Feb 18, 2022 at 05:33:33PM +0800, John Garry wrote:
> > Skip the Sigtrap test for arm + arm64, same as was done for s390 in
> > commit a840974e96fd ("perf test: Test 73 Sig_trap fails on s390"). For
> > this, reuse BP_SIGNAL_IS_SUPPORTED - meaning that the arch can use BP to
> > generate signals - instead of BP_ACCOUNT_IS_SUPPORTED, which is
> > appropriate.
> >
> > As described by Will at [0], in the test we get stuck in a loop of handling
> > the HW breakpoint exception and never making progress. GDB handles this
> > by stepping over the faulting instruction, but with perf the kernel is
> > expected to handle the step (which it doesn't for arm).
> >
> > Dmitry made an attempt to get this work, also mentioned in the same thread
> > as [0], which was appreciated. But the best thing to do is skip the test
> > for now.
> >
> > [0] https://lore.kernel.org/linux-perf-users/20220118124343.GC98966@leoy-ThinkPad-X240s/T/#m13b06c39d2a5100d340f009435df6f4d8ee57b5a
> >
> > Fixes: Fixes: 5504f67944484 ("perf test sigtrap: Add basic stress test for sigtrap handling")
> > Signed-off-by: John Garry <john.garry@huawei.com>
>
> I tested this patch on my Juno board:
>
> root@Juno:# ./perf test 73
> 73: Sigtrap : Skip
>
> Tested-by: Leo Yan <leo.yan@linaro.org>
Thanks, applied.
- Arnaldo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-18 12:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 9:33 [PATCH v2] perf test: Skip Sigtrap test for arm+aarch64 John Garry
2022-02-18 9:33 ` John Garry
2022-02-18 9:44 ` Marco Elver
2022-02-18 9:44 ` Marco Elver
2022-02-18 10:46 ` Leo Yan
2022-02-18 10:46 ` Leo Yan
2022-02-18 12:56 ` Arnaldo Carvalho de Melo [this message]
2022-02-18 12:56 ` Arnaldo Carvalho de Melo
2022-02-21 9:52 ` kajoljain
2022-02-21 9:52 ` kajoljain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yg+Xmt27POS2y2LI@kernel.org \
--to=acme@kernel.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=irogers@google.com \
--cc=john.garry@huawei.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tmricht@linux.ibm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.