mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
To: phasta@kernel.org, David Gow <david@davidgow.net>
Cc: "Christian König" <christian.koenig@amd.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Pierre-Eric Pelloux-Prayer" <pierre-eric.pelloux-prayer@amd.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	kernel-dev@igalia.com, kunit-dev@googlegroups.com
Subject: Re: [PATCH] drm/sched: Increase drm_mock_sched_job_wait_finished timeout when CONFIG_HZ=100
Date: Mon, 14 Sep 2026 13:12:54 +0100	[thread overview]
Message-ID: <f86fafc7-3e42-47b2-aca7-e0b4be56b699@igalia.com> (raw)
In-Reply-To: <26926372f9d375e1741b16abd2a910f3754a0410.camel@mailbox.org>


On 14/09/2026 12:48, Philipp Stanner wrote:
> On Mon, 2026-09-14 at 12:21 +0100, Tvrtko Ursulin wrote:
>> It's not a loss really to
>> skip the scheduling quality tests on more platforms than strictly
>> required so I'd say lets go with that.
> 
> Does that mean you agree with my idea of having two options for
> building the tests, one for sanity and one for performance-ish things?

A new kconfig? Makes sense.
Regards,

Tvrtko


  reply	other threads:[~2026-09-14 12:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-13  8:41 David Gow
2026-09-14  8:49 ` Tvrtko Ursulin
2026-09-14 10:06   ` David Gow
2026-09-14 11:21     ` Tvrtko Ursulin
2026-09-14 11:48       ` Philipp Stanner
2026-09-14 12:12         ` Tvrtko Ursulin [this message]
2026-09-14 13:33           ` David Gow
2026-09-14  9:03 ` Philipp Stanner
2026-09-14 10:07   ` David Gow

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=f86fafc7-3e42-47b2-aca7-e0b4be56b699@igalia.com \
    --to=tvrtko.ursulin@igalia.com \
    --cc=christian.koenig@amd.com \
    --cc=dakr@kernel.org \
    --cc=david@davidgow.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-dev@igalia.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=phasta@kernel.org \
    --cc=pierre-eric.pelloux-prayer@amd.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®