On Mon, Sep 30, 2019 at 12:12 AM Toke Høiland-Jørgensen wrote:
>
> Andrii Nakryiko writes:
>
> > On Fri, Sep 27, 2019 at 6:11 AM KP Singh wrote:
> >>
> >> From: KP Singh
> >>
> >> Introduce struct bpf_object_open_buffer_attr and an API function,
> >> bpf_object__open_xattr, as the existing API,
Thanks for the feeback!
I will be happy to update this patch once there is consensus about
the design of the API for future additions.
On 30-Sep 09:12, Toke Høiland-Jørgensen wrote:
> Andrii Nakryiko writes:
>
> > On Fri, Sep 27, 2019 at 6:11 AM KP Singh wrote:
> >>
> >> From: KP Singh
> >>
>
Andrii Nakryiko writes:
> On Fri, Sep 27, 2019 at 6:11 AM KP Singh wrote:
>>
>> From: KP Singh
>>
>> Introduce struct bpf_object_open_buffer_attr and an API function,
>> bpf_object__open_xattr, as the existing API, bpf_object__open_buffer,
>> doesn't provide a way to specify neither the "needs_
On Fri, Sep 27, 2019 at 6:11 AM KP Singh wrote:
>
> From: KP Singh
>
> Introduce struct bpf_object_open_buffer_attr and an API function,
> bpf_object__open_xattr, as the existing API, bpf_object__open_buffer,
> doesn't provide a way to specify neither the "needs_kver" nor
> the "flags" parameter
From: KP Singh
Introduce struct bpf_object_open_buffer_attr and an API function,
bpf_object__open_xattr, as the existing API, bpf_object__open_buffer,
doesn't provide a way to specify neither the "needs_kver" nor
the "flags" parameter to the internal call to the
__bpf_object__open which makes it
5 matches
Mail list logo