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 4F704C77B75 for ; Wed, 19 Apr 2023 22:27:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233761AbjDSW13 (ORCPT ); Wed, 19 Apr 2023 18:27:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49088 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232047AbjDSW1F (ORCPT ); Wed, 19 Apr 2023 18:27:05 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4771BCC19; Wed, 19 Apr 2023 15:25:42 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 1FCE0219D8; Wed, 19 Apr 2023 22:23:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1681943023; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=vY8XN3Sn3K1YcDvAR1zsIPMfvzeTloMrq3UeYNL0QaE=; b=W4RZg/5wedj4o/nehxu1JkvbBXwjUR1CQtUu+DigmwIBHJc4x1KAwp8WVeqFwpsMTjB9wK xjh4KzW3dLI4MVyVZsKpUjxoMAtTkz6TT8yuuF3jYQ1ltg81qSh2zmij51XuTCiJ2Oyqvw 8aUfEclQ2AS4kRhDjtRdTwnWh8LpKK4= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1681943023; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=vY8XN3Sn3K1YcDvAR1zsIPMfvzeTloMrq3UeYNL0QaE=; b=Ih4T4Lt0LjXvm5m12QXGbyk8agAG49M4S2b0KrSwIKidzJ7CpEqgDlrPyBnwvw38+2ChNU 7trsWXwVU6dURqAw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id AFD311390E; Wed, 19 Apr 2023 22:23:39 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id uRZcIOtpQGSUUgAAMHmgww (envelope-from ); Wed, 19 Apr 2023 22:23:39 +0000 Date: Wed, 19 Apr 2023 15:23:36 -0700 From: tonyj@suse.de To: Andrii Nakryiko Cc: Shung-Hsi Yu , Arnaldo Carvalho de Melo , Toke =?iso-8859-1?Q?H=F8iland-J=F8rgensen?= , Andrii Nakryiko , bpf@vger.kernel.org, linux-perf-users@vger.kernel.org, Alexei Starovoitov , Daniel Borkmann , Quentin Monnet , Jiri Olsa , Michal Suchanek , Jesper Dangaard Brouer , Jakub Sitnicki , David Miller Subject: Re: Packaging bpftool and libbpf: GitHub or kernel? Message-ID: References: <87leiw11yz.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org On Wed, Apr 19, 2023 at 12:42:39PM -0700, Andrii Nakryiko wrote: > I won't claim anything for perf, maybe Arnaldo can clarify, but I > suspect that perf is also meant to be relatively independent from > specific kernel and work on wide variety of kernels. Supposedly it is though I've never been able to convince myself to decouple (and ship the latest perf) for SLE. One reason is documented userspace functionality that has no backing kernel support which for an Enterprise distro opens us up to bug reports. For a while Vince was maintaining a page documenting breakage in the perf_event ABI but last I checked it ended at V4.0. Not sure if he just stopped updating, or that's where breakage ended :) I know how Fedora maintains perf but I keep meaning to look at how RHEL maintains it. As Michal said our code base is V5.14 for SLE15* and due to the frequent code-refactoring in perf, backporting perf userspace fixes for SLE is a real chore unless we agressively maintain forward porting ("forklifting"). Tony -- Tony Jones SUSE Kernel Performance Team