On Fri, Oct 22, 2021 at 12:18 PM Dave Marchevsky <davemarchevsky@xxxxxx> wrote: > > On 10/20/21 5:01 PM, Toke Høiland-Jørgensen wrote: > > Andrii Nakryiko <andrii.nakryiko@xxxxxxxxx> writes: > > > >> On Mon, Oct 11, 2021 at 1:20 AM Dave Marchevsky <davemarchevsky@xxxxxx> wrote: > >>> > >>> As part of the road to libbpf 1.0, and discussed in libbpf issue tracker > >>> [0], bpf_program__get_prog_info_linear and its associated structs and > >>> helper functions should be deprecated. The functionality is too specific > >>> to the needs of 'perf', and there's little/no out-of-tree usage to > >>> preclude introduction of a more general helper in the future. > >>> > >>> [0] Closes: https://github.com/libbpf/libbpf/issues/313 > >> > >> styling nit: don't know if it's described anywhere or not, but when > >> people do references like this, they use 2 spaces of indentation. No > >> idea how it came to be, but that's what I did for a while and see > >> others doing the same. > >> > >>> > >>> Signed-off-by: Dave Marchevsky <davemarchevsky@xxxxxx> > >>> --- > > [...] > > >> we can actually deprecate all this starting from v0.6, because perf is > >> building libbpf statically, so no worries about releases (also there > >> are no replacement APIs we have to wait full release for) > > > > Just FYI, we're also using this in libxdp, and that does link > > dynamically to libbpf. It's not an issue to move away from it[0], but > > perf is not the only user :) > > > > -Toke > > > > [0] Track that here: https://github.com/xdp-project/xdp-tools/issues/127 > > > > I submitted a PR to migrate the xdp-tools usage as well. Strange that > this didn't show up in an "all github" search. > > Andrii, should the DEPRECATED_SINCE stay at 0.7 in light of this? There is no replacement API that we need to wait to go through full libbpf release, so no, it can stay as is.
