Page MenuHomeFreeBSD

Retire non-EARLY_AP_STARTUP code
Needs RevisionPublic

Authored by emaste on Aug 7 2023, 8:54 PM.
Tags
None
Referenced Files
Unknown Object (File)
Oct 9 2024, 10:26 PM
Unknown Object (File)
Sep 27 2024, 12:51 PM
Unknown Object (File)
Sep 26 2024, 2:05 AM
Unknown Object (File)
Sep 7 2024, 6:49 AM
Unknown Object (File)
Jul 12 2024, 4:00 AM
Unknown Object (File)
Jul 7 2024, 12:50 AM
Unknown Object (File)
May 3 2024, 5:19 PM
Unknown Object (File)
May 2 2024, 2:43 AM

Details

Reviewers
jrtc27

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

emaste requested review of this revision.Aug 7 2023, 8:54 PM
jrtc27 requested changes to this revision.Aug 7 2023, 8:56 PM
jrtc27 added a subscriber: jrtc27.

Uh, not all architectures currently support EARLY_AP_STARTUP. Even arm64 doesn't; there's a comment in the GICv3 driver for example about it IIRC.

This revision now requires changes to proceed.Aug 7 2023, 8:56 PM

The basic problem on arm64 is:

  • IPIs need an INTRNG PIC
  • INTRNG PIC needs newbus to probe up to at least BUS_PASS_INTERRUPT
  • newbus doesn't run until SI_SUB_DRIVERS
  • SI_SUB_SMP comes before SI_SUB_DRIVERS under EARLY_AP_STARTUP

Uh, not all architectures currently support EARLY_AP_STARTUP

Yeah, I noticed this when only x86 config files needed modification. See D41351 for a proposed first step.