From: Francis Laniel <flaniel@linux.microsoft.com>
To: buildroot@buildroot.org
Cc: Francis Laniel <flaniel@linux.microsoft.com>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>
Subject: [Buildroot] [PATCH 0/2] Bump sysdig to 0.29.2
Date: Tue, 3 May 2022 15:26:59 +0100 [thread overview]
Message-ID: <20220503142701.14397-1-flaniel@linux.microsoft.com> (raw)
Hi.
In my last contribution, I wrote a mistake in sysdig.mk which leaded DRIVER_NAME
to be empty [1]...
(The machine where I built is not the same than the one where I wrote and send
the patch...)
So, in this series, I fixed my previous error and bumped sysdig to its latest
version.
I was, of course, able to build and run sysdig within a VM based on
qemu_x86_64_defconfig:
Welcome to Buildroot
buildroot login: root
# sysdig --version
sysdig version 0.29.2
# sysdig | head
scap: loading out-of-tree module taints kernel.
scap: driver loading, scap
scap: adding new consumer (____ptrval____)
scap: initializing ring buffer for CPU 0
scap: CPU buffer initialized, size=8388608
scap: starting capture
4 14:21:45.440896991 0 <NA> (114) > switch next=10 pgft_maj=7 pgft_min=1300 vm_size=45464 vm_rss=18460 vm_swap=0
...
91 14:21:45.449639600 0 <NA> (0) > switch next=114(<NA>) pgft_maj=0 pgft_min=0 vm_size=0 vm_rss=0 vm_swap=0
scap: deallocating consumer (____ptrval____)
scap: no more consumers, stopping capture
If you see any way to improve this contribution, feel free to share it!
Francis Laniel (2):
package/sysdig: fix DRIVER_NAME definition
package/sysdig: bump to version 0.29.2
package/sysdig/sysdig.hash | 2 +-
package/sysdig/sysdig.mk | 7 ++++---
2 files changed, 5 insertions(+), 4 deletions(-)
Best regards and thank you in advance.
---
[1] https://git.buildroot.net/buildroot/commit/?id=ea86757e51cf424566f79896335d31d15b89d0d9
--
2.25.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-05-03 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 14:26 Francis Laniel [this message]
2022-05-03 14:27 ` [Buildroot] [PATCH 1/2] package/sysdig: fix DRIVER_NAME definition Francis Laniel
2022-05-03 19:15 ` Yann E. MORIN
2022-05-03 14:27 ` [Buildroot] [PATCH 2/2] package/sysdig: bump to version 0.29.2 Francis Laniel
2022-05-03 19:22 ` Yann E. MORIN
2022-05-04 12:28 ` Francis Laniel
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=20220503142701.14397-1-flaniel@linux.microsoft.com \
--to=flaniel@linux.microsoft.com \
--cc=angelo.compagnucci@gmail.com \
--cc=buildroot@buildroot.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