Re: [PATCH bpf-next v3 0/2] libbpf: Extend linker API to support in-memory ELF files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@xxxxxxxxxx>:

On Wed, 11 Dec 2024 08:40:28 -0800 you wrote:
> This gives API consumers the option of using anonymous files/memfds to
> avoid writing temporary ELFs to disk, which will be useful for performing
> linking as part of bpftrace's JIT compilation.
> 
> v3:
> - Removed "filename" option. Now always generate our own filename for
>   passed-in FDs and buffers.
> - Use a common function (bpf_linker_add_file) for shared
>   implementation of bpf_linker__add_file, bpf_linker__add_fd and
>   bpf_linker__add_buf.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/2] libbpf: Pull file-opening logic up to top-level functions
    https://git.kernel.org/bpf/bpf-next/c/b641712925bf
  - [bpf-next,v3,2/2] libbpf: Extend linker API to support in-memory ELF files
    https://git.kernel.org/bpf/bpf-next/c/6d5e5e5d7ce1

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html






[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux