On Sun, 2 May 2021 at 20:55, Sean Anderson seanga2@gmail.com wrote:
Valgrind uses magic code sequences to define an ABI that the client may use to request behavior from the host. In particular, this may be used to inform valgrind about custom allocators, such as the one used in U-Boot.
This adds headers defining these sequences to U-Boot. It also adds a config option to disable emission of these sequences entirely, in the (likely) event that the user does not wish to use valgrind. Note that this option was originally called NVALGRIND, but was renamed (and inverted) to CONFIG_VALGRIND.
These headers were copied from valgrind 3.16.1-4 as distributed in Arch Linux. They are licensed with the bzip2 1.16 license. This appears to be a BSD license with some clauses from Zlib.
Signed-off-by: Sean Anderson seanga2@gmail.com
Kconfig | 14 + Licenses/README | 1 + Licenses/bzip2-1.0.6.txt | 30 + include/valgrind/memcheck.h | 251 ++ include/valgrind/valgrind.h | 7106 +++++++++++++++++++++++++++++++++++ 5 files changed, 7402 insertions(+) create mode 100644 Licenses/bzip2-1.0.6.txt create mode 100644 include/valgrind/memcheck.h create mode 100644 include/valgrind/valgrind.h
Reviewed-by: Simon Glass sjg@chromium.org