qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Andrew Melnichenko <andrew@daynix.com>
Cc: mst@redhat.com, armbru@redhat.com, eblake@redhat.com,
	 qemu-devel@nongnu.org, berrange@redhat.com,
	yuri.benditovich@daynix.com,  yan@daynix.com,
	akihiko.odaki@daynix.com
Subject: Re: [PATCH v9 4/5] qmp: Added new command to retrieve eBPF blob.
Date: Wed, 13 Mar 2024 13:05:14 +0800	[thread overview]
Message-ID: <CACGkMEseH32rxhpWkBshe+d8YArbmTL60d8C9Rd0sXV5PYziVQ@mail.gmail.com> (raw)
In-Reply-To: <CABcq3pEQ9-RW5w+4gOaQJZbcPuYnFjoVk6axoj4g53OArbso+w@mail.gmail.com>

On Wed, Mar 13, 2024 at 7:13 AM Andrew Melnichenko <andrew@daynix.com> wrote:
>
> Hi all,
> I've checked - apparently, qapi/ebpf.json should be added to
> MAINTAINERS - I'll fix it.

I've fixed this by myself and the pull request has been merged.

Thanks

>
> On Fri, Mar 8, 2024 at 10:14 AM Jason Wang <jasowang@redhat.com> wrote:
> >
> > On Tue, Feb 6, 2024 at 12:55 AM Andrew Melnychenko <andrew@daynix.com> wrote:
> > >
> > > Now, the binary objects may be retrieved by id.
> > > It would require for future qmp commands that may require specific
> > > eBPF blob.
> > >
> > > Added command "request-ebpf". This command returns
> > > eBPF program encoded base64. The program taken from the
> > > skeleton and essentially is an ELF object that can be
> > > loaded in the future with libbpf.
> > >
> > > The reason to use the command to provide the eBPF object
> > > instead of a separate artifact was to avoid issues related
> > > to finding the eBPF itself. eBPF object is an ELF binary
> > > that contains the eBPF program and eBPF map description(BTF).
> > > Overall, eBPF object should contain the program and enough
> > > metadata to create/load eBPF with libbpf. As the eBPF
> > > maps/program should correspond to QEMU, the eBPF can't
> > > be used from different QEMU build.
> > >
> > > The first solution was a helper that comes with QEMU
> > > and loads appropriate eBPF objects. And the issue is
> > > to find a proper helper if the system has several
> > > different QEMUs installed and/or built from the source,
> > > which helpers may not be compatible.
> > >
> > > Another issue is QEMU updating while there is a running
> > > QEMU instance. With an updated helper, it may not be
> > > possible to hotplug virtio-net device to the already
> > > running QEMU. Overall, requesting the eBPF object from
> > > QEMU itself solves possible failures with acceptable effort.
> > >
> > > Links:
> > > [PATCH 3/5] qmp: Added the helper stamp check.
> > > https://lore.kernel.org/all/20230219162100.174318-4-andrew@daynix.com/
> > >
> > > Signed-off-by: Andrew Melnychenko <andrew@daynix.com>
> > > ---
> > >  ebpf/ebpf.c           | 69 +++++++++++++++++++++++++++++++++++++++++++
> >
> > Let's add ebpf.c to MAINTAINERS otherwise CI may warn like:
> >
> > https://gitlab.com/jasowang/qemu/-/jobs/6349138969
> >
> > Thanks
> >
>



  reply	other threads:[~2024-03-13  5:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 16:54 [PATCH v9 0/5] eBPF RSS through QMP support Andrew Melnychenko
2024-02-05 16:54 ` [PATCH v9 1/5] ebpf: Added eBPF map update through mmap Andrew Melnychenko
2024-02-05 16:54 ` [PATCH v9 2/5] ebpf: Added eBPF initialization by fds Andrew Melnychenko
2024-02-05 16:54 ` [PATCH v9 3/5] virtio-net: Added property to load eBPF RSS with fds Andrew Melnychenko
2024-02-05 16:54 ` [PATCH v9 4/5] qmp: Added new command to retrieve eBPF blob Andrew Melnychenko
2024-02-21 12:30   ` Markus Armbruster
2024-03-08  8:14   ` Jason Wang
2024-03-12 22:47     ` Andrew Melnichenko
2024-03-13  5:05       ` Jason Wang [this message]
2024-02-05 16:54 ` [PATCH v9 5/5] ebpf: Updated eBPF program and skeleton Andrew Melnychenko
2024-02-26 10:23 ` [PATCH v9 0/5] eBPF RSS through QMP support Andrew Melnichenko
2024-03-08  6:30   ` Jason Wang
2024-03-08  8:06     ` Jason Wang
2024-03-12 22:45       ` Andrew Melnichenko
2024-03-13  5:06         ` Jason Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACGkMEseH32rxhpWkBshe+d8YArbmTL60d8C9Rd0sXV5PYziVQ@mail.gmail.com \
    --to=jasowang@redhat.com \
    --cc=akihiko.odaki@daynix.com \
    --cc=andrew@daynix.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yan@daynix.com \
    --cc=yuri.benditovich@daynix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).