public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Neel Desai <neel.desai@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH v2 1/1] tests/kms_cursor_legacy: Skip 2x-cursor-vs-flip subtests for gen > 9
Date: Tue, 12 Mar 2019 18:44:41 +0200	[thread overview]
Message-ID: <20190312164441.GG3888@intel.com> (raw)
In-Reply-To: <a8cc9404b98e3bd6359783dcdf38618c3db0de24.1552406927.git.neel.desai@intel.com>

On Tue, Mar 12, 2019 at 09:12:44AM -0700, Neel Desai wrote:
> Due to DDB allocation changes, we have to add all the planes to the
> drm_atomic_state post gen 9.

As we discussed on irc that is not true. The cursor has a fixed
allocation and thus never needs to be added to the state on account
of ddb allocation changing (except for full modesets). So the real
reason for the cursor being added to the state is something else.
I think the answer has something more to do with the selected
max watermark level.

Also I'm not entirely convinced that the fixed allocation scheme
is working quite right currently. We never seem to check that we
actually have enough ddb space for the selected max watermark
level for the cursor. We should add such a check, and we also may
have to change how we calculate the size of the fixed cursor ddb
allocation to make sure the cursor isn't needlessly limiting the
max watermark level we can use.

> When the watermarks are computed by the
> kernel, the cursor plane is added to the drm_atomic_state which
> introduces a dependency on hw_done object when the kernel processes
> DRM_IOCTL_MODE_ATOMIC and DRM_IOCTL_MODE_CURSOR in parallel. There is no
> race-free way to handle this corner case. These subtests made sense for
> older generations but not anymore. Hence, skipping these sub-tests post
> gen 9.
> 
> Reference: https://bugs.freedesktop.org/show_bug.cgi?id=109079
> Signed-off-by: Neel Desai <neel.desai@intel.com>
> cc: Sudeep Dutt <sudeep.dutt@intel.com>
> cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> ---
>  tests/kms_cursor_legacy.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/tests/kms_cursor_legacy.c b/tests/kms_cursor_legacy.c
> index d6987eea..645c0b93 100644
> --- a/tests/kms_cursor_legacy.c
> +++ b/tests/kms_cursor_legacy.c
> @@ -1115,6 +1115,7 @@ static void cursor_vs_flip(igt_display_t *display, enum flip_test mode, int nloo
> 
>  static void two_screens_cursor_vs_flip(igt_display_t *display, int nloops, bool atomic)
>  {
> +	const int gen = intel_gen(intel_get_drm_devid(display->drm_fd));
>  	struct drm_mode_cursor arg[2][2];
>  	struct drm_event_vblank vbl;
>  	struct igt_fb fb_info[2], cursor_fb;
> @@ -1126,6 +1127,8 @@ static void two_screens_cursor_vs_flip(igt_display_t *display, int nloops, bool
>  	};
>  	igt_output_t *outputs[2];
> 
> +	igt_require(gen <= 9);
> +
>  	shared = mmap(NULL, PAGE_SIZE, PROT_WRITE, MAP_SHARED | MAP_ANON, -1, 0);
>  	igt_assert(shared != MAP_FAILED);
> 
> --
> 2.17.1
> 
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev

-- 
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-03-12 16:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 16:12 [igt-dev] [PATCH v2 0/1] Skip 2x-cursor-vs-flip subtests for gen > 9 Neel Desai
2019-03-12 16:12 ` [igt-dev] [PATCH v2 1/1] tests/kms_cursor_legacy: " Neel Desai
2019-03-12 16:44   ` Ville Syrjälä [this message]
2019-03-12 16:46     ` Desai, Neel
2019-03-12 17:06       ` Ville Syrjälä
2019-03-12 17:16         ` Neel Desai
2019-03-12 21:01     ` Ville Syrjälä
2019-03-12 16:21 ` [igt-dev] [PATCH v2 0/1] " Chris Wilson
2019-03-12 16:26   ` Chris Wilson
2019-03-13 12:34 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-03-13 15:57 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20190312164441.GG3888@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=neel.desai@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