From: Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
To: Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: igt-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
Daniel Vetter <daniel.vetter-/w4YWyX8dFk@public.gmane.org>,
intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
amd-gfx mailing list
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
dri-devel
<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [Intel-gfx] [PATCH] RFC: Make igts for cross-driver stuff mandatory?
Date: Tue, 30 Oct 2018 09:54:54 +0100 [thread overview]
Message-ID: <20181030085454.GG21967@phenom.ffwll.local> (raw)
In-Reply-To: <CAPM=9tykF1U0Kah42ej7GR=6HyKe+WeV-LRe7_xB0VEUkikdPQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, Oct 30, 2018 at 12:17:30PM +1000, Dave Airlie wrote:
> On Fri, 19 Oct 2018 at 18:51, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> >
> > Hi all,
> >
> > This is just to collect feedback on this idea, and see whether the
> > overall dri-devel community stands on all this. I think the past few
> > cross-vendor uapi extensions all came with igts attached, and
> > personally I think there's lots of value in having them: A
> > cross-vendor interface isn't useful if every driver implements it
> > slightly differently.
> >
> > I think there's 2 questions here:
> >
> > - Do we want to make such testcases mandatory?
>
> Yes I think if at all practical it probably makes sense to have some
> mandatory test cases for all cross-vendor features, or features that
> might become cross vendor in the future.
I've created a few patches to test that in gitlab CI. I think the only
thing left now is CI'ing sysroot builds, but I don't know how to do that
myself.
> > - If yes, are we there yet, or is there something crucially missing
> > still?
>
> I think the does igt build in all the places needed is the main one,
> I've no idea what a baseline IGT test run looks like on non-intel hw,
> how useful is it?
We're in the process of moving i915 tests into a tests/i915/ subfolder. I
think after that we could try to them on some hardware (my long term plan
is to use vkms for that and put it into gitlab CI with qemu). We have
accidentally run igts on amdgpu instead of i915 on KBL-G (and our CI found
at least one bug in one of my refactor series), so stuff works :-)
Coverage is a bit a mixed bag I think, but that's always the case when you
retrofit a testsuite.
-Daniel
>
> Acked-by: Dave Airlie <airlied@redhat.com>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: igt-dev@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org,
amd-gfx mailing list <amd-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] RFC: Make igts for cross-driver stuff mandatory?
Date: Tue, 30 Oct 2018 09:54:54 +0100 [thread overview]
Message-ID: <20181030085454.GG21967@phenom.ffwll.local> (raw)
In-Reply-To: <CAPM=9tykF1U0Kah42ej7GR=6HyKe+WeV-LRe7_xB0VEUkikdPQ@mail.gmail.com>
On Tue, Oct 30, 2018 at 12:17:30PM +1000, Dave Airlie wrote:
> On Fri, 19 Oct 2018 at 18:51, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> >
> > Hi all,
> >
> > This is just to collect feedback on this idea, and see whether the
> > overall dri-devel community stands on all this. I think the past few
> > cross-vendor uapi extensions all came with igts attached, and
> > personally I think there's lots of value in having them: A
> > cross-vendor interface isn't useful if every driver implements it
> > slightly differently.
> >
> > I think there's 2 questions here:
> >
> > - Do we want to make such testcases mandatory?
>
> Yes I think if at all practical it probably makes sense to have some
> mandatory test cases for all cross-vendor features, or features that
> might become cross vendor in the future.
I've created a few patches to test that in gitlab CI. I think the only
thing left now is CI'ing sysroot builds, but I don't know how to do that
myself.
> > - If yes, are we there yet, or is there something crucially missing
> > still?
>
> I think the does igt build in all the places needed is the main one,
> I've no idea what a baseline IGT test run looks like on non-intel hw,
> how useful is it?
We're in the process of moving i915 tests into a tests/i915/ subfolder. I
think after that we could try to them on some hardware (my long term plan
is to use vkms for that and put it into gitlab CI with qemu). We have
accidentally run igts on amdgpu instead of i915 on KBL-G (and our CI found
at least one bug in one of my refactor series), so stuff works :-)
Coverage is a bit a mixed bag I think, but that's always the case when you
retrofit a testsuite.
-Daniel
>
> Acked-by: Dave Airlie <airlied@redhat.com>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-10-30 8:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 8:50 [PATCH] RFC: Make igts for cross-driver stuff mandatory? Daniel Vetter
2018-10-19 8:50 ` [igt-dev] " Daniel Vetter
2018-10-22 10:27 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-10-22 10:52 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-22 12:59 ` ✗ Fi.CI.IGT: failure " Patchwork
[not found] ` <20181019085049.25482-1-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2018-10-25 9:58 ` [PATCH] " Liviu Dudau
2018-10-25 9:58 ` [igt-dev] " Liviu Dudau
[not found] ` <20181025095804.GB29083-hOhETlTuV5niMG9XS5x8Mg@public.gmane.org>
2018-10-25 10:31 ` Daniel Vetter
2018-10-25 10:31 ` [Intel-gfx] " Daniel Vetter
2018-10-26 15:28 ` Alex Deucher
2018-10-26 15:28 ` Alex Deucher
2018-10-30 2:17 ` [Intel-gfx] " Dave Airlie
2018-10-30 2:17 ` [igt-dev] " Dave Airlie
[not found] ` <CAPM=9tykF1U0Kah42ej7GR=6HyKe+WeV-LRe7_xB0VEUkikdPQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-10-30 8:54 ` Daniel Vetter [this message]
2018-10-30 8:54 ` Daniel Vetter
2018-10-25 12:51 ` Sean Paul
2018-10-25 12:51 ` [igt-dev] " Sean Paul
2018-10-25 16:35 ` Eric Anholt
2018-10-25 16:35 ` [Intel-gfx] " Eric Anholt
[not found] ` <87efcernkp.fsf-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
2018-10-26 3:49 ` Zhou, David(ChunMing)
2018-10-26 3:49 ` Zhou, David(ChunMing)
[not found] ` <BY1PR12MB0502FFCA69A2C76817C22C8DB4F00-PicGAnIBOobrCwm+z9iKNgdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-10-26 8:32 ` Daniel Vetter
2018-10-26 8:32 ` Daniel Vetter
[not found] ` <CAKMK7uFsET+riNKw6eGt1+Uiuhq8eww1E4OFYVCC83CfQFN5qg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-10-26 8:48 ` zhoucm1
2018-10-26 8:48 ` zhoucm1
2018-10-26 14:41 ` Alex Deucher
2018-10-26 14:41 ` Alex Deucher
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=20181030085454.GG21967@phenom.ffwll.local \
--to=daniel-/w4ywyx8dfk@public.gmane.org \
--cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=daniel.vetter-/w4YWyX8dFk@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=igt-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/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 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.