mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Gow <david@davidgow.net>
To: Mark Brown <broonie@kernel.org>,
	Brendan Higgins <brendan.higgins@linux.dev>,
	Rae Moar <raemoar63@gmail.com>,
	Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Cc: David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	dri-devel@lists.freedesktop.org, linux-kselftest@vger.kernel.org,
	kunit-dev@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kunit: configs: Enable DRM tests
Date: Sun, 13 Sep 2026 16:53:32 +0800	[thread overview]
Message-ID: <8aab06f1-89ed-46f7-87a7-846c820d6d4f@davidgow.net> (raw)
In-Reply-To: <20260911-kunit-drm-v1-1-c5c0f18fc7b0@kernel.org>

Le 12/09/2026 à 04:25, 'Mark Brown' via KUnit Development a écrit :
> There are a number of KUnit tests in the DRM subsystem but these are not
> run as standard since they are gated behind the main DRM config option
> and all_tests.config does not ensure that is enabled.  Add it.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---

I think this is overall a worthwhile change, but the 
drm_sched_scheduler_overhead_tests do fail on UML at the moment.

I've sent a potential fix out (the test seems to fail if CONFIG_HZ is 
100) here:
https://lore.kernel.org/all/20260913084155.520015-2-david@davidgow.net/

Ideally, that'd land first so we don't end up with yet more breakage, 
but otherwise we can perhaps disable those tests on UML for now.

Regardless, this is:

Reviewed-by: David Gow <david@davidgow.net>

Cheers,
-- David

>   tools/testing/kunit/configs/all_tests.config | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/tools/testing/kunit/configs/all_tests.config b/tools/testing/kunit/configs/all_tests.config
> index bccc2c77196d5..bee893f9fbbc6 100644
> --- a/tools/testing/kunit/configs/all_tests.config
> +++ b/tools/testing/kunit/configs/all_tests.config
> @@ -59,3 +59,5 @@ CONFIG_SND=y
>   CONFIG_SND_SOC=y
>   CONFIG_SND_SOC_TOPOLOGY_BUILD=y
>   CONFIG_SND_SOC_CS35L56_I2C=y
> +
> +CONFIG_DRM=y
> 
> ---
> base-commit: 8cdeaa50eae8dad34885515f62559ee83e7e8dda
> change-id: 20260911-kunit-drm-9cce0032e098
> 
> Best regards,
> --
> Mark Brown <broonie@kernel.org>
> 


      reply	other threads:[~2026-09-13  8:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 20:25 Mark Brown
2026-09-13  8:53 ` David Gow [this message]

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=8aab06f1-89ed-46f7-87a7-846c820d6d4f@davidgow.net \
    --to=david@davidgow.net \
    --cc=airlied@gmail.com \
    --cc=brendan.higgins@linux.dev \
    --cc=broonie@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=raemoar63@gmail.com \
    --cc=simona@ffwll.ch \
    --cc=tvrtko.ursulin@igalia.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

all inboxes | Powered by JetHome®