"Alexandre Courbot" <acourbot@xxxxxxxxxx> writes: > Hi Boqun, > > On Fri Mar 21, 2025 at 3:17 AM JST, Boqun Feng wrote: >> Also an Instant type has been proposed and reviewed for a while: >> >> https://lore.kernel.org/rust-for-linux/20250220070611.214262-5-fujita.tomonori@xxxxxxxxx/ >> >> we should use that type instead of re-inventing the wheel here. Of >> course, it's currently not quite working because Instant is only for >> CLOCK_MONOTONIC. But there was a proposal to make `Instant` generic over >> clock: >> >> https://lore.kernel.org/rust-for-linux/20230714-rust-time-v2-1-f5aed84218c4@xxxxxxxxxxxxx/ >> >> if you follow that design, you can implement a `Instant<NovaGpu>`, where >> >> ipml Now for NovaGpu { >> fn now() -> Instant<Self> { >> // your Timer::read() implementation. >> } >> } > > Ah, thanks for pointing this out. I'll keep track of these patches, > hopefully they get merged soon! Would that actually work though? Instant is a ktime_t, which is a signed i64 rather than a u64. When I read your patch I assumed that you had to add your own Timestamp because the value had to be whatever was read from the GPU, independent of the clock value kept by the system or other hardware. db48x
