Page MenuHomeFreeBSD

arm64/gicv3: Initialize all ITS collections at attach time
AbandonedPublic

Authored by scottph on Oct 13 2020, 7:14 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 10 2024, 4:31 AM
Unknown Object (File)
Dec 14 2023, 8:20 PM
Unknown Object (File)
Dec 9 2023, 6:58 PM
Unknown Object (File)
Nov 19 2023, 8:57 AM
Unknown Object (File)
Nov 17 2023, 4:41 AM
Unknown Object (File)
Oct 16 2023, 7:13 PM
Unknown Object (File)
Oct 13 2023, 5:27 PM
Unknown Object (File)
Oct 12 2023, 11:41 AM
Subscribers

Details

Summary

When device drivers attach, they configure interrupts. We want to
target all interrupts to the boot cpu early on, and then shuffle
them at a later point. However, we use domain proximity
information to limit which cpus an ITS will target. To handle the
case where the boot cpu isn't in the ITS's proximity doman, we
locate all redistributors and configure all ITS collections at
attach time, so that we're ready to configure any interrupts.

Sponsored by: Ampere Computing

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

Another approach could be to just all interrupts to target the boot cpu, maybe before ap startup and maybe apply proximity restrictions after ap startup?

D28340's approach of letting all CPUs get targeted by an ITS removes the need for changing this initialization.