All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v2 0/2] gpudev: annotate memory allocation functions
Date: Mon, 28 Oct 2024 12:01:01 -0700	[thread overview]
Message-ID: <20241028190301.264378-1-stephen@networkplumber.org> (raw)
In-Reply-To: <20241017225844.235401-1-stephen@networkplumber.org>

Use function attributes to catch misuse of GPU memory
at compile time.

v2 - remove test case where invalid pointer was being passed.
     The test is now caught at compile time, making a runtime test
     no longer necessary.

Stephen Hemminger (2):
  test-gpudev: avoid use-after-free and free-non-heap warnings
  gpudev: add malloc annotations to rte_gpu_mem_alloc

 app/test-gpudev/main.c  | 16 +++-----------
 lib/gpudev/rte_gpudev.h | 46 +++++++++++++++++++++--------------------
 2 files changed, 27 insertions(+), 35 deletions(-)

-- 
2.45.2


  parent reply	other threads:[~2024-10-28 19:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17 22:58 [PATCH 0/2] gpudev: annotate memory allocation Stephen Hemminger
2024-10-17 22:58 ` [PATCH 1/2] test-gpudev: avoid use-after-free and free-non-heap warnings Stephen Hemminger
2024-10-17 22:58 ` [PATCH 2/2] gpudev: add malloc annotations to rte_gpu_mem_alloc Stephen Hemminger
2024-10-28 19:01 ` Stephen Hemminger [this message]
2024-10-28 19:01   ` [PATCH v2 1/2] test-gpudev: avoid use-after-free and free-non-heap warnings Stephen Hemminger
2024-10-28 19:01   ` [PATCH v2 2/2] gpudev: add malloc annotations to rte_gpu_mem_alloc Stephen Hemminger
2024-11-08 14:36   ` [PATCH v2 0/2] gpudev: annotate memory allocation functions David Marchand
2024-11-09  0:22 ` [PATCH 0/2] gpudev: annotate memory allocation Stephen Hemminger

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=20241028190301.264378-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.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 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.