From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Andrew Melnychenko <andrew@daynix.com>
Cc: jasowang@redhat.com, mst@redhat.com, armbru@redhat.com,
eblake@redhat.com, qemu-devel@nongnu.org,
yuri.benditovich@daynix.com, yan@daynix.com
Subject: Re: [PATCH v5 4/5] qmp: Added new command to retrieve eBPF blob.
Date: Thu, 3 Aug 2023 15:16:23 +0100 [thread overview]
Message-ID: <ZMu2t/egT5giMXk4@redhat.com> (raw)
In-Reply-To: <20230802204125.33688-5-andrew@daynix.com>
On Wed, Aug 02, 2023 at 11:41:22PM +0300, Andrew Melnychenko 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 | 70 +++++++++++++++++++++++++++++++++++++++++++
> ebpf/ebpf.h | 31 +++++++++++++++++++
> ebpf/ebpf_rss.c | 6 ++++
> ebpf/meson.build | 2 +-
> qapi/ebpf.json | 57 +++++++++++++++++++++++++++++++++++
> qapi/meson.build | 1 +
> qapi/qapi-schema.json | 1 +
> 7 files changed, 167 insertions(+), 1 deletion(-)
> create mode 100644 ebpf/ebpf.c
> create mode 100644 ebpf/ebpf.h
> create mode 100644 qapi/ebpf.json
> diff --git a/qapi/ebpf.json b/qapi/ebpf.json
> new file mode 100644
> index 00000000000..40851f8c177
> --- /dev/null
> +++ b/qapi/ebpf.json
> @@ -0,0 +1,57 @@
> +# -*- Mode: Python -*-
> +# vim: filetype=python
> +#
> +# This work is licensed under the terms of the GNU GPL, version 2 or later.
> +# See the COPYING file in the top-level directory.
> +
> +##
> +# = eBPF Objects
> +##
> +
> +{ 'include': 'common.json' }
> +
> +##
> +# @EbpfObject:
> +#
> +# Structure that holds eBPF ELF object encoded in base64.
> +#
> +# Since: 8.3
We're just releasing 8.1, so next will be 8.2
There will never be any 8.3 because we reset to next major
version in the first release of each year.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-08-03 14:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 20:41 [PATCH v5 0/5] eBPF RSS through QMP support Andrew Melnychenko
2023-08-02 20:41 ` [PATCH v5 1/5] ebpf: Added eBPF map update through mmap Andrew Melnychenko
2023-08-08 2:39 ` Jason Wang
2023-08-08 23:15 ` Andrew Melnichenko
2023-08-09 2:21 ` Jason Wang
2023-08-14 8:36 ` Andrew Melnichenko
2023-08-16 1:16 ` Jason Wang
2023-08-18 2:07 ` Andrew Melnichenko
2023-08-21 3:57 ` Jason Wang
2023-08-02 20:41 ` [PATCH v5 2/5] ebpf: Added eBPF initialization by fds Andrew Melnychenko
2023-08-02 20:41 ` [PATCH v5 3/5] virtio-net: Added property to load eBPF RSS with fds Andrew Melnychenko
2023-08-02 20:41 ` [PATCH v5 4/5] qmp: Added new command to retrieve eBPF blob Andrew Melnychenko
2023-08-03 14:16 ` Daniel P. Berrangé [this message]
2023-08-05 7:34 ` Markus Armbruster
2023-08-08 17:43 ` Andrew Melnichenko
2023-08-21 17:15 ` Markus Armbruster
2023-08-02 20:41 ` [PATCH v5 5/5] ebpf: Updated eBPF program and skeleton Andrew Melnychenko
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=ZMu2t/egT5giMXk4@redhat.com \
--to=berrange@redhat.com \
--cc=andrew@daynix.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jasowang@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).