Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp2223604imc; Tue, 12 Mar 2019 09:20:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqzO6hEpEaLrbtqEt9/SQpoKPa62JgX0s2HaFgfp8/inlsXp3wiUTheYohsyVL3pWXwAP158 X-Received: by 2002:a63:4542:: with SMTP id u2mr35388705pgk.291.1552407626717; Tue, 12 Mar 2019 09:20:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552407626; cv=none; d=google.com; s=arc-20160816; b=TUSQcI/Vd6wxqgnDSiSYyjiEldNNwuXjxnqef/LwDx3sgpC1rDhS6ZXMhdJH5e5qgV ACYFr5ERBFiAYtPsIeIhJe8DmCHdsagmPxe4edtoHlEevKIf4m4EK/N8I284hdH5bLpd wmweMWDwH31fvtZT0SsGcvWZcNaP0dvbPfUKi7MEhppmIlQsvORPo/9YIamNFhGiZMqC mkLayuzkhjq5mr4/q1m9M6Wy8i4BYAHsfOjY9aQZ4Q3UAvNm9u4YLH/lFIZTlpUCrB5A A1o0ukMEHhS68/QDk7TRA+cbaxuMCPCpmNU7G6WBtY9CdbhPmYY8+Sk40XKDqUj1hY1Y 6Iug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=ZtIfOTFcJPLrLFti3O3pAMEQ2STJBEwh8CCDSQM8N8s=; b=xCPFm5i0VbOCPFSRR0FDncSNpIsVvcJWb24xlW/6LK2oQMfWn/FRgBkBAGAI6KhqwY I7Z0mgNQAANmzTRX6S5FYXr108Tz78sr/xqJ1Pj57ygm47jZlwZyXXl3qrVtmv7uWK6N npTkw93NK4s/ZkwN/M+xVqquAzhaVCvzBkiLOpznLYY3aN6x8Qu61K5CX1m+liYbEucO 3boiEy87CEl25/5+E73u4WetrR6U5CuCE7bzgXlaLIZl/cwi8iUs7XzB0FnDRQtxk5q+ MEBaMSB27cU6VqLWilBWKoRQiDmi99taG27dRXTHb9a8EiqURMv74ORHKHD2+FVVZVjQ 6FWw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 23si7783609pgc.220.2019.03.12.09.20.10; Tue, 12 Mar 2019 09:20:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726695AbfCLQTq (ORCPT + 99 others); Tue, 12 Mar 2019 12:19:46 -0400 Received: from foss.arm.com ([217.140.101.70]:44912 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726365AbfCLQTq (ORCPT ); Tue, 12 Mar 2019 12:19:46 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id BF36480D; Tue, 12 Mar 2019 09:19:45 -0700 (PDT) Received: from e107158-lin.cambridge.arm.com (e107158-lin.cambridge.arm.com [10.1.195.17]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id CE1D43F59C; Tue, 12 Mar 2019 09:19:43 -0700 (PDT) Date: Tue, 12 Mar 2019 16:19:41 +0000 From: Qais Yousef To: Alexei Starovoitov Cc: Steven Rostedt , Ingo Molnar , Alexei Starovoitov , Daniel Borkmann , Martin KaFai Lau , Song Liu , Yonghong Song , "linux-kernel@vger.kernel.org" , "netdev@vger.kernel.org" , "bpf@vger.kernel.org" Subject: Re: [RFC][PATCH] Export supported trace features in debugfs Message-ID: <20190312161941.6vlxp3qvad5oy4fs@e107158-lin.cambridge.arm.com> References: <20190312110437.5977-1-qais.yousef@arm.com> <20190312152703.dulqcnhkknklxihq@ast-mbp> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190312152703.dulqcnhkknklxihq@ast-mbp> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/12/19 08:27, Alexei Starovoitov wrote: > On Tue, Mar 12, 2019 at 11:07:14AM +0000, Qais Yousef wrote: > > eBPF tools like bcc-tools have hard time figuring out when features like > > raw_tracepoint are supported in the kernel on which we are running. At > > the moment a fragile mechanism of matching bpf_find_raw_tracepoint() > > function in /proc/kallsyms is used to find out whether raw tracepoints > > can be used or not. But when this function was renamed recently to > > bpf_get_raw_tracepoint() the tool started to fail to use raw > > tracepoints. > > > > To help in providing a more reliable way to detect features like > > RAW_TRACEPOINT, add a new file in trace debugfs to export the supported > > features. > > > > $cat /sys/kernel/debug/tracing/supported_features > > RAW_TRACEPOINT > > EXAMPLE_FEATURE_1 > > EXAMPLE_FEATURE_2 > > > > Signed-off-by: Qais Yousef > > this type of attempts have been made in the past and we always rejected them. > Please use 'bpftool' instead that detects numerous bpf related features including raw_tp. > # bpftool feature probe|grep raw_tracepoint > eBPF program_type raw_tracepoint is available > I see. I should have looked harder. I'll have a look at what bpftool does then. Thanks -- Qais Yousef