From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by smtp.subspace.kernel.org (Postfix) with ESMTPS id 686D61ADC6E;
	Tue, 14 Jan 2025 16:21:19 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1736871679; cv=none; b=kFD5ZwICJXLZyUa17WfK5EcWL+9j5ZwbTrE4f1V+BElHb1b8lSP96YfxgCmlxo1YTQZa6nnFqvhqVckBHN5zs9EsMB8h/OvIpI3KlZYUbUcU0KdfraZK9W+a2BrjNVNNJqn4Ls5YvFQnRgVtmk9wuu4bhwVFhJMg/uPJ07oveYE=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1736871679; c=relaxed/simple;
	bh=fItVol50/+YaGZarRhLoai1RaEyMgZvH+fRABBY5oRk=;
	h=Date:From:To:Cc:Subject:Message-ID:MIME-Version:Content-Type:
	 Content-Disposition; b=QYcPRgVot29F82XwvzoIwgPlKGx85+DVhFqUAUqxXWYk3c2/W3vW+wIaBtY2z6SH9gRe7QQuTF4ykU52HPB2WIuwoHb3CHJ/JhU5y8gjXeBc1mEaQQUxTtsxNdeX3plfqV3bENkgreL/Ir7/W1Via8DbNzuARuzPoC+OnRGE3XU=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=kYXNX1B9; arc=none smtp.client-ip=10.30.226.201
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="kYXNX1B9"
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8FAA4C4CEDD;
	Tue, 14 Jan 2025 16:21:18 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
	s=k20201202; t=1736871678;
	bh=fItVol50/+YaGZarRhLoai1RaEyMgZvH+fRABBY5oRk=;
	h=Date:From:To:Cc:Subject:From;
	b=kYXNX1B9ZQUwzCdpbwP/Y2h8WsUaNRDrzj5ti17ZyL9i13+SKjLfEmsIgedcLWxwG
	 G3IgGZfQymDmNp4yHVG2y9xSBcq/eT95MmQha50fxOUYZG7O4BPw7WWJgKj+6FZi6y
	 I4Riuh8PFmnwXq18fp7CZUVTA22Ni6Rg1ltyzdIJE+5XCgu0FKrymwMdGnJBA9mpjl
	 j3B6yJXbHF4+g1LVbN78yA8iBe/yPEqZfpxtlIVXb79FJqSVRNx11UQFiq6anjnmHP
	 SVLsEbuIKaPERExhSoP8xpH/Yz9zAGSDxk3mPCiPq+3xqW+a15OYRh1pHQ2RtM4w7Y
	 dGpQ+bTxIoYdQ==
Date: Tue, 14 Jan 2025 13:21:15 -0300
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: lsf-pc@lists.linux-foundation.org
Cc: bpf@vger.kernel.org, dwarves@vger.kernel.org,
	Namhyung Kim <namhyung@kernel.org>,
	Alan Maguire <alan.maguire@oracle.com>
Subject: [LSF/MM/BPF TOPIC] pahole + BTF update and next steps
Message-ID: <Z4aO-4mkXi4ID7xs@x1>
Precedence: bulk
X-Mailing-List: dwarves@vger.kernel.org
List-Id: <dwarves.vger.kernel.org>
List-Subscribe: <mailto:dwarves+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:dwarves+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Hi,
 
	I'd like to propose a BPF activity on a pahole + BTF update,
mentioning features that were implemented since last year, changes in
the release cadence, testing, and maintainance of pahole.

	Also about preparing it for when BTF gets natively generated by
gcc/clang for the kernel, when it becomes a BTF "augmenter", adding
extra info or removing/fixing initial compiler BTF generation problems.

	This would be kinda complementary to José's "Compiled BPF"
proposal, I guess.

	There are also new usage in perf of BPF and BTF that could be
covered, if there's interest in that as well.

Thanks,

- Arnaldo