Page MenuHomeFreeBSD

Use the physical timer when able
ClosedPublic

Authored by andrew on Mar 15 2023, 2:18 PM.
Tags
None
Referenced Files
Unknown Object (File)
Oct 14 2024, 12:11 AM
Unknown Object (File)
Oct 9 2024, 6:47 PM
Unknown Object (File)
Oct 2 2024, 8:17 AM
Unknown Object (File)
Sep 28 2024, 1:09 PM
Unknown Object (File)
Sep 23 2024, 11:06 PM
Unknown Object (File)
Sep 21 2024, 9:41 AM
Unknown Object (File)
Sep 21 2024, 1:44 AM
Unknown Object (File)
Sep 20 2024, 3:43 PM
Subscribers

Details

Summary

To allow bhyve manage the virtual timer while in a guest have FreeBSD
use the virtual timer only when bhyve will be unavailable due to not
starting at EL2 where the hypervisor switcher will run.

Sponsored by: Arm Ltd

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Assuming we know the res is always non-null in these cases, I think we're good. I kinda think they should be, but that's just from a quick read.

sys/arm/arm/generic_timer.c
664

only question: are we guaranteed that these timers will be around in this case? Similar below...

This revision is now accepted and ready to land.Mar 15 2023, 2:55 PM
sys/arm/arm/generic_timer.c
664

We require the virtual and physical timer interrupts as they are marked non-optional in arm_tmr_irq_defs

This revision was automatically updated to reflect the committed changes.