Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp1178989pxb; Fri, 18 Feb 2022 02:16:40 -0800 (PST) X-Google-Smtp-Source: ABdhPJw40YIB+uVuR+lOHS4nlu0wg5NYgpvvq7vjDZOqZFW62PXOuEaUGFcg3CzlR4YTi5Iya/F5 X-Received: by 2002:a17:902:6b02:b0:14f:4122:e8ac with SMTP id o2-20020a1709026b0200b0014f4122e8acmr6841919plk.166.1645179400417; Fri, 18 Feb 2022 02:16:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645179400; cv=none; d=google.com; s=arc-20160816; b=ANc2Mp8xlaH8HcHJzjko5Whida3xxCxZ/cf881qmlyqhS6iwy+Y7QtSO26YSHF6iJA 2jdcwOpjNEMEK44cLBpOzOawbYykGB909j32GT7pefTJMtW1fHQYlxVVt79NEgTQ4Ix3 ck7Pj/eoX5toV/DpEB3HgVEl4bzPua5ooInXt0CP4iODurmyK6F69xLiBCpTfPBLOocN DXy6IQfNqdurCFNPDXN2IBv1qBWcQQG33DQH1JkhyynhqO0b3vsc1c4JlQ6lFGx4nscR kZTCRX6FF88YGkMmyrAepYiQdEVrzzKmdWdHpfo8hIY1MUzP+inJkfjM1+xej4Whv1i9 vDCA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=9TGdjV0Q3xyVks5N4khTecn3sldyZnJb3gKUY1KtrMU=; b=tDiIQytiRUmaQ8jtpCq8wI/IvPvO+zE/68T7SBqY3wTqFXFH+uJU7SO+55y7m879cC 9NjO1f38qUPx47ApaDRXGZ3xwwiLNagBOKHHLyXLimXiawMTu+bu4ZfZOMIk9lpE6zij biHFrBtUckq8sb1tAx/gYixLdjj0moUEZvEwchuvANgZS2fWcPfb8EKG2dNZWqPu9mwp iZRpsl5UoQCAazyNRcI4VLbjB/B4yXInX7cjEfImAbT7v/OgXbGGD3/xVbYOt0RFeCD/ +F8khxGWNjUq02/40C+T8RWPF9x4dQbQX+kcUodYDtzmo8bKUvah2m3YwtcfXqbmFcCP dHhQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=AOlbdfQf; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j186si10414602pge.112.2022.02.18.02.16.26; Fri, 18 Feb 2022 02:16:40 -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=@google.com header.s=20210112 header.b=AOlbdfQf; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233729AbiBRJoo (ORCPT + 99 others); Fri, 18 Feb 2022 04:44:44 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:55458 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232251AbiBRJon (ORCPT ); Fri, 18 Feb 2022 04:44:43 -0500 Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 70C3B23BCF for ; Fri, 18 Feb 2022 01:44:27 -0800 (PST) Received: by mail-yb1-xb31.google.com with SMTP id j12so18380188ybh.8 for ; Fri, 18 Feb 2022 01:44:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9TGdjV0Q3xyVks5N4khTecn3sldyZnJb3gKUY1KtrMU=; b=AOlbdfQfIplSLJ+l7JlFsTZZwiIAFQP4vIRwLqfU+sjpXwwcGu+odpiC4icGnuczPs KCQ7UdnoBYRMsYk4KeyzhC7qAGYFA6E0Qpq1O8DZcHvVi2MjhrMYLTiUb75o29fdI75c CKuYhRHEpbSSPBB14diyEqMWUJEOPcEGtzPdzR+LoAq888eDJge9JXTuL5kepYYkD1cg QhlHmg2DKjFO5jG057keS4XhnJcVSMwgq5fnEB5xAJIPsb5YlIYAsux692PLMV3ZZHpX lfFUmmSibdwm0f4NpT9WiEByUqvPez+8mLlHyJBgv/9VM10QxKwTWqjEryMUlv6dNWKb dqLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9TGdjV0Q3xyVks5N4khTecn3sldyZnJb3gKUY1KtrMU=; b=fO0JW1qQedh9cMtxvjSDx09mcpYelOYQvByRceSsQ2H5N2paWmF1FEX+Jn9GHYweqd G0pFaI7JGm2GF/7wVDDAVPrr3IRckSMDo/RMa5gbD0n4kNriYcU7gLlocEWT8iuCMTQX h+yIR3Tz4beBjEsIJKmhqs1Fm3VSoAK/+z+xZEKvT4qQGB+NkgxwPodh98xE+K5lRucO tVMewQB6i66Blmgtrb+EPGEjfdu2uh5TEeGhbYTPp0InS+wxUL3sQEjIvKSx+9vw6Zr3 F+WJnun1ecWdFOwDj3HABshtwiyYPacVlAeCn9zQYLKm2OKk51G+arVaTjxFgS7lavUb 6Ftw== X-Gm-Message-State: AOAM53146EjVes9CcZjUC0LUKdw6J/C+dthgOcqqFrvH01tlOrYtuMmg UZAf4R+ssMh/faQoMCU44b9+yjk6+yS7tk540dKv8A== X-Received: by 2002:a05:6902:2:b0:624:4cb5:fd3b with SMTP id l2-20020a056902000200b006244cb5fd3bmr791226ybh.1.1645177466506; Fri, 18 Feb 2022 01:44:26 -0800 (PST) MIME-Version: 1.0 References: <1645176813-202756-1-git-send-email-john.garry@huawei.com> In-Reply-To: <1645176813-202756-1-git-send-email-john.garry@huawei.com> From: Marco Elver Date: Fri, 18 Feb 2022 10:44:15 +0100 Message-ID: Subject: Re: [PATCH v2] perf test: Skip Sigtrap test for arm+aarch64 To: John Garry Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org, mark.rutland@arm.com, jolsa@kernel.org, namhyung@kernel.org, leo.yan@linaro.org, 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 Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL 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: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 18 Feb 2022 at 10:39, 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 Acked-by: Marco Elver Thanks ! > diff --git a/tools/perf/tests/sigtrap.c b/tools/perf/tests/sigtrap.c > index 1f147fe6595f..e32ece90e164 100644 > --- a/tools/perf/tests/sigtrap.c > +++ b/tools/perf/tests/sigtrap.c > @@ -22,19 +22,6 @@ > #include "tests.h" > #include "../perf-sys.h" > > -/* > - * PowerPC and S390 do not support creation of instruction breakpoints using the > - * perf_event interface. > - * > - * Just disable the test for these architectures until these issues are > - * resolved. > - */ > -#if defined(__powerpc__) || defined(__s390x__) > -#define BP_ACCOUNT_IS_SUPPORTED 0 > -#else > -#define BP_ACCOUNT_IS_SUPPORTED 1 > -#endif > - > #define NUM_THREADS 5 > > static struct { > @@ -135,7 +122,7 @@ static int test__sigtrap(struct test_suite *test __maybe_unused, int subtest __m > char sbuf[STRERR_BUFSIZE]; > int i, fd, ret = TEST_FAIL; > > - if (!BP_ACCOUNT_IS_SUPPORTED) { > + if (!BP_SIGNAL_IS_SUPPORTED) { > pr_debug("Test not supported on this architecture"); > return TEST_SKIP; > } > -- > 2.26.2 >