Revision 95a31314b0385f55fdbc23a4376063be592df8ff authored by John Baldwin on 21 January 2010, 17:55:47 UTC, committed by John Baldwin on 21 January 2010, 17:55:47 UTC
Add a facility for associating optional descriptions with active interrupt
handlers.  This is primarily intended as a way to allow devices that use
multiple interrupts (e.g. MSI) to meaningfully distinguish the various
interrupt handlers.
- Add a new BUS_DESCRIBE_INTR() method to the bus interface to associate
  a description with an active interrupt handler setup by BUS_SETUP_INTR.
  It has a default method (bus_generic_describe_intr()) which simply passes
  the request up to the parent device.
- Add a bus_describe_intr() wrapper around BUS_DESCRIBE_INTR() that supports
  printf(9) style formatting using var args.
- Reserve MAXCOMLEN bytes in the intr_handler structure to hold the name of
  an interrupt handler and copy the name passed to intr_event_add_handler()
  into that buffer instead of just saving the pointer to the name.
- Add a new intr_event_describe_handler() which appends a description string
  to an interrupt handler's name.
- Implement support for interrupt descriptions on amd64, i386, and sparc64 by
  having the nexus(4) driver supply a custom bus_describe_intr method that
  invokes a new intr_describe() MD routine which in turn looks up the
  associated interrupt event and invokes intr_event_describe_handler().
1 parent cb53aec
Raw File
LOCKS
$FreeBSD$

This file documents formal review/approval requirements that have been
approved by core.

subsystem       login   expires  notes
--------------------------------------

Special cases:
src/*	RELENG_4_*	Requires Security Officer approval.
src/*	RELENG_5_*	Requires Security Officer approval.
src/*	RELENG_6_*	Requires Security Officer approval.
back to top