6a19373dc0
support for 64-bit RISC-V architecture, liveness analysis for guru-mode write operations,
bpf syscall_any and abort() tapsets, bpf foreach iteration of multi-key arrays,
return of inter-cpu output ordering
Changelog is as follows:
= SystemTap frontend (stap) changes
- stap-prep now tries to download the main kernel debuginfo file from
a debuginfod server, if configured.
= SystemTap backend changes
- SystemTap has added support for the 64-bit RISC-V architecture.
- SystemTap now uses DynInst to perform a liveness analysis on
target variables and warn when a guru-mode modification to a variable
will have no effect. The liveness analysis is currently done on
x86_64, PowerPC, and AArch64.
- The kernel-user relayfs transport again sorts messages into a total
time order across CPUs. High output-volume scripts may need a
larger "-s BUF" parameter to reliably transfer. "-b" bulk mode
is also available again as an alternative.
- The bpf backend now supports foreach iteration in multi-key associative arrays.
= SystemTap tapset changes
- Updated syscall_any tapset mapping to include newer syscalls.
- syscall_any tapset can be used by the bpf backend.
- abort() tapset can be used by the bpf backend.
= Known issues with this release
- There are known issues on kernel 5.10+ after adapting to set_fs()
removal, with some memory accesses that previously returned valid data
instead returning -EFAULT (see PR26811).
- An sdt probe cannot parse a parameter that uses a segment register.
(PR13429)
- The presence of a line such as
*CFLAGS += $(call cc-option, -fno-var-tracking-assignments)
in older linux kernel Makefile unnecessarily reduces debuginfo quality,
consider removing that line if you build kernels. Linux 5.10+ fixes this.
= Bugs fixed for this release <https://sourceware.org/PR#####>
6562 $SYSTEMTAP_DEBUGINFO_PATH does not work
15724 stapdyn looking for libdyninstAPI_RT.a
26839 Systemtap build failures with clang
27820 abort() tapset not implemented in the bpf mode
27829 support for floating point values passed through sdt.h markers
27864 loc2stap.cxx assertion failure on loc_unavailable type location, rawhide
27881 failed to extend vma mapped entry when the address is adjacent
27903 handle f33 glibc $$parms
27932 List Python as a prerequisite in README
27933 Use of unitialized functioncall synthetic field in
27934 failure to attach statement
27940 The /* pc=0x... */ is no longer printed by "stap -v -L 'kernel.function("*")'
27942 testsuite/systemtap.base/perf.sh drop bashism
27984 stap skipping partially-inlined instance, but it is not inline function actually
28070 extend vma end address to the different module
28079 adapt to kernel 5.14 task_struct.__state change
28084 autoconf-x86-uniregs.c compile failled with -Werror cause STAPCONF_X86_UNIREGS missing
28140 kernel panic on tracepoint activation in stap module
28184 task_fd_lookup failed on linux 5.11
28244 linux objtool imposes symbol length limits on generated function names
28384 finish nfs_proc tapset port 4.3 string server_ip
28443 Provide syscall_any tapset for bpf
28449 loss of cross-cpu output ordering
28544 procfs_bpf.exp regression due to string handling error
28557 module kprobe insertion on modern kernels
(From OE-Core rev: 99ed4a3d78f8224d414bd49d887333a4509529f3)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.
A guide to submitting patches to OpenEmbedded is available at:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
There is good documentation on how to write/format patches at:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.