bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Seltzer Richman <grantseltzer@gmail.com>
To: bpf <bpf@vger.kernel.org>
Subject: Typical way to handle missing macros in vmlinux.h
Date: Wed, 28 Apr 2021 15:13:06 -0400	[thread overview]
Message-ID: <CAO658oV9AAcMMbVhjkoq5PtpvbVf41Cd_TBLCORTcf3trtwHfw@mail.gmail.com> (raw)

Hi all,

I'm working on enabling CO:RE in a project I work on, tracee, and am
running into the dilemma of missing macros that we previously were
able to import from their various header files. I understand that
macros don't make their way into BTF and therefore the generated
vmlinux.h won't have them. However I can't import the various header
files because of multiple-definition issues.

Do people typically redefine each of these macros for their project?
If so is there anything I should be careful of, such as architectural
differences. Does anyone have creative ideas, even if not developed
fully yet that I can possibly contribute to libbpf?

Thanks so much,
Grant Seltzer

             reply	other threads:[~2021-04-28 19:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 19:13 Grant Seltzer Richman [this message]
2021-04-28 21:15 ` Typical way to handle missing macros in vmlinux.h Andrii Nakryiko
2021-05-03 18:32   ` Grant Seltzer Richman
2021-05-03 18:43     ` Andrii Nakryiko
2021-05-03 20:20       ` Grant Seltzer Richman
2021-05-03 21:21         ` Andrii Nakryiko
2021-05-04 15:31           ` Grant Seltzer Richman
2021-05-04 16:24             ` Yonghong Song
2021-05-04 16:57               ` Grant Seltzer Richman
2021-05-04 22:31             ` Andrii Nakryiko

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=CAO658oV9AAcMMbVhjkoq5PtpvbVf41Cd_TBLCORTcf3trtwHfw@mail.gmail.com \
    --to=grantseltzer@gmail.com \
    --cc=bpf@vger.kernel.org \
    /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).