Page MenuHomeFreeBSD

Don't use critical section when calling intr_irq_handler()
ClosedPublic

Authored by trasz on Oct 6 2020, 3:04 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 17 2024, 7:58 AM
Unknown Object (File)
Feb 8 2024, 2:25 AM
Unknown Object (File)
Feb 4 2024, 4:49 PM
Unknown Object (File)
Jan 18 2024, 2:54 AM
Unknown Object (File)
Dec 25 2023, 8:29 AM
Unknown Object (File)
Dec 23 2023, 2:18 AM
Unknown Object (File)
Nov 30 2023, 7:07 AM
Unknown Object (File)
Nov 29 2023, 10:09 PM
Subscribers

Details

Summary

Don't use critical section when calling intr_irq_handler() - that
function enters critical section by itself anyway.

(XXX: Probably the critical section here can disappear entirely;
I'd rather do that later.)

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

trasz requested review of this revision.Oct 6 2020, 3:04 PM
This revision is now accepted and ready to land.Oct 6 2020, 5:41 PM
jhb added inline comments.
sys/riscv/riscv/intr_machdep.c
174 ↗(On Diff #77941)

This is likely needed as it is what sets the boundary as to when a context switch to a taskqueue or other there scheduled by a handler executes. If intr_isrc_dispatch() has its own critical section, then you can remove this, but if it doesn't, you probably need to leave this in place.