From: Vignesh Raman <vignesh.raman@collabora.com>
To: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>,
igt-dev@lists.freedesktop.org
Cc: helen.koike@collabora.com, daniels@collabora.com
Subject: Re: [igt-dev] [PATCH i-g-t] lib/igt_kms: Fix memory corruption
Date: Fri, 27 Oct 2023 17:28:56 +0530 [thread overview]
Message-ID: <0d1eb92d-1b39-9e95-da93-010f4e25241e@collabora.com> (raw)
In-Reply-To: <2b05e124-6772-ec09-1b50-f1dbfa860d57@intel.com>
Hi Bhanu,
On 27/10/23 15:25, Modem, Bhanuprakash wrote:
>> With the initial patch all-pipes subtest was passing.
>
> Looks, these tests are considering crtc count as display->n_pipes (16),
> but for_each_pipe() operates on IGT_MAX_PIPES (8) causing the failures.
>
>>
>>
>>>> - for (i = 0; i < resources->count_crtcs; i++) {
>>>> + for (i = 0; i < min(resources->count_crtcs, IGT_MAX_PIPES); i++) {
>>>
>>> With this change, we are missing the information of crtc index 7 to
>>> 15 in the display structure, aren't we?
>>
>> Yes agree. Do we need to fix the all-pipes subtest failure with your
>> proposed solution?
>
> IMHO, increasing IGT_MAX_PIPES to 16 would be the simplest solution.
>
> @@ -68,8 +68,15 @@ enum pipe {
> PIPE_D,
> PIPE_E,
> PIPE_F,
> PIPE_G,
> PIPE_H,
> + PIPE_I,
> + PIPE_J,
> + PIPE_K,
> + PIPE_L,
> + PIPE_M,
> + PIPE_N,
> + PIPE_O,
> IGT_MAX_PIPES
> };
Thanks for the suggestion. This works and all-pipes subtest passed. I
will run some tests and send v2 patch.
Regards,
Vignesh
next prev parent reply other threads:[~2023-10-27 11:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 2:20 [igt-dev] [PATCH i-g-t] lib/igt_kms: Fix memory corruption Vignesh Raman
2023-10-26 3:23 ` [igt-dev] ✓ CI.xeBAT: success for " Patchwork
2023-10-26 3:27 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-10-26 4:48 ` [igt-dev] [PATCH i-g-t] " Modem, Bhanuprakash
2023-10-26 9:45 ` Vignesh Raman
2023-10-27 9:55 ` Modem, Bhanuprakash
2023-10-27 11:58 ` Vignesh Raman [this message]
2023-10-27 7:38 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
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=0d1eb92d-1b39-9e95-da93-010f4e25241e@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=bhanuprakash.modem@intel.com \
--cc=daniels@collabora.com \
--cc=helen.koike@collabora.com \
--cc=igt-dev@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox