Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp541702pxb; Thu, 17 Feb 2022 09:17:20 -0800 (PST) X-Google-Smtp-Source: ABdhPJzQa6k9NPRdMkYqeTa28RfkLMaP/GoRbyrq2aM41MIB/SyhEPtmysJnqXRVFFTTsy4L2jin X-Received: by 2002:a50:9ee6:0:b0:3e3:53ea:da61 with SMTP id a93-20020a509ee6000000b003e353eada61mr3690842edf.39.1645118240297; Thu, 17 Feb 2022 09:17:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645118240; cv=none; d=google.com; s=arc-20160816; b=MgUB+JAga6045CX4FGXf0oLv9fGtL+LtSPBeHt/MgBKtotKShixA8ah+CbRDNSxCFf V4sPyT5WSYlooK+NE8iPRHe+UydI6oPnvT9BuuXR8EsjdukHEU3N/FZzn0+1kroVe060 gUKHv7urBhDJq3vYr3qKpgVBKsgoUs+6NUlIJL8wKT2Mw59/QYl0suth82s0AWYqGAZZ Nzn7M13W3bzf5rwT8HBPFVFCR5BCwVJQFTDPxsQB4jMctJ9cJFdAZbcLiUCq3Ta8UJCo gLYZTIwjZ61tmgPHMae7S2ODPze1dq8M6W234ESn/ksy7ICakBOTunOdExDxyeGbYejD 5Sfw== 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=Krbys4z1HiJYbO7ekpiHQnj69+zGpmG1n2OUUWl+mIM=; b=WPrJi+PQ4Rx/lAq/lK9ud8ZThzZrtsZ75dzfwRGIDl24lyXhUv7Fr444N3egSYNTXO eN2keMz86YWShN/vFpQyDcY9aJ5zn0UcpV6OQb0vqrM0H045/RF6aOb2Vqkr7NW6Zr63 b3EiZl3vwfL83L9o+9vq/5/+LY4UrSXe3vmUpjPdRzl4hHCo4s4fUv+bm8r4h1Kz658U sGMurElvA+I3aADENt8dXUEvo/XJZPMG9i5qjOJvaZ4rotkeQqHHgxYWsO2evNzV2tiO aNlWFMB3dwdj5mRgOZyNO02ORiI6Ce0VdZBkr01FWDH7uKJl95otCB+b1PXc4nlkpk+z QYtw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=Sum0eKi9; 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 y3si2059736ejk.567.2022.02.17.09.16.54; Thu, 17 Feb 2022 09:17:20 -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=Sum0eKi9; 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 S243401AbiBQQqW (ORCPT + 99 others); Thu, 17 Feb 2022 11:46:22 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:33188 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239915AbiBQQqV (ORCPT ); Thu, 17 Feb 2022 11:46:21 -0500 Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3BA1D13E24 for ; Thu, 17 Feb 2022 08:46:01 -0800 (PST) Received: by mail-yb1-xb2a.google.com with SMTP id bt13so14311971ybb.2 for ; Thu, 17 Feb 2022 08:46:01 -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=Krbys4z1HiJYbO7ekpiHQnj69+zGpmG1n2OUUWl+mIM=; b=Sum0eKi9lz9/AsHv7XUtUOTvCs8DBrKvEzLtHtvjJ2sq5smZHSfCSkdVPJaEVStXAY DcmI8SFRd3HdnLNleqKe20e4PSC95CvEvqvYu6rU2zEccEMklpN+27lDiI7yK3QbX1Wm 6Svp0TrvotB+PBNZ7S0B4vJ66hAaAaHuKVy+CzM05vWtOo5rWM3fvTMy2LZjDr1OZzLL BIOa3FMCLEEoJ2v5dYWygMcy70OTcnoVvwXs6Ptg3ViwGq8rMaLJ+7t225e+LvaBg5tw mGl0JNL0W/CichfPjAiFqlGr7QrLznIBXXqJ/7G2fK71/mzetmBkZ8JJqt/5BU+RKEJt RQew== 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=Krbys4z1HiJYbO7ekpiHQnj69+zGpmG1n2OUUWl+mIM=; b=c+wv/CArjULt5aMUqgXNKzkA4v9/zkM6k2A73Afkei8heqBoqrMLtcp+B45kBeGv3o RIojXM72yGsFphL8kvz3IsdriuPTu2kVlBXl9oIG9igeZp1kK8lqKVMkNGFfCtxZ0BaI bLoBZm6UOOML0AgbQkEv8iQoXzST+o4ordO6dFz8xfBncamfeBBcCubEJQeIwASx7Edf dWtv7+wi4ZXZgQkH6u97Y0Ky9BtpfpGt5WNpsp6IZps/Y2TqpmDwehONI5e21IAKrweL jszuoJ7qVa9LlK8tEE6DI041M9UGgkqFiXvN2QSprV9g7uuoyNswxoyBH0dk2qDdcfOR ZBww== X-Gm-Message-State: AOAM531qn0+WtuiqdOPqFiuQN5VdWf589uGalPjXteoraEfa2xtbVHJX 0ip1/wr99/EfSbyM77oP55SdoNRw6HQN5Cu0cGBRAw== X-Received: by 2002:a25:bb8d:0:b0:61d:aca6:8aa0 with SMTP id y13-20020a25bb8d000000b0061daca68aa0mr3232251ybg.609.1645116360251; Thu, 17 Feb 2022 08:46:00 -0800 (PST) MIME-Version: 1.0 References: <1645114959-119064-1-git-send-email-john.garry@huawei.com> In-Reply-To: <1645114959-119064-1-git-send-email-john.garry@huawei.com> From: Marco Elver Date: Thu, 17 Feb 2022 17:45:49 +0100 Message-ID: Subject: Re: [PATCH] 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 Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,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 Thu, 17 Feb 2022 at 17:28, 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"). > > 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 > > diff --git a/tools/perf/tests/sigtrap.c b/tools/perf/tests/sigtrap.c > index 1f147fe6595f..3f0b5c1398b5 100644 > --- a/tools/perf/tests/sigtrap.c > +++ b/tools/perf/tests/sigtrap.c > @@ -29,7 +29,8 @@ > * Just disable the test for these architectures until these issues are > * resolved. > */ > -#if defined(__powerpc__) || defined(__s390x__) > +#if defined(__powerpc__) || defined(__s390x__) || \ > + defined(__arm__) || defined(__aarch64__) > #define BP_ACCOUNT_IS_SUPPORTED 0 > #else > #define BP_ACCOUNT_IS_SUPPORTED 1 This is now equivalent to BP_SIGNAL_IS_SUPPORTED tools/perf/tests/tests.h -- and different from the original BP_ACCOUNT_IS_SUPPORTED (and makes me wonder why BP_SIGNAL_IS_SUPPORTED wasn't just used from the beginning). Perhaps just use BP_SIGNAL_IS_SUPPORTED. Thanks, -- Marco