Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: katarzyna.piecielska@intel.com
Subject: kmemleaks and our CI
Date: Tue, 3 Dec 2024 17:48:59 +0100	[thread overview]
Message-ID: <734868cf-2f46-47b5-9f77-869164d50bb8@linux.intel.com> (raw)

Dear xe kernel driver developers,

I am looking into sane ways to integrate kmemleaks with our CI. By sane I mean ways that will help us find and fix leaks while not overwhelming us with noise and our DUTs with unnecessary load.

It came to my attention that we may be running _all_ our CI tests with kmemleak enabled and scanning. To me this has two problems. The first is that it slows down memory allocation and freeing, no big deal.

The second problem however, is that if all our CI tests are indeed running with kmemleak enabled and scanning, it means that we are not testing our drivers in a kernel without kmemleak. I don't have numbers, but I assume that a large portion of real world use cases will have kmemleak disabled.

Is it a problem to run all our CI tests with kmemleak enabled and scanning?

Thanks,

Peter

             reply	other threads:[~2024-12-03 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 16:48 Peter Senna Tschudin [this message]
2024-12-04 22:37 ` kmemleaks and our CI Lucas De Marchi

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=734868cf-2f46-47b5-9f77-869164d50bb8@linux.intel.com \
    --to=peter.senna@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=katarzyna.piecielska@intel.com \
    /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