viortc_ptp_do_xtstamp(9)
β¨ viortc_ptp_do_xtstamp π«
okay bestie, welcome to the viortc_ptp_do_xtstamp(9) page β it's a kernel API manual entry and it's literally the whole vibe of "hey device, gimme a crosststamp please" π«Ά
πΈ NAME πΈ
viortc_ptp_do_xtstamp β get crosststamp from device β¨
π SYNOPSIS π
int viortc_ptp_do_xtstamp (struct viortc_ptp_clock *vio_ptp , u8
hw_counter , enum clocksource_ids cs_id , struct viortc_ptp_cross_ctx
*ctx );
π¦ ARGUMENTS π¦
vio_ptpβ the virtio_rtc PTP clock, aka the main character of this whole situation πhw_counterβ the virtio_rtc HW counter type, it's au8, slay πcs_idβ the clocksource id that corresponds tohw_counter, no cap they're a matched set πctxβ the context forget_device_system_crosststamp, keeping it all organized fr fr
π DESCRIPTION π
Reads the HW-specific crosststamp from the device. That's it. That's the whole plot. it's giving "just go ask the hardware nicely" πβ¨
β CONTEXT β
Process context. so like, normal sleepable vibes, not some interrupt-y chaos π
π RETURN π
- Zero on success π
- negative error code otherwise π
π₯ SEE ALSO π₯
- Kernel file
./drivers/virtio/virtio_rtc_ptp.c struct viortc_ptp_clock(9)struct viortc_ptp_cross_ctx(9)viortc_ptp_get_time_fn(9)viortc_ptp_getcrosststamp(9)viortc_ptp_unregister(9)viortc_ptp_get_cross_cap(9)viortc_ptp_register(9)
ok that's the whole page bestie, go read the source and hydrate π
sign-off szn π β this one's from the ./drivers/virtio source tree, dated October 2026, and you can find it filed under viortc_ptp_do_xtstamp(9) in the Kernel API Manual. obsessed. periodt. π
β¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms