Page MenuHomeFreeBSD

kern/intr: add interrupt counters to intr_isrc
Needs ReviewPublic

Authored by ehem_freebsd_m5p.com on Aug 11 2023, 7:50 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Oct 25, 12:28 AM
Unknown Object (File)
Oct 6 2024, 1:55 AM
Unknown Object (File)
Oct 3 2024, 6:01 AM
Unknown Object (File)
Oct 3 2024, 4:16 AM
Unknown Object (File)
Oct 1 2024, 8:52 AM
Unknown Object (File)
Sep 26 2024, 9:17 PM
Unknown Object (File)
Sep 25 2024, 12:08 PM
Unknown Object (File)
Sep 21 2024, 9:04 AM
Subscribers

Details

Reviewers
mjg
markj
Summary

Maintaining the intrcnt/intrnames variables are causing problems.
Notably INTRNG's interrupt release code is unable to properly release
counters. At this point it seems best to work towards moving the values
elsewhere.

The counters also really belong to the interrupting device, not the
controller. As such they should be in the device-side structure, not
the interrupt controller structure.

Additionally this is an architecture-independent area. This should
increase shared source code by taking over.

Note, the array of counters ensures no two processors modify the same
counter at the same time. IPI and PPI interrupt handlers *never* report
strays, thus there is little danger of collision on the stray counter.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 53052
Build 49943: arc lint + arc unit

Event Timeline

ehem_freebsd_m5p.com created this revision.

This is splitting the counter add commit off the flag add commit. Originally these seemed like a single task, but seems further consideration is needed for the flags.

Unfortunately see D38448 for most comments so far.

I have no direct disagreement with @mjg's wish for such counters to be moved to the per-processor area. Issue is this commit is merely an intermediate step in moving the counters from the giant table of counters to intr_event.

I would hope a future commit could make ie_intrcnt serve as the interrupt counter if the interrupt is uni-processor. Whereas for multi-processor interrupts it could serve as an index into the per-processor area.

Issue is still, that is a topic for a future commit, not this one.