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=-3.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=no 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 5E577C35254 for ; Mon, 17 Feb 2020 11:07:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 343FD207FD for ; Mon, 17 Feb 2020 11:07:23 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="fvhdaV0N" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727274AbgBQLHW (ORCPT ); Mon, 17 Feb 2020 06:07:22 -0500 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:46970 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726863AbgBQLHW (ORCPT ); Mon, 17 Feb 2020 06:07:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1581937641; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4meJ+9cGtIXsHFSQL1G0hT63jAf2xSIQo/UpbNAdilE=; b=fvhdaV0NNfIPezjxNs5364V2Vdz6ebK8LfQ7i7z2+MOQ2Hyvry4vAHUDzOkoYY46VCHwN7 tGMHlsi6MvSTH1d1pf0aYS7V4dV0iuVH/dwl+/f31iodDW4nA4ZQD4ay2jvi8awanJTrn6 pAuQqb1c7buWcJbrcftKuiEyKMnWN2Q= Received: from mail-lj1-f200.google.com (mail-lj1-f200.google.com [209.85.208.200]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-78-UVAPm0FLPz-IEPPphPW9MA-1; Mon, 17 Feb 2020 06:07:18 -0500 X-MC-Unique: UVAPm0FLPz-IEPPphPW9MA-1 Received: by mail-lj1-f200.google.com with SMTP id s25so5766948ljm.9 for ; Mon, 17 Feb 2020 03:07:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version:content-transfer-encoding; bh=4meJ+9cGtIXsHFSQL1G0hT63jAf2xSIQo/UpbNAdilE=; b=SjH9xjEk3IhrGTL+jl+qeYSkLm1qpeMOUKjM1vm5ZBzs7HC5vdEY4yubRDPefORFG7 SyNATad+Qer173qjQcNYKazyGAMRsPvmbH9gpzZaO/PjzTuQw7S4Jp90cc9kLpcm5Zsy pWFCuek3DRltbvVfqSg5OTSfyflcmzLzj/FBAvSBW1HpHAkcE9tdYvGXjzNnibdH9gSO yI5tVFnW3Xm15AGMXYIN9R5vlnPJlyTHuPYKexslqILc6IFoy+TMJUCjk3DjlzizOSfz wgsw/B6jwXVE3JXq+ANeAl+ogs5ULGUwVOUVM2XKJRQqoxsgZ7lQKHzlFypRBS6J5ZUT dDGA== X-Gm-Message-State: APjAAAWOOBtDPeOxyVT+U7eQfzTQZ0nq2taTJMCt9IphbssoKzsN26eJ CYAZmG7dZKOmK5jhOcdgBOChSxJ7PNxoF0ymN37JdByvK3vitNFQpJNhkllkfniAScJY3TUnvVF k0H8rfS93havx X-Received: by 2002:a2e:e12:: with SMTP id 18mr9901890ljo.123.1581937636845; Mon, 17 Feb 2020 03:07:16 -0800 (PST) X-Google-Smtp-Source: APXvYqwIPHCIs14g1Gu8hKPTMZVM4Wo6sviJJaYmXzxNaFPsm29lKGs9/zSmdLZZmKob3xGBzkcGNw== X-Received: by 2002:a2e:e12:: with SMTP id 18mr9901866ljo.123.1581937636587; Mon, 17 Feb 2020 03:07:16 -0800 (PST) Received: from alrua-x1.borgediget.toke.dk ([45.145.92.2]) by smtp.gmail.com with ESMTPSA id q10sm173109ljj.60.2020.02.17.03.07.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 17 Feb 2020 03:07:15 -0800 (PST) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 3D9931808E6; Mon, 17 Feb 2020 12:07:15 +0100 (CET) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Eelco Chaudron , bpf@vger.kernel.org Cc: davem@davemloft.net, netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net, kafai@fb.com, songliubraving@fb.com, yhs@fb.com, andriin@fb.com Subject: Re: [PATCH bpf-next v3] libbpf: Add support for dynamic program attach target In-Reply-To: <158193725120.96608.9449808053785640511.stgit@xdp-tutorial> References: <158193725120.96608.9449808053785640511.stgit@xdp-tutorial> X-Clacks-Overhead: GNU Terry Pratchett Date: Mon, 17 Feb 2020 12:07:15 +0100 Message-ID: <878sl1bhgc.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sender: bpf-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org Eelco Chaudron writes: > Currently when you want to attach a trace program to a bpf program > the section name needs to match the tracepoint/function semantics. > > However the addition of the bpf_program__set_attach_target() API > allows you to specify the tracepoint/function dynamically. > > The call flow would look something like this: > > xdp_fd =3D bpf_prog_get_fd_by_id(id); > trace_obj =3D bpf_object__open_file("func.o", NULL); > prog =3D bpf_object__find_program_by_title(trace_obj, > "fentry/myfunc"); > bpf_program__set_expected_attach_type(prog, BPF_TRACE_FENTRY); > bpf_program__set_attach_target(prog, xdp_fd, > "xdpfilt_blk_all"); > bpf_object__load(trace_obj) > > Signed-off-by: Eelco Chaudron Acked-by: Toke H=C3=B8iland-J=C3=B8rgensen