Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: "vitaly prosyak" <vprosyak@amd.com>,
	"Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	vitaly.prosyak@amd.com, igt-dev@lists.freedesktop.org,
	Christian Koenig <christian.koenig@amd.com>,
	Alexander Deucher <alexander.deucher@amd.com>,
	Jesse Zhang <jesse.zhang@amd.com>,
	Harry Wentland <harry.wentland@amd.com>
Subject: Re: [PATCH] lib/amd: add memleak functions
Date: Thu, 27 Feb 2025 10:08:10 +0100	[thread overview]
Message-ID: <dc46ac89-04da-49eb-be06-ce700d9c780e@linux.intel.com> (raw)
In-Reply-To: <2a494d9e-d771-4bd6-b328-517b7cc7dc50@amd.com>



On 27.02.2025 06:08, vitaly prosyak wrote:
[...]

Hi Vataly,

Thank you for your message.

> Hi Peter,
> 
> Thanks for the update! I really appreciate the effort you’ve put into making the approach more global and vendor-agnostic—great work!
> 
> It would be incredibly useful to have both --kmemleak options available (for the entire test list and individual tests).
> 
> Could you kindly provide guidance on how to add these options (-konce or -keach) to igt-runner? For example, how should I modify the following commands to include them?

The kmemleak patch has not been merged yet. If you'd like to try it before it
gets merged, you can find the patches here:

https://patchwork.freedesktop.org/series/143996/

Regarding the kmemleak integration, I apologize for any confusion in the
discussion. The intended usage is as follows:
 - Create a test list that includes only the tests you want kmemleak to
   scan.
 - Pass the -keach option to igt_runner.

> 
> sudo ./scripts/run-tests.sh -t -v /home/vprosyak/src/igt-gpu-tools/build/tests/amd/amd_basic

I'm assuming this script calls igt_runner. If so, please add -keach as an
additional command-line argument to igt_runner.

Once the patch is merged, this will enable igt_runner to generate a file
named kmemleak.txt in the results directory. The file will include entries
like:

 "kmemleaks found after running test@name"

to separate different scans within the same file.

Additionally, you can modify your test list to include only the tests you
want kmemleak to scan. This is where I unintentionally added noise to
the discussion.

Since you can create a custom test list and use it with -keach, there is
no need to extend the kmemleak library to support a separate test list.

> 
> or
> 
> sudo ./scripts/run-tests.sh -v -T /home/infra/igt/custom.testlist  
> 
> Thanks again for your great work and support!

Happy to help, let me know if you need anything else!

Peter

> 
> Vitaly
>> [...]


  reply	other threads:[~2025-02-27  9:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 11:43 [PATCH] lib/amd: add memleak functions vitaly.prosyak
2025-02-18 13:15 ` ✓ i915.CI.BAT: success for " Patchwork
2025-02-18 14:16 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-18 18:10 ` ✗ i915.CI.Full: failure " Patchwork
2025-02-19  1:16 ` [PATCH] " Zhang, Jesse(Jie)
2025-02-19  4:49 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-02-19 10:41 ` [PATCH] " Kamil Konieczny
2025-02-19 17:50   ` vitaly prosyak
2025-02-26  9:09     ` Zbigniew Kempczyński
2025-02-26  9:43       ` Peter Senna Tschudin
2025-02-26 10:09         ` Zbigniew Kempczyński
2025-02-26 10:24           ` Peter Senna Tschudin
2025-02-27  5:08             ` vitaly prosyak
2025-02-27  9:08               ` Peter Senna Tschudin [this message]
2025-02-27 10:53                 ` Kamil Konieczny
2025-02-27 11:13                   ` Peter Senna Tschudin
2025-02-28  3:01                 ` vitaly prosyak
2025-02-27 10:27               ` Peter Senna Tschudin
2025-02-28  3:17                 ` vitaly prosyak

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=dc46ac89-04da-49eb-be06-ce700d9c780e@linux.intel.com \
    --to=peter.senna@linux.intel.com \
    --cc=alexander.deucher@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=harry.wentland@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jesse.zhang@amd.com \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=vitaly.prosyak@amd.com \
    --cc=vprosyak@amd.com \
    --cc=zbigniew.kempczynski@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