From: Philipp Stanner <phasta@mailbox.org>
To: Tvrtko Ursulin <tursulin@ursulin.net>,
Maxime Ripard <mripard@kernel.org>
Cc: Matthew Brost <matthew.brost@intel.com>,
Danilo Krummrich <dakr@kernel.org>,
Philipp Stanner <phasta@kernel.org>,
Christian Koenig <christian.koenig@amd.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Matthew Auld <matthew.auld@intel.com>,
Arun Pravin <arunpravin.paneerselvam@amd.com>,
Simona Vetter <simona.vetter@ffwll.ch>,
David Airlie <airlied@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/tests: Mark slow tests as slow
Date: Thu, 26 Feb 2026 13:48:27 +0100 [thread overview]
Message-ID: <595ce86b8a91f18ab8c73295a4a89c8f9353a794.camel@mailbox.org> (raw)
In-Reply-To: <e343e45b-6328-4a38-ad31-1487e273f12a@ursulin.net>
On Thu, 2026-02-26 at 12:42 +0000, Tvrtko Ursulin wrote:
>
> On 26/02/2026 10:56, Maxime Ripard wrote:
>
>
[…]
> > > > {}
> > > > };
> > > > static struct kunit_suite drm_sched_priority = {
> > > > .name = "drm_sched_basic_priority_tests",
> > > > @@ -544,11 +544,11 @@ static void drm_sched_test_credits(struct kunit *test)
> > > > drm_mock_sched_entity_free(entity);
> > > > drm_mock_sched_fini(sched);
> > > > }
> > > > static struct kunit_case drm_sched_credits_tests[] = {
> > > > - KUNIT_CASE(drm_sched_test_credits),
> > > > + KUNIT_CASE_SLOW(drm_sched_test_credits),
> > >
> > > Same really.
> > >
> > > Anyway, the scheduler parts LGTM and I can follow up trying to optimise
> > > these two later.
> > >
> > > For the scheduler:
> > >
> > > Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
> >
> > Thanks!
>
> I have a patch already which makes those (and one more) test cases
> faster, but I will wait sending it until you merge this one.
And why would we want to flag a test as slow just to immediately
afterwards make it faster?
Would it not be wiser to drop Maxime's change?
P.
next prev parent reply other threads:[~2026-02-26 12:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 11:03 [PATCH] drm/tests: Mark slow tests as slow Maxime Ripard
2026-02-24 11:12 ` Thomas Zimmermann
2026-02-24 11:43 ` Danilo Krummrich
2026-02-24 12:29 ` Tvrtko Ursulin
2026-02-24 12:44 ` Philipp Stanner
2026-02-24 12:49 ` Tvrtko Ursulin
2026-02-26 10:56 ` Maxime Ripard
2026-02-26 12:42 ` Tvrtko Ursulin
2026-02-26 12:48 ` Philipp Stanner [this message]
2026-02-26 13:02 ` Tvrtko Ursulin
2026-02-26 13:17 ` Philipp Stanner
2026-02-26 13:23 ` Tvrtko Ursulin
2026-02-24 13:07 ` Arunpravin Paneer Selvam
2026-02-27 5:13 ` Claude review: " Claude Code Review Bot
2026-02-27 5:13 ` Claude Code Review Bot
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=595ce86b8a91f18ab8c73295a4a89c8f9353a794.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=airlied@gmail.com \
--cc=arunpravin.paneerselvam@amd.com \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=phasta@kernel.org \
--cc=simona.vetter@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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