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 X-Spam-Level: X-Spam-Status: No, score=-7.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4DA6EC433E0 for ; Fri, 3 Jul 2020 09:52:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2D82520723 for ; Fri, 3 Jul 2020 09:52:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1593769920; bh=hfJTl0/D4/JbSzv4qnqArqGvNEob8dhcym8H2fhZ85M=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=fxHjiwWXowk2qtSi51Ni0ZvxlJ5bUigmU8dKNcaZm7QMaORnE+OWAAHP61eAohYjz plN+HWZhjPAIiBYrkY4HQprm1xw37qLbV7XpODoocQmY1HBm496Wvfbim21XvC24WR lfchMYq2So5CUC1MGnqblATgKbPDrnvv0ug0S+8w= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726290AbgGCJv6 convert rfc822-to-8bit (ORCPT ); Fri, 3 Jul 2020 05:51:58 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:40696 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726311AbgGCJv5 (ORCPT ); Fri, 3 Jul 2020 05:51:57 -0400 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-471-ojwtpxGtOXGd74_3FGCCmQ-1; Fri, 03 Jul 2020 05:51:53 -0400 X-MC-Unique: ojwtpxGtOXGd74_3FGCCmQ-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D88C4107ACCD; Fri, 3 Jul 2020 09:51:50 +0000 (UTC) Received: from krava.redhat.com (unknown [10.40.194.24]) by smtp.corp.redhat.com (Postfix) with ESMTP id 39ABF9CA0; Fri, 3 Jul 2020 09:51:46 +0000 (UTC) From: Jiri Olsa To: Alexei Starovoitov , Daniel Borkmann Cc: netdev@vger.kernel.org, bpf@vger.kernel.org, Song Liu , Yonghong Song , Martin KaFai Lau , David Miller , John Fastabend , Wenbo Zhang , KP Singh , Andrii Nakryiko , Brendan Gregg , Florent Revest , Al Viro Subject: [PATCH v5 bpf-next 7/9] bpf: Add info about .BTF.ids section to btf.rst Date: Fri, 3 Jul 2020 11:51:09 +0200 Message-Id: <20200703095111.3268961-8-jolsa@kernel.org> In-Reply-To: <20200703095111.3268961-1-jolsa@kernel.org> References: <20200703095111.3268961-1-jolsa@kernel.org> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=jolsa@kernel.org X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: kernel.org Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: 8BIT Sender: bpf-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org Updating btf.rst doc with info about .BTF.ids section Signed-off-by: Jiri Olsa --- Documentation/bpf/btf.rst | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/Documentation/bpf/btf.rst b/Documentation/bpf/btf.rst index 4d565d202ce3..17ebd78d2c9e 100644 --- a/Documentation/bpf/btf.rst +++ b/Documentation/bpf/btf.rst @@ -691,6 +691,42 @@ kernel API, the ``insn_off`` is the instruction offset in the unit of ``struct bpf_insn``. For ELF API, the ``insn_off`` is the byte offset from the beginning of section (``btf_ext_info_sec->sec_name_off``). +4.2 .BTF.ids section +==================== + +The .BTF.ids section encodes BTF ID values that are used within the kernel. + +This section is created during the kernel compilation with the help of +macros defined in ``include/linux/btf_ids.h`` header file. Kernel code can +use them to create lists and sets (sorted lists) of BTF ID values. + +The ``BTF_ID_LIST`` and ``BTF_ID`` macros define unsorted list of BTF ID values, +with following syntax:: + + BTF_ID_LIST(list) + BTF_ID(type1, name1) + BTF_ID(type2, name2) + +resulting in following layout in .BTF.ids section:: + + __BTF_ID__type1__name1__1: + .zero 4 + __BTF_ID__type2__name2__2: + .zero 4 + +The ``int list[];`` variable is defined to access the list. + +The ``BTF_ID_UNUSED`` macro defines 4 zero bytes. It's used when we +want to define unused entry in BTF_ID_LIST, like:: + + BTF_ID_LIST(bpf_skb_output_btf_ids) + BTF_ID(struct, sk_buff) + BTF_ID_UNUSED + BTF_ID(struct, task_struct) + +All the BTF ID lists and sets are compiled in the .BTF.ids section and +resolved during the linking phase of kernel build by ``resolve_btfids`` tool. + 5. Using BTF ************ -- 2.25.4