From: Daniel Vetter <daniel@ffwll.ch> To: DRI Development <dri-devel@lists.freedesktop.org>, IGT development <igt-dev@lists.freedesktop.org> Cc: Petri Latvala <petri.latvala@intel.com>, Daniel Vetter <daniel.vetter@intel.com>, Daniel Vetter <daniel.vetter@ffwll.ch>, Liviu Dudau <liviu.dudau@arm.com>, Alex Deucher <alexander.deucher@amd.com>, Dave Airlie <airlied@redhat.com>, Arkadiusz Hiler <arkadiusz.hiler@intel.com>, Sean Paul <sean@poorly.run> Subject: Re: [PATCH] drm/doc: Make igts for cross-driver stuff strongly suggested Date: Thu, 7 Feb 2019 11:13:00 +0100 [thread overview] Message-ID: <20190207101300.GR3271@phenom.ffwll.local> (raw) In-Reply-To: <20190128172258.9585-1-daniel.vetter@ffwll.ch> On Mon, Jan 28, 2019 at 06:22:58PM +0100, Daniel Vetter wrote: > Compared to the RFC[1] no changes to the patch itself, but igt moved > forward a lot: > > - gitlab CI builds with: reduced configs/libraries, arm cross build > and a sysroot build (should address all the build/cross platform > concerns raised in the RFC discussions). > > - tests reorganized into subdirectories so that the i915-gem tests > don't clog the main/shared tests directory anymore > > - quite a few more non-intel people contributing/reviewing/committing > igt tests patches. > > I think this addresses all the concerns raised in the RFC discussions, > and assuming there's enough Acks and no new issues that pop up, we can > go ahead with this. > > v2: > - Use "should" (in the usual RFC sense) to make it clear that in the > end this is all up to reviewer's discretion, as usual (Jani). > - Also in the title s/mandatory/strongly suggested/ (me) > - Make it clear we're not going to block features if a testcase is not > feasible, given hw and state of igt, both having some good gaps in > what can be tested (Harry, Eric, Sean, ...). > > 1: https://patchwork.kernel.org/patch/10648851/ > Cc: Petri Latvala <petri.latvala@intel.com> > Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com> > Cc: Liviu Dudau <liviu.dudau@arm.com> > Cc: Sean Paul <sean@poorly.run> > Cc: Eric Anholt <eric@anholt.net> > Cc: Alex Deucher <alexander.deucher@amd.com> > Cc: Dave Airlie <airlied@redhat.com> > Cc: Daniel Stone <daniel@fooishbar.org> > Cc: "Wentland, Harry" <Harry.Wentland@amd.com> > Cc: Brian Starkey <Brian.Starkey@arm.com> > Reviewed-by: Eric Anholt <eric@anholt.net> (v1) > Acked-by: Petri Latvala <petri.latvala@intel.com> > Acked-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com> > Acked-by: Sean Paul <sean@poorly.run> > Acked-by: "Wentland, Harry" <Harry.Wentland@amd.com> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> With all the additional ones I think we have enough acks, and Dave agreed that this seems ready to go. Merged into drm-misc-next. Thanks everyone for helping figuring this out, and if anything pops up, pls raise it so we can clarify the documentation. Cheers, Daniel > --- > Documentation/gpu/drm-uapi.rst | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst > index a752aa561ea4..c9fd23efd957 100644 > --- a/Documentation/gpu/drm-uapi.rst > +++ b/Documentation/gpu/drm-uapi.rst > @@ -238,6 +238,14 @@ DRM specific patterns. Note that ENOTTY has the slightly unintuitive meaning of > Testing and validation > ====================== > > +Testing Requirements for userspace API > +-------------------------------------- > + > +New cross-driver userspace interface extensions, like new IOCTL, new KMS > +properties, new files in sysfs or anything else that constitutes an API change > +should have driver-agnostic testcases in IGT for that feature, if such a test > +can be reasonably made using IGT for the target hardware. > + > Validating changes with IGT > --------------------------- > > -- > 2.20.1 > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch> To: DRI Development <dri-devel@lists.freedesktop.org>, IGT development <igt-dev@lists.freedesktop.org> Cc: Petri Latvala <petri.latvala@intel.com>, Daniel Vetter <daniel.vetter@intel.com>, Liviu Dudau <liviu.dudau@arm.com>, Alex Deucher <alexander.deucher@amd.com>, Dave Airlie <airlied@redhat.com>, Sean Paul <sean@poorly.run>, Brian Starkey <Brian.Starkey@arm.com> Subject: Re: [igt-dev] [PATCH] drm/doc: Make igts for cross-driver stuff strongly suggested Date: Thu, 7 Feb 2019 11:13:00 +0100 [thread overview] Message-ID: <20190207101300.GR3271@phenom.ffwll.local> (raw) In-Reply-To: <20190128172258.9585-1-daniel.vetter@ffwll.ch> On Mon, Jan 28, 2019 at 06:22:58PM +0100, Daniel Vetter wrote: > Compared to the RFC[1] no changes to the patch itself, but igt moved > forward a lot: > > - gitlab CI builds with: reduced configs/libraries, arm cross build > and a sysroot build (should address all the build/cross platform > concerns raised in the RFC discussions). > > - tests reorganized into subdirectories so that the i915-gem tests > don't clog the main/shared tests directory anymore > > - quite a few more non-intel people contributing/reviewing/committing > igt tests patches. > > I think this addresses all the concerns raised in the RFC discussions, > and assuming there's enough Acks and no new issues that pop up, we can > go ahead with this. > > v2: > - Use "should" (in the usual RFC sense) to make it clear that in the > end this is all up to reviewer's discretion, as usual (Jani). > - Also in the title s/mandatory/strongly suggested/ (me) > - Make it clear we're not going to block features if a testcase is not > feasible, given hw and state of igt, both having some good gaps in > what can be tested (Harry, Eric, Sean, ...). > > 1: https://patchwork.kernel.org/patch/10648851/ > Cc: Petri Latvala <petri.latvala@intel.com> > Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com> > Cc: Liviu Dudau <liviu.dudau@arm.com> > Cc: Sean Paul <sean@poorly.run> > Cc: Eric Anholt <eric@anholt.net> > Cc: Alex Deucher <alexander.deucher@amd.com> > Cc: Dave Airlie <airlied@redhat.com> > Cc: Daniel Stone <daniel@fooishbar.org> > Cc: "Wentland, Harry" <Harry.Wentland@amd.com> > Cc: Brian Starkey <Brian.Starkey@arm.com> > Reviewed-by: Eric Anholt <eric@anholt.net> (v1) > Acked-by: Petri Latvala <petri.latvala@intel.com> > Acked-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com> > Acked-by: Sean Paul <sean@poorly.run> > Acked-by: "Wentland, Harry" <Harry.Wentland@amd.com> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> With all the additional ones I think we have enough acks, and Dave agreed that this seems ready to go. Merged into drm-misc-next. Thanks everyone for helping figuring this out, and if anything pops up, pls raise it so we can clarify the documentation. Cheers, Daniel > --- > Documentation/gpu/drm-uapi.rst | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst > index a752aa561ea4..c9fd23efd957 100644 > --- a/Documentation/gpu/drm-uapi.rst > +++ b/Documentation/gpu/drm-uapi.rst > @@ -238,6 +238,14 @@ DRM specific patterns. Note that ENOTTY has the slightly unintuitive meaning of > Testing and validation > ====================== > > +Testing Requirements for userspace API > +-------------------------------------- > + > +New cross-driver userspace interface extensions, like new IOCTL, new KMS > +properties, new files in sysfs or anything else that constitutes an API change > +should have driver-agnostic testcases in IGT for that feature, if such a test > +can be reasonably made using IGT for the target hardware. > + > Validating changes with IGT > --------------------------- > > -- > 2.20.1 > -- 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-02-07 10:13 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-01-28 17:22 [PATCH] drm/doc: Make igts for cross-driver stuff strongly suggested Daniel Vetter 2019-01-28 17:22 ` [igt-dev] " Daniel Vetter 2019-01-28 17:51 ` Liviu Dudau 2019-01-28 17:51 ` [igt-dev] " Liviu Dudau 2019-01-29 7:27 ` Jani Nikula 2019-01-29 7:27 ` [igt-dev] " Jani Nikula 2019-01-29 14:52 ` Brian Starkey 2019-01-29 14:52 ` [igt-dev] " Brian Starkey 2019-01-30 7:00 ` Tomi Valkeinen 2019-02-05 19:10 ` [igt-dev] " Boris Brezillon 2019-02-05 19:45 ` Alex Deucher 2019-02-05 19:45 ` [igt-dev] " Alex Deucher 2019-02-07 10:13 ` Daniel Vetter [this message] 2019-02-07 10:13 ` 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=20190207101300.GR3271@phenom.ffwll.local \ --to=daniel@ffwll.ch \ --cc=airlied@redhat.com \ --cc=alexander.deucher@amd.com \ --cc=arkadiusz.hiler@intel.com \ --cc=daniel.vetter@ffwll.ch \ --cc=daniel.vetter@intel.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=igt-dev@lists.freedesktop.org \ --cc=liviu.dudau@arm.com \ --cc=petri.latvala@intel.com \ --cc=sean@poorly.run \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.