Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp7393597rwb; Tue, 15 Nov 2022 11:34:41 -0800 (PST) X-Google-Smtp-Source: AA0mqf79gxQrpq850pcqsJhlSvAkW+NKYj/AVA73/OFFxAYPluyXRqJ+7PE8QzulAHweCf1/DO2/ X-Received: by 2002:aa7:d58b:0:b0:468:4c9a:7c6c with SMTP id r11-20020aa7d58b000000b004684c9a7c6cmr3044914edq.397.1668540881614; Tue, 15 Nov 2022 11:34:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668540881; cv=none; d=google.com; s=arc-20160816; b=xAAqvloIMimdMNqHRzOQ8FUFZzfLW4I8gqkalZFsbXominUHvOxn/Fhp45gFfSzxCR V9X3RNXsxHrIEdMJv3HxSvCh74v5hAMZKM0HgSKLf/Si9QfVH5twY39owlghhuG7J5p7 qn44knf9W1Fwa8ywu0NT1kCf8ZfQLoZ5T7CIroBHNY5QX5l+wpffQn54/OKUPpbPovFa g+Ocz6+wVrBGbVJubXZHiYHY4IOxSKtWHymme7tEhJaSKi7qWQa9EFrStAWVyMFMGCi0 UW3JiaT17N3tJYxp6VF2gqCcx5nIFfWmaFtMUaEmYNpw8PGinPwMTy2TIitsZd4qkaTZ fQ8Q== 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=NVmIK2KbmJcILQt5r8JiDxSMthBbVHuraQkf2M+r6zU=; b=0G9A58q2qv9n/ShPi6nLuqdKl6yVHkPCqRRbX9JQURwOK2yX57vtwevJRWkjbRVlEI KEf8Jw8LSvUqKHoAPii9ZzHRWxcMTgQVBgBWkfQiOHQS5Kot+twpDvB59HlganMVXGAq 6AKHxiYgUxgqJ2i2MP5y2ZibHmyOTX2fyWlL8okyD+6HmuVWMAdDk6t/w+LUh3DejO0r UD2z5bpmNrKXGABUZmPRiQo/YB40C4UhHbEJ02WdR/T1uGXBWU/Ct9neNe6sQVEy+dZM 9MEoGUgGuD6Ueb6jrdhHD8q39VgahbUivRNhLpHj9EAtTw02guNtL3YhLadpyoXZzDEL h+Gw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=glxVraLD; 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 u17-20020a509511000000b00461bff75d84si11343058eda.463.2022.11.15.11.34.19; Tue, 15 Nov 2022 11:34:41 -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=glxVraLD; 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 S230282AbiKOTNN (ORCPT + 91 others); Tue, 15 Nov 2022 14:13:13 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55950 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229882AbiKOTNL (ORCPT ); Tue, 15 Nov 2022 14:13:11 -0500 Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4903C303F9 for ; Tue, 15 Nov 2022 11:13:09 -0800 (PST) Received: by mail-wr1-x433.google.com with SMTP id z14so25849530wrn.7 for ; Tue, 15 Nov 2022 11:13:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=NVmIK2KbmJcILQt5r8JiDxSMthBbVHuraQkf2M+r6zU=; b=glxVraLDq6ErCS0YWPINbeqZZiQ1hA5c9A2gN06m1BOXrHnUSMdK9e2OvJty/UbiDB bHoNHG1ugIncwjk4bkc0mkhFtPEFIWItDdWxd8tN5gamuZfZH4zu8oJcJyLeeHq2KrT4 LUNaPxVGvHzY3a5yuPIthrIgp5AXd31R/JQ98XWTvxorSP2y1ym421vOQnpmwgq2Fv5l N1RR9tK/aQrWqeDH7xKupWbtyUsS6yQpPC1XmOOCvxehqKnmwDQY4FeQlCmZmlF0CZt4 yaHgYJUPrG5+KHlXYs6knDSJTQQ3XYX0fNfE/9pJkUwr0a5ztJGryqzVvcJTBvE1IZO2 b7xw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=NVmIK2KbmJcILQt5r8JiDxSMthBbVHuraQkf2M+r6zU=; b=4Rv+c4tqN5BV0upkISrQ6ZW9okixfW166X1hrK+N5dgay/9llyCl9260LTjulvQiQR 0M3fHN9Ldqj/JkgpmRs6cO8xCKXzszR+M9lRr5+k6JSFGgiYZWm7YGzWIhR+Bv1mTG/E 7KO2YI44oD/R3FcMEbqB/Ufp4reUf6gO2RgvMtVakPlSWibs2Eh4HaYRE1Hi5oRIlLMx uR+bDWzTbK9dhZnZY0XWwsYNOIsvxqg7qjZbbQrhxyVQtRXYOlayd2PZ3Oz5QfuONNrb 3HjIm47YoBoAxB9117aiYoQ82BRud1GL0XentL/pp2ZDF7vOolO0lapHwAyYOXLKx5Wx qU8g== X-Gm-Message-State: ANoB5pnqMUKRTo8AHb0f+Lu9O/RjXtdYPXWlqSY3l1F1eqpTY7FfYVMF J5je2NWWpuDRB1CLbAAwcpodnfRRJ1MKuv+3QjM3vA== X-Received: by 2002:a05:6000:1241:b0:236:d8f8:b87d with SMTP id j1-20020a056000124100b00236d8f8b87dmr11346690wrx.343.1668539587668; Tue, 15 Nov 2022 11:13:07 -0800 (PST) MIME-Version: 1.0 References: <20221103045437.163510-1-irogers@google.com> In-Reply-To: From: Ian Rogers Date: Tue, 15 Nov 2022 11:12:55 -0800 Message-ID: Subject: Re: [PATCH v1 0/7] Fix perf trace libbpf 1.0+ compatibility To: Leo Yan Cc: Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, Stephane Eranian 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, 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, Nov 11, 2022 at 4:09 AM Leo Yan wrote: > > Hi Ian, Arnaldo, > > On Wed, Nov 02, 2022 at 09:54:30PM -0700, Ian Rogers wrote: > > Perf trace can augment system calls with a BPF program passed as an > > event. The BPF code for this lives in examples. This patch fixes the > > example code to not used deprecated/removed APIs in libbpf. As libbpf > > has similar header files to tools/perf/include/bpf the code is > > transitioned to use the more standard libbpf code and the perf BPF > > header files removed. > > I think you missed to update the code examples/bpf/sys_enter_openat.c, > either you could remove it (since it's duplicate with > augmented_raw_syscalls.c), or we should apply below fixing: Arnaldo, what do you think? Thanks, Ian > From f30af3b43060e482c54e113cbe90223173c69abd Mon Sep 17 00:00:00 2001 > From: Leo Yan > Date: Fri, 11 Nov 2022 12:02:24 +0000 > Subject: [PATCH] perf trace: sys_enter_openat.c fix libbpf 1.0+ compatibility > > Avoid use of tools/perf/include/bpf/bpf.h and use the more regular BPF > headers. > > With fixing: > > # ./perf trace -e examples/bpf/sys_enter_openat.c > 0.000 irqbalance/1025 syscalls:sys_enter_openat(AT_FDCWD, "", O_RDONLY) > 1.596 irqbalance/1025 syscalls:sys_enter_openat(AT_FDCWD, "", O_RDONLY) > 1.832 irqbalance/1025 syscalls:sys_enter_openat(AT_FDCWD, "", O_RDONLY) > 1.864 irqbalance/1025 syscalls:sys_enter_openat(AT_FDCWD, "", O_RDONLY) > > Signed-off-by: Leo Yan > --- > tools/perf/examples/bpf/sys_enter_openat.c | 9 ++++++--- > 1 file changed, 6 insertions(+), 3 deletions(-) > > diff --git a/tools/perf/examples/bpf/sys_enter_openat.c b/tools/perf/examples/bpf/sys_enter_openat.c > index c4481c390d23..8edfa7c147d1 100644 > --- a/tools/perf/examples/bpf/sys_enter_openat.c > +++ b/tools/perf/examples/bpf/sys_enter_openat.c > @@ -14,7 +14,9 @@ > * the return value. > */ > > -#include > +#include > +#include > +#include > > struct syscall_enter_openat_args { > unsigned long long unused; > @@ -25,9 +27,10 @@ struct syscall_enter_openat_args { > long mode; > }; > > -int syscall_enter(openat)(struct syscall_enter_openat_args *args) > +SEC("syscalls:sys_enter_openat") > +int syscall_enter_openat(struct syscall_enter_openat_args *args) > { > return 1; > } > > -license(GPL); > +char _license[] SEC("license") = "GPL";