From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0946AC7618B for ; Thu, 16 Mar 2023 17:34:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230004AbjCPRe6 (ORCPT ); Thu, 16 Mar 2023 13:34:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55192 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229903AbjCPRev (ORCPT ); Thu, 16 Mar 2023 13:34:51 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4BE785ADEE; Thu, 16 Mar 2023 10:34:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=ZWCsXuEnx5NPHpKnprrXUTjLpix1zKrrJlc3ZEj5QZQ=; b=eZshu5PoYOFmhYfVeDH1ySCMbb VkI0LmoRQng2JMFCroNhLnri1gdzRcxOo6i2qEYjto0yFHVM1YpN5mMvVD9uAEOQJfBop4fVucM32 aiPq9DFkUZqO+BMNj+4VTIzfwwTEm+XCuAyD/oBvOKctWlJl5cGIpsxBdOc7uqqsJTeMbD8dqabq9 jZbbuEWtB53VuQxyjrTbx/PABYlHTB8NlpD7iKdVB1zF+59VChK7ESu6Za0uCbDBUo9stnFJYSnZ7 QLuimxG/wuwQKmgDs5Llr7qXlNMi4KVPNT4KDyFnYWObHIG9pl0q8etPwfLbfDfNh4xWVC3sAD5jl QWKFxWWg==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1pcrUv-00F2M2-Of; Thu, 16 Mar 2023 17:34:41 +0000 Date: Thu, 16 Mar 2023 17:34:41 +0000 From: Matthew Wilcox To: Jiri Olsa Cc: Alexei Starovoitov , Andrii Nakryiko , Hao Luo , Andrew Morton , Alexander Viro , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , bpf@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-perf-users@vger.kernel.org, Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh , Stanislav Fomichev , Daniel Borkmann , Namhyung Kim , Dave Chinner Subject: Re: [PATCHv3 bpf-next 0/9] mm/bpf/perf: Store build id in file object Message-ID: References: <20230316170149.4106586-1-jolsa@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230316170149.4106586-1-jolsa@kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-perf-users@vger.kernel.org On Thu, Mar 16, 2023 at 06:01:40PM +0100, Jiri Olsa wrote: > hi, > this patchset adds build id object pointer to struct file object. > > We have several use cases for build id to be used in BPF programs > [2][3]. Yes, you have use cases, but you never answered the question I asked: Is this going to be enabled by every distro kernel, or is it for special use-cases where only people doing a very specialised thing who are willing to build their own kernels will use it? Saying "hubble/tetragon" doesn't answer that question. Maybe it does to you, but I have no idea what that software is. Put it another way: how does this make *MY* life better? Literally me. How will it affect my life?