diff options
| author | Warner Losh <imp@FreeBSD.org> | 2024-05-10 21:41:36 +0000 |
|---|---|---|
| committer | Warner Losh <imp@FreeBSD.org> | 2024-05-10 21:41:36 +0000 |
| commit | a2409f17377ebb5c6e3e522ae090a0845ee19aeb (patch) | |
| tree | d3cca13a4280fc4868db64a997182f3c1e082d77 | |
| parent | 38c35248fe3b740e107682b4a10bebe28992590f (diff) | |
| download | src-a2409f17377ebb5c6e3e522ae090a0845ee19aeb.tar.gz src-a2409f17377ebb5c6e3e522ae090a0845ee19aeb.zip | |
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
| -rw-r--r-- | sys/kern/kern_intr.c | 5 |
1 files changed, 4 insertions, 1 deletions
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. |