From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Maíra Canal" <mcanal@igalia.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Melissa Wen" <mwen@igalia.com>, "Iago Toral" <itoral@igalia.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Tvrtko Ursulin" <tvrtko.ursulin@igalia.com>,
"Dave Stevenson" <dave.stevenson@raspberrypi.com>,
"Raspberry Pi Kernel Maintenance" <kernel-list@raspberrypi.com>
Cc: kernel-dev@igalia.com, dri-devel@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
"Maíra Canal" <mcanal@igalia.com>
Subject: Re: [PATCH v3 2/7] drm: Add drm_timeout_rel_to_jiffies()
Date: Wed, 16 Sep 2026 13:38:37 +0300 [thread overview]
Message-ID: <92e315da6bd0a3daa36948f4de2e1b4f82c49e27@intel.com> (raw)
In-Reply-To: <c20c43109d3ebb08ad6a0c811ffaeb48f90efed5@intel.com>
On Wed, 16 Sep 2026, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Tue, 15 Sep 2026, Maíra Canal <mcanal@igalia.com> wrote:
>> drm_timeout_abs_to_jiffies() covers the drivers whose wait UAPI takes an
>> absolute deadline, but there is no equivalent for the drivers that
>> express a wait as a duration. Drivers such as i915 and v3d convert the
>> value themselves.
>>
>> Converting a nanosecond duration to jiffies needs some care.
>> nsecs_to_jiffies() returns unsigned long, so on 32-bit a large
>> userspace-supplied timeout overflows its range and is silently truncated.
>>
>> i915 already handles both cases in a local helper, which v3d has a copy
>> of. Add the same conversion to the core, so that it is available to any
>> driver and both copies can be dropped.
>>
>> Signed-off-by: Maíra Canal <mcanal@igalia.com>
>> ---
>> drivers/gpu/drm/drm_timeout.c | 45 +++++++++++++++++++++++++++++++++++++++++++
>> include/drm/drm_timeout.h | 1 +
>> 2 files changed, 46 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/drm_timeout.c b/drivers/gpu/drm/drm_timeout.c
>> index 35e10293e0a1..ee545475429c 100644
>> --- a/drivers/gpu/drm/drm_timeout.c
>> +++ b/drivers/gpu/drm/drm_timeout.c
>> @@ -9,6 +9,7 @@
>> #include <linux/export.h>
>> #include <linux/jiffies.h>
>> #include <linux/ktime.h>
>> +#include <linux/math64.h>
>> #include <linux/sched.h>
>>
>> #include <drm/drm_timeout.h>
>> @@ -48,3 +49,47 @@ signed long drm_timeout_abs_to_jiffies(int64_t timeout_nsec)
>> return timeout_jiffies64 + 1;
>> }
>> EXPORT_SYMBOL(drm_timeout_abs_to_jiffies);
>> +
>> +/**
>> + * drm_timeout_rel_to_jiffies - calculate jiffies timeout from relative value
>> + * @timeout_nsec: relative timeout in ns, 0 for poll
>> + *
>> + * Calculate the timeout in jiffies from a relative timeout in ns, for drivers
>> + * whose UAPI expresses a wait as a duration rather than as a deadline.
>> + *
>> + * The result is clamped to MAX_JIFFY_OFFSET. That keeps it positive once it is
>> + * converted to the signed long taken by dma_fence_wait_timeout() and friends,
>> + * which matters on 32-bit, and keeps it distinct from MAX_SCHEDULE_TIMEOUT so
>> + * that a finite wait is never understood as an infinite one.
>> + *
>> + * It's strongly discouraged to use relative timeouts in uAPIs, as they do not
>> + * survive a restarted ioctl. A signal-interrupted ioctl is re-entered with the
>> + * same arguments, so the duration starts counting from zero again. New uAPIs
>> + * should take an absolute deadline and use drm_timeout_abs_to_jiffies().
>> + *
>> + * Returns:
>> + * 0 if @timeout_nsec is 0. Otherwise the equivalent number of jiffies and
>> + * clamped to MAX_JIFFY_OFFSET.
>> + */
>> +unsigned long drm_timeout_rel_to_jiffies(u64 timeout_nsec)
>> +{
>> + u64 secs;
>> + u32 rem;
>> +
>> + /* Make 0 timeout means poll, as for the absolute variant. */
>> + if (timeout_nsec == 0)
>> + return 0;
>> +
>> + /*
>> + * As nsecs_to_jiffies64() does not guard against overflow, split
>> + * the timeout into whole seconds and nanoseconds. This way
>> + * nsecs_to_jiffies64() is always handed a value below a second.
>> + */
>> + secs = div_u64_rem(timeout_nsec, NSEC_PER_SEC, &rem);
>> + if (secs >= MAX_JIFFY_OFFSET / HZ)
>> + return MAX_JIFFY_OFFSET;
>> +
>> + return min_t(u64, MAX_JIFFY_OFFSET,
>> + secs_to_jiffies(secs) + nsecs_to_jiffies64(rem) + 1);
>> +}
>> +EXPORT_SYMBOL(drm_timeout_rel_to_jiffies);
>> diff --git a/include/drm/drm_timeout.h b/include/drm/drm_timeout.h
>> index cd9621c52062..6ee222a3e97c 100644
>> --- a/include/drm/drm_timeout.h
>> +++ b/include/drm/drm_timeout.h
>> @@ -12,5 +12,6 @@
>> #include <linux/types.h>
>>
>> signed long drm_timeout_abs_to_jiffies(s64 timeout_nsec);
>> +unsigned long drm_timeout_rel_to_jiffies(u64 timeout_nsec);
>
> The signed/unsigned differences here bug me a little. Maybe explain why
> in the commit message if there's a rationale?
>
> I note that drm_timeout_rel_to_jiffies() return value is assigned to
> unsigned long variables half the time. I guess its kernel-doc could say
> it never returns negative values?
Gah, I meant drm_timeout_abs_to_jiffies() here, sorry.
>
> BR,
> Jani.
>
>
>
>
>>
>> #endif
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-09-16 10:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 19:42 [PATCH v3 0/7] drm: Consolidate the wait timeout conversion helpers Maíra Canal
2026-09-15 19:42 ` [PATCH v3 1/7] drm: Move drm_timeout_abs_to_jiffies() to drm_timeout.c Maíra Canal
2026-09-16 10:33 ` Jani Nikula
2026-09-28 16:03 ` Thomas Zimmermann
2026-09-28 16:12 ` Thomas Zimmermann
2026-09-28 16:23 ` Thomas Zimmermann
2026-09-15 19:42 ` [PATCH v3 2/7] drm: Add drm_timeout_rel_to_jiffies() Maíra Canal
2026-09-16 10:38 ` Jani Nikula
2026-09-16 10:38 ` Jani Nikula [this message]
2026-09-16 13:08 ` Maíra Canal
2026-09-16 16:06 ` Jani Nikula
2026-09-28 16:37 ` Thomas Zimmermann
2026-09-28 18:09 ` Maíra Canal
2026-09-29 8:07 ` Thomas Zimmermann
2026-09-15 19:42 ` [PATCH v3 3/7] drm/amdgpu: Use drm_timeout_abs_to_jiffies() Maíra Canal
2026-09-15 19:42 ` [PATCH v3 4/7] drm/v3d: Use drm_timeout_rel_to_jiffies() Maíra Canal
2026-09-29 8:22 ` Thomas Zimmermann
2026-09-15 19:42 ` [PATCH v3 5/7] drm/i915: " Maíra Canal
2026-09-16 10:42 ` Jani Nikula
2026-09-29 8:20 ` Thomas Zimmermann
2026-09-30 17:12 ` Andi Shyti
2026-09-15 19:42 ` [PATCH v3 6/7] drm/vc4: " Maíra Canal
2026-09-15 19:42 ` [PATCH v3 7/7] drm: Rename drm_utils.h to drm_panel_quirks.h Maíra Canal
2026-09-22 12:00 ` Maíra Canal
2026-09-29 8:17 ` Thomas Zimmermann
2026-09-15 21:21 ` ✓ i915.CI.BAT: success for drm: Consolidate the wait timeout conversion helpers (rev3) Patchwork
2026-09-16 9:14 ` ✓ i915.CI.Full: " Patchwork
2026-09-16 12:22 ` [PATCH v3 0/7] drm: Consolidate the wait timeout conversion helpers Christian König
2026-09-30 22:51 ` Maíra Canal
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=92e315da6bd0a3daa36948f4de2e1b4f82c49e27@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=itoral@igalia.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kernel-dev@igalia.com \
--cc=kernel-list@raspberrypi.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcanal@igalia.com \
--cc=mripard@kernel.org \
--cc=mwen@igalia.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tvrtko.ursulin@igalia.com \
--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