All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH 1/4] Add valgrind headers to U-Boot
Date: Tue, 4 May 2021 09:26:09 -0600	[thread overview]
Message-ID: <CAPnjgZ0yipA+6LtuLmsYU2moxvO5KVQQ6psQXxcb=cp6Qdu27w@mail.gmail.com> (raw)
In-Reply-To: <20210503025516.1931890-2-seanga2@gmail.com>

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>

  reply	other threads:[~2021-05-04 15:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03  2:55 [PATCH 0/4] malloc: Enable profiling dlmalloc with valgrind Sean Anderson
2021-05-03  2:55 ` [PATCH 1/4] Add valgrind headers to U-Boot Sean Anderson
2021-05-04 15:26   ` Simon Glass [this message]
2021-05-03  2:55 ` [PATCH 2/4] malloc: Annotate allocator for valgrind Sean Anderson
2021-05-04 15:26   ` Simon Glass
2021-05-03  2:55 ` [PATCH 3/4] doc: sandbox: Document how to run sandbox with valgrind Sean Anderson
2021-05-04 15:26   ` Simon Glass
2021-05-04 23:23     ` Sean Anderson
2021-05-05 23:32       ` Simon Glass
2021-05-03  2:55 ` [PATCH 4/4] malloc: Fix sbrk clearing memory after freeing it instead of before Sean Anderson
2021-05-04 15:26   ` Simon Glass
2021-05-04 23:32     ` Sean Anderson

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='CAPnjgZ0yipA+6LtuLmsYU2moxvO5KVQQ6psQXxcb=cp6Qdu27w@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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.