From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: juhapekka.heikkila@gmail.com,
Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>,
igt-dev@lists.freedesktop.org
Cc: juha-pekka.heikkila@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t] igt/tests: Clear pipes properly in kms_atomic_transition
Date: Tue, 30 Jun 2020 14:13:33 +0200 [thread overview]
Message-ID: <1dff87a1-7636-86a6-d8fe-b31931327e85@linux.intel.com> (raw)
In-Reply-To: <79815182-5f59-cdb3-75da-741042273457@gmail.com>
Op 23-06-2020 om 17:07 schreef Juha-Pekka Heikkila:
> On 23.6.2020 16.53, Stanislav Lisovskiy wrote:
>> There is an issue happening from time to time in kms_atomic_transition
>> (bug #1918). We periodically get assertion that some two outputs
>> attempt to use same pipe like this:
>>
>> "Failed assertion: output->pending_pipe != b->pending_pipe"
>>
>> After some investigation came to conclusion that this is happening
>> because we are calling igt_output_set_pipe(output, PIPE_NONE) only
>> for connected outputs, which is wrong.
>> Periodically igt_display_refresh/igt_output_refresh call calls can
>> update the output state to disconnected. However that doesn't clear
>> the pipe being assigned(i.e output->pending_pipe).
>> So this causes assertion to be triggered on next igt_display_refresh
>> called during commit.
>>
>> Bugzilla: https://gitlab.freedesktop.org/drm/intel/-/issues/1918
>>
>> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
>> ---
>> tests/kms_atomic_transition.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/tests/kms_atomic_transition.c b/tests/kms_atomic_transition.c
>> index 754a4969..a55388cd 100644
>> --- a/tests/kms_atomic_transition.c
>> +++ b/tests/kms_atomic_transition.c
>> @@ -665,8 +665,9 @@ static unsigned set_combinations(igt_display_t *display, unsigned mask, struct i
>> enum pipe pipe;
>> unsigned event_mask = 0;
>> - for_each_connected_output(display, output)
>> - igt_output_set_pipe(output, PIPE_NONE);
>> + for_each_pipe(display, pipe)
>> + for_each_valid_output_on_pipe(display, pipe, output)
>> + igt_output_set_pipe(output, PIPE_NONE);
>> for_each_pipe(display, pipe) {
>> igt_plane_t *plane = igt_pipe_get_plane_type(&display->pipes[pipe],
>>
>
> Look ok to me.
>
> Reviewed-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
Nack, for_each_valid_output_on_pipe uses for_each_connected_output, so you keep the bug..
for (i = 0; i < display->n_outputs; i++)
igt_output_set_pipe(&display->outputs[i], PIPE_NONE); ?
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-06-30 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 13:53 [igt-dev] [PATCH i-g-t] igt/tests: Clear pipes properly in kms_atomic_transition Stanislav Lisovskiy
2020-06-23 15:00 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-06-23 15:07 ` [igt-dev] [PATCH i-g-t] " Juha-Pekka Heikkila
2020-06-30 12:13 ` Maarten Lankhorst [this message]
2020-06-30 13:11 ` Lisovskiy, Stanislav
2020-06-23 21:56 ` [igt-dev] ✓ Fi.CI.IGT: success 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=1dff87a1-7636-86a6-d8fe-b31931327e85@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juha-pekka.heikkila@intel.com \
--cc=juhapekka.heikkila@gmail.com \
--cc=stanislav.lisovskiy@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