From: vitaly prosyak <vprosyak@amd.com>
To: "Peter Senna Tschudin" <peter.senna@linux.intel.com>,
"Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>,
"Strawbridge, Michael" <Michael.Strawbridge@amd.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 22:17:30 -0500 [thread overview]
Message-ID: <b93fa221-a368-4d98-b5e6-3539ba68d6ca@amd.com> (raw)
In-Reply-To: <c4c07559-0bd7-4d77-a890-309b3f772359@linux.intel.com>
On 2025-02-27 05:27, Peter Senna Tschudin wrote:
> Hello again Vitaly,
>
> [...]
>
>> 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?
>>
>> sudo ./scripts/run-tests.sh -t -v /home/vprosyak/src/igt-gpu-tools/build/tests/amd/amd_basic
> I’ve sent another revision of the patch that updates scripts/run-tests.sh,
> adding the -K option. This allows you to run tests like this:
>
> sudo ./scripts/run-tests.sh -K each -t -v /home/vprosyak/src/igt-gpu-tools/build/tests/amd/amd_basic
>
>> or
>>
>> sudo ./scripts/run-tests.sh -v -T /home/infra/igt/custom.testlist
> Same here:
>
> sudo ./scripts/run-tests.sh -v -K each -T /home/infra/igt/custom.testlist
>
> You can find the patch here: https://patchwork.freedesktop.org/series/143996/
Hi Peter,
Feel free to use:
Reviewed-by: Vitaly Prosyak <vitaly.prosyak@amd.com>
for your three patches. We truly appreciate your work, and we're eagerly awaiting your merge!
The key point is that it shouldn't introduce any regressions since the -keach or -konce options will be disabled by default. Once we enable it and put CI under pressure, we might uncover some surprises—potentially false-positive leaks. If that happens, we can try resolving them by issuing the scan and clear commands twice.
Let’s see how it plays out! Thanks again for your effort.
Thanks, Vitaly
>
> Would you be open to reviewing the new patch and sending your Reviewed-by
> once you think it’s ready? That would help speed up the merge process.
>
> Let me know if I can assist in any way.
>
> Cheers,
>
> Peter
prev parent reply other threads:[~2025-02-28 3:17 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
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 [this message]
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=b93fa221-a368-4d98-b5e6-3539ba68d6ca@amd.com \
--to=vprosyak@amd.com \
--cc=Michael.Strawbridge@amd.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=peter.senna@linux.intel.com \
--cc=vitaly.prosyak@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