All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matteo Croce" <mcroce@linux.microsoft.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>, Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] recipes-kernel: add libbpf
Date: Fri, 19 Feb 2021 00:04:41 +0100	[thread overview]
Message-ID: <CAFnufp1JF5te_Jq6HqYkvOT8rDJhEHKfn2V954X17gvH4p9eyA@mail.gmail.com> (raw)
In-Reply-To: <CADkTA4OsXBJk-a29_=Sx6-FBOgRAR7M3X+=RdVqju7PDLBFnmw@mail.gmail.com>

Okay, I've addressed all comments but the test one.

I pushed it to a local fork of meta-oe here:
https://github.com/teknoraver/meta-openembedded/commit/679944b06ffc564b4b99eae5d934f742bb2a9c09

Which kind of test needs to be done here?
A selftest to be run with oe-selftest? A ptest? A tool copied into the image?

If we just need to check if the bpf() syscall is supported, there is
bpftool packaged already, which can list the loaded programs like:

# bpftool prog
3: cgroup_device  tag 3a32ccd9e03ea87a  gpl
       loaded_at 2021-02-17T11:50:08+0100  uid 0
       xlated 504B  jited 309B  memlock 4096B
4: cgroup_skb  tag 6deef7357e7b4530  gpl
       loaded_at 2021-02-17T11:50:08+0100  uid 0
       xlated 64B  jited 54B  memlock 4096B
...

Regards,
-- 
per aspera ad upstream

  reply	other threads:[~2021-02-18 23:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 18:17 [PATCH] recipes-kernel: add libbpf Matteo Croce
2021-02-08 20:13 ` [OE-core] " Bruce Ashfield
2021-02-08 20:24   ` Bruce Ashfield
2021-02-08 21:22   ` Matteo Croce
2021-02-08 21:34     ` Bruce Ashfield
2021-02-09 16:44       ` Khem Raj
2021-02-09 17:02         ` Matteo Croce
2021-02-18  2:31   ` Matteo Croce
2021-02-18  3:51     ` Bruce Ashfield
2021-02-18 23:04       ` Matteo Croce [this message]
2021-02-22 16:54         ` Bruce Ashfield

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=CAFnufp1JF5te_Jq6HqYkvOT8rDJhEHKfn2V954X17gvH4p9eyA@mail.gmail.com \
    --to=mcroce@linux.microsoft.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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.