Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: "Sharma, Swati2" <swati2.sharma@intel.com>,
	"Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Heikkila, Juha-pekka" <juha-pekka.heikkila@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v2] igt/tests: Clear pipes properly in kms_atomic_transition
Date: Fri, 10 Jul 2020 13:21:18 +0000	[thread overview]
Message-ID: <0c6cb49a813848a4b99859f336d3ba54@intel.com> (raw)
In-Reply-To: <f067c7eb-df2a-e5f4-efdf-551682c30790@intel.com>

I couldn't find the patchwork link, can someone forward link to the results?

Thanks,
Lakshmi.

-----Original Message-----
From: Sharma, Swati2 <swati2.sharma@intel.com> 
Sent: Friday, July 10, 2020 3:13 PM
To: Lisovskiy, Stanislav <stanislav.lisovskiy@intel.com>; igt-dev@lists.freedesktop.org
Cc: Heikkila, Juha-pekka <juha-pekka.heikkila@intel.com>; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v2] igt/tests: Clear pipes properly in kms_atomic_transition

Thanks for the patch. Pushed.
There is regression seen in kms_vblank; but its not related to changes in the patch.
@lakshmi can you please re-report?

On 30-Jun-20 6:54 PM, 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
> 
> v2: - Do not use for_each_valid_output_on_pipe as it also iterates
>        only on connected outputs(Maarten)
>      - Also fix run_modeset_tests function
> 
> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> ---
>   tests/kms_atomic_transition.c | 10 ++++++----
>   1 file changed, 6 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/kms_atomic_transition.c 
> b/tests/kms_atomic_transition.c index 754a4969..656bd51e 100644
> --- a/tests/kms_atomic_transition.c
> +++ b/tests/kms_atomic_transition.c
> @@ -664,9 +664,10 @@ static unsigned set_combinations(igt_display_t *display, unsigned mask, struct i
>   	igt_output_t *output;
>   	enum pipe pipe;
>   	unsigned event_mask = 0;
> +	int i;
>   
> -	for_each_connected_output(display, output)
> -		igt_output_set_pipe(output, PIPE_NONE);
> +	for (i = 0; i < display->n_outputs; i++)
> +		igt_output_set_pipe(&display->outputs[i], PIPE_NONE);
>   
>   	for_each_pipe(display, pipe) {
>   		igt_plane_t *plane = 
> igt_pipe_get_plane_type(&display->pipes[pipe],
> @@ -743,11 +744,12 @@ static void run_modeset_tests(igt_display_t *display, int howmany, bool nonblock
>   	igt_output_t *output;
>   	unsigned width = 0, height = 0;
>   
> +	for (i = 0; i < display->n_outputs; i++)
> +		igt_output_set_pipe(&display->outputs[i], PIPE_NONE);
> +
>   	for_each_connected_output(display, output) {
>   		drmModeModeInfo *mode = igt_output_get_mode(output);
>   
> -		igt_output_set_pipe(output, PIPE_NONE);
> -
>   		width = max(width, mode->hdisplay);
>   		height = max(height, mode->vdisplay);
>   	}
> 

--
~Swati Sharma
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-07-10 13:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 13:24 [igt-dev] [PATCH i-g-t v2] igt/tests: Clear pipes properly in kms_atomic_transition Stanislav Lisovskiy
2020-06-30 13:47 ` [igt-dev] ✓ Fi.CI.BAT: success for igt/tests: Clear pipes properly in kms_atomic_transition (rev2) Patchwork
2020-06-30 17:09 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-07-08 13:40 ` [igt-dev] [PATCH i-g-t v2] igt/tests: Clear pipes properly in kms_atomic_transition Maarten Lankhorst
2020-07-10 13:12 ` Sharma, Swati2
2020-07-10 13:21   ` Vudum, Lakshminarayana [this message]
2020-07-10 14:11 ` [igt-dev] ✓ Fi.CI.IGT: success for igt/tests: Clear pipes properly in kms_atomic_transition (rev2) 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=0c6cb49a813848a4b99859f336d3ba54@intel.com \
    --to=lakshminarayana.vudum@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=juha-pekka.heikkila@intel.com \
    --cc=stanislav.lisovskiy@intel.com \
    --cc=swati2.sharma@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