From: Daniel Vetter <daniel@ffwll.ch>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: IGT development <igt-dev@lists.freedesktop.org>,
Keith Packard <keithp@keithp.com>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 5/9] tests/kms_lease: test implicit primary plane usage in setcrtc ioctl
Date: Wed, 27 Mar 2019 10:21:15 +0100 [thread overview]
Message-ID: <20190327092115.GW2665@phenom.ffwll.local> (raw)
In-Reply-To: <20190327092623.2258f092@collabora.com>
On Wed, Mar 27, 2019 at 09:26:23AM +0100, Boris Brezillon wrote:
> On Thu, 28 Feb 2019 15:19:14 +0100
> Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>
> > Again we need to make sure that a lease can't use planes it's not
> > allowed to through legacy ioctls. SetCrtc is a bit more tricky, since
>
> ^ "to use through"?
Yup.
>
> > we should still allow to shut down a CRTC, e.g. when we're allowed to
> > use other planes on that CRTC.
> >
> > Current kernels fail this.
> >
> > Cc: Keith Packard <keithp@keithp.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> > ---
> > tests/kms_lease.c | 60 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 60 insertions(+)
> >
> > diff --git a/tests/kms_lease.c b/tests/kms_lease.c
> > index 6453c7beafd8..c11d37aeac7a 100644
> > --- a/tests/kms_lease.c
> > +++ b/tests/kms_lease.c
> > @@ -372,6 +372,65 @@ static void page_flip_implicit_plane(data_t *data)
> > connector_id_to_output(&data->master.display, data->connector_id));
> > }
> >
> > +static void setcrtc_implicit_plane(data_t *data)
> > +{
> > + uint32_t object_ids[3];
> > + struct local_drm_mode_create_lease mcl;
> > + drmModePlaneRes *plane_resources;
> > + uint32_t wrong_plane_id = 0;
> > + igt_output_t *output =
> > + connector_id_to_output(&data->master.display,
> > + data->connector_id);
> > + drmModeModeInfo *mode = igt_output_get_mode(output);
> > + int i;
> > +
> > + /* find a plane which isn't the primary one for us */
> > + plane_resources = drmModeGetPlaneResources(data->master.fd);
> > + for (i = 0; i < plane_resources->count_planes; i++) {
> > + if (plane_resources->planes[i] != data->plane_id) {
> > + wrong_plane_id = plane_resources->planes[i];
> > + break;
> > + }
> > + }
> > + drmModeFreePlaneResources(plane_resources);
> > + igt_require(wrong_plane_id);
>
> Maybe we could add an helper to retrieve wrong_plane_id instead of
> duplicating the code.
Hm, where is it duplicated? The other very similar loop looks for the
worng connector, and there's a few other loops to look for the right
plane/connector. I think they're all different.
>
> > +
> > + mcl.object_ids = (uint64_t) (uintptr_t) &object_ids[0];
> > + mcl.object_count = 0;
> > + mcl.flags = 0;
> > +
> > + object_ids[mcl.object_count++] = data->connector_id;
> > + object_ids[mcl.object_count++] = data->crtc_id;
> > +
> > + drmSetClientCap(data->master.fd, DRM_CLIENT_CAP_UNIVERSAL_PLANES, 0);
> > + do_or_die(create_lease(data->master.fd, &mcl));
> > + drmSetClientCap(data->master.fd, DRM_CLIENT_CAP_UNIVERSAL_PLANES, 1);
> > +
> > + /* Set a mode on the leased output */
> > + igt_assert_eq(0, prepare_crtc(&data->master, data->connector_id, data->crtc_id));
>
> Same goes for those create-lease+prepare-CRTC steps.
There's a helper for the common case, but for these "wrong" leases there's
always subtle differences. A helper would be be about as much code as just
open-coding it. Maybe we could move the UNIVERSAL_PLANES as a mode flag
into create_lease, but given how often I screamed at my tests for not
working because I got that one wrong, I think it's better to be explicit.
>
> > +
> > + /* sanity check */
> > + do_or_die(drmModeSetCrtc(data->master.fd, data->crtc_id, -1,
> > + 0, 0, object_ids, 1, mode));
> > + do_or_die(drmModeSetCrtc(mcl.fd, data->crtc_id, -1,
> > + 0, 0, object_ids, 1, mode));
> > + close(mcl.fd);
> > +
> > + object_ids[mcl.object_count++] = wrong_plane_id;
> > + do_or_die(create_lease(data->master.fd, &mcl));
> > +
> > + igt_assert_eq(drmModeSetCrtc(mcl.fd, data->crtc_id, -1,
> > + 0, 0, object_ids, 1, mode),
> > + -EACCES);
> > + /* make sure we are allowed to turn the CRTC off */
> > + do_or_die(drmModeSetCrtc(mcl.fd, data->crtc_id,
> > + 0, 0, 0, NULL, 0, NULL));
>
> Do we actually test the case where the lessor has setup the CRTC with a
> plane that's not accessible by the lesse. I think that's what you were
> trying to test here, but I don't see where it's done in the code.
> Shouldn't we have something like:
>
> do_or_die(drmModeSetCrtc(data->master.fd, data->crtc_id, -1,
> 0, 0, object_ids, 1, mode));
Sanity check above does exactly that.
> igt_assert_eq(0, drmModeSetCrtc(mcl.fd, data->crtc_id, 0, 0, 0,
> NULL, 0, NULL));
That's the line right above wrapped in the do_or_die.
> Looks good otherwise.
Cleared up with my comments above and r-b for the entire thing (with the
commit message fixed)?
-Daniel
>
> Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
>
> > + close(mcl.fd);
> > +
> > + cleanup_crtc(&data->master,
> > + connector_id_to_output(&data->master.display, data->connector_id));
> > +}
> > +
> > /* Test listing lessees */
> > static void lessee_list(data_t *data)
> > {
> > @@ -1086,6 +1145,7 @@ igt_main
> > { "lease_invalid_crtc", lease_invalid_crtc },
> > { "lease_invalid_plane", lease_invalid_plane },
> > { "page_flip_implicit_plane", page_flip_implicit_plane },
> > + { "setcrtc_implicit_plane", setcrtc_implicit_plane },
> > { }
> > }, *f;
> >
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-03-27 9:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 14:19 [igt-dev] [PATCH i-g-t 1/9] tests/kms_addfb_basic: Check that only the owner can rmfb Daniel Vetter
2019-02-28 14:19 ` [igt-dev] [PATCH i-g-t 2/9] tests:core_prop_blob: Drop local_ prefixes Daniel Vetter
2019-02-28 14:29 ` Ville Syrjälä
2019-02-28 14:19 ` [igt-dev] [PATCH i-g-t 3/9] tests: s/core_prop_blob/kms_prop_blob Daniel Vetter
2019-02-28 14:30 ` Ville Syrjälä
2019-02-28 14:19 ` [igt-dev] [PATCH i-g-t 4/9] tests/kms_lease: test implicit primary plane usage in page_flip ioctl Daniel Vetter
2019-03-27 8:04 ` Boris Brezillon
2019-02-28 14:19 ` [igt-dev] [PATCH i-g-t 5/9] tests/kms_lease: test implicit primary plane usage in setcrtc ioctl Daniel Vetter
2019-03-27 8:26 ` Boris Brezillon
2019-03-27 9:21 ` Daniel Vetter [this message]
2019-03-27 10:10 ` Boris Brezillon
2019-03-27 12:14 ` Daniel Vetter
2019-02-28 14:19 ` [igt-dev] [PATCH i-g-t 6/9] tests/kms_lease: test implicit cursor plane usage Daniel Vetter
2019-03-27 8:28 ` Boris Brezillon
2019-02-28 14:19 ` [igt-dev] [PATCH i-g-t 7/9] tests/kms_lease: Adjust to kernel errno changes Daniel Vetter
2019-03-27 8:29 ` Boris Brezillon
2019-02-28 14:19 ` [igt-dev] [PATCH i-g-t 8/9] tests/kms_lease: Handle new errno from idr/xa double insert Daniel Vetter
2019-03-27 8:30 ` Boris Brezillon
2019-02-28 14:19 ` [igt-dev] [PATCH i-g-t 9/9] tests/kms_lease: Check crtc used in atomic ioctl Daniel Vetter
2019-03-27 8:38 ` Boris Brezillon
2019-03-27 9:23 ` Daniel Vetter
2019-02-28 14:29 ` [igt-dev] [PATCH i-g-t 1/9] tests/kms_addfb_basic: Check that only the owner can rmfb Ville Syrjälä
2019-02-28 14:36 ` Chris Wilson
2019-02-28 15:44 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/9] " Patchwork
2019-02-28 18:05 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-03-28 9:09 ` Daniel Vetter
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=20190327092115.GW2665@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=boris.brezillon@collabora.com \
--cc=daniel.vetter@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=keithp@keithp.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