From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Shreesh Adiga <16567adigashreesh@gmail.com>
Cc: qemu-devel@nongnu.org, jasowang@redhat.com, andrew@daynix.com,
yuri.benditovich@daynix.com
Subject: Re: [PATCH] ebpf: fix compatibility with libbpf 1.0+
Date: Mon, 19 Dec 2022 10:56:57 +0000 [thread overview]
Message-ID: <Y6BDeYCy309Ug4G5@redhat.com> (raw)
In-Reply-To: <20221218143927.597975-1-16567adigashreesh@gmail.com>
On Sun, Dec 18, 2022 at 08:09:27PM +0530, Shreesh Adiga wrote:
> The current implementation fails to load on a system with
> libbpf 1.0 and reports that legacy map definitions in 'maps'
> section are not supported by libbpf v1.0+. This commit updates
> the Makefile to add BTF (-g flag) and appropriately updates
> the maps in rss.bpf.c and update the skeleton file in repo.
Can you split this into two pieces - one updating the build
system for new compiler usage, and one updating the program
to remove the legacy map defs.
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:[~2022-12-19 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 14:39 [PATCH] ebpf: fix compatibility with libbpf 1.0+ Shreesh Adiga
2022-12-18 16:15 ` Philippe Mathieu-Daudé
2022-12-20 16:30 ` Shreesh Adiga
2022-12-28 16:19 ` Andrew Melnichenko
2023-02-14 20:10 ` Andrew Melnichenko
2023-02-16 5:28 ` Jason Wang
2022-12-19 10:56 ` Daniel P. Berrangé [this message]
2022-12-19 13:44 ` Shreesh Adiga
2022-12-19 13:49 ` Daniel P. Berrangé
2022-12-20 14:02 ` Shreesh Adiga
2022-12-20 14:05 ` Daniel P. Berrangé
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=Y6BDeYCy309Ug4G5@redhat.com \
--to=berrange@redhat.com \
--cc=16567adigashreesh@gmail.com \
--cc=andrew@daynix.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.