Page MenuHomeFreeBSD

linuxkpi: extend range of nsecs_to_jiffies64 to support Mesa's drm_syncobj usage
ClosedPublic

Authored by hselasky on Feb 26 2020, 9:10 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 10 2024, 12:15 AM
Unknown Object (File)
Feb 4 2024, 11:11 PM
Unknown Object (File)
Jan 13 2024, 3:24 AM
Unknown Object (File)
Dec 23 2023, 1:24 AM
Unknown Object (File)
Dec 15 2023, 9:16 PM
Unknown Object (File)
Dec 5 2023, 5:10 PM
Unknown Object (File)
Nov 28 2023, 3:13 AM
Unknown Object (File)
Nov 24 2023, 3:19 PM

Details

Summary

For Some Reason™ we've been experiencing breakage in Vulkan fences (implemented using DRM syncobj).

@jbeich noticed that changing INT64_MAX to INT32_MAX in the part of Mesa that sets the timeout_nsec field on the drm_syncobj_wait struct fixes it. Well, turns out Mesa has been relying on the implementation details of Linux's nsecs_to_jiffies64 — it supports a wider range of numbers, and INT64_MAX works fine. Let's do a similar thing I guess..

Test Plan

Rebuild drm-kms after adding this patch, reboot, retry using Vulkan applications (e.g. vkquake) — now they work fine instead of quitting almost instantly.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 29631

Event Timeline

hselasky updated this revision to Diff 68861.
hselasky edited reviewers, added: val_packett.cool; removed: hselasky.

Hi Greg,

Can you test this patch instead?

--HPS

Wow, that's a lot more code :D But yeah, works fine.

This revision is now accepted and ready to land.Feb 26 2020, 10:54 PM

I just have to give it a spin at work tomorrow and I'll submit it.