Page MenuHomeFreeBSD

intrng: allow specifying an interrupt number during allocation
AbandonedPublic

Authored by ehem_freebsd_m5p.com on Oct 25 2021, 1:44 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 1, 2:24 PM
Unknown Object (File)
Oct 4 2024, 10:40 AM
Unknown Object (File)
Oct 3 2024, 12:09 PM
Unknown Object (File)
Oct 1 2024, 10:20 AM
Unknown Object (File)
Oct 1 2024, 2:55 AM
Unknown Object (File)
Sep 29 2024, 10:28 PM
Unknown Object (File)
Sep 28 2024, 4:26 AM
Unknown Object (File)
Sep 27 2024, 11:42 AM

Details

Reviewers
None
Summary

All interrupt architectures besides INTRNG expect interrupt numbers to
be selected outside. Increase INTRNG's cross-architecture potential by
allowing this approach.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 42334
Build 39222: arc lint + arc unit

Event Timeline

This is more in the direction of D32504. Theory is, can INTRNG be adjusted to provide sufficient functionality to replace the current x86 interrupt framework?

In this initial form I used 0x80 as this is nominally a flag meant for use by isrc_alloc_irq() and doesn't really need to be stored permanently on the intr_irqsrc structure. The value doesn't really matter since it can readily by changed via intr.h, but seemed best to somehow hint it was a setup-only flag.

Other feature needed to subsume PowerPC interrupts is to be able to hash values for the irq_sources[] table. That though brings in the issue of how best to deal with collisions?

I now expect to abandon this. At this point I've got a PoC implementation of using a resource manager to handle the interrupt number ranges. This was a thought, but it seems unlikely now.

Marking D32632 as abandoned. I've got something which approaches the same goal, but is distinct enough to not take over D32632.