From a2409f17377ebb5c6e3e522ae090a0845ee19aeb Mon Sep 17 00:00:00 2001 From: Warner Losh Date: Fri, 10 May 2024 15:41:36 -0600 Subject: intr: Document how to get the interrupt frame Document that the only way to get the interrupt thread is to use curthread->td_intr_frame, rather than the old-style of having a NULL pointer for the interrupt thread. As of 38c35248fe3b, support for that has been removed. I neglected to update that commit message with these details. Suggested by: mhorne --- sys/kern/kern_intr.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/sys/kern/kern_intr.c b/sys/kern/kern_intr.c index 008f8d1242ca..7a57d964acd9 100644 --- a/sys/kern/kern_intr.c +++ b/sys/kern/kern_intr.c @@ -1346,7 +1346,10 @@ ithread_loop(void *arg) * * Input: * o ie: the event connected to this interrupt. - * o frame: the current trap frame. +-------------------------------------------------------------------------------- + * o frame: the current trap frame. If the client interrupt + * handler needs this frame, they should get it + * via curthread->td_intr_frame. * * Return value: * o 0: everything ok. -- cgit v1.2.3