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)
Fri, Nov 7, 12:52 PM
Unknown Object (File)
Thu, Nov 6, 8:38 PM
Unknown Object (File)
Wed, Nov 5, 6:40 PM
Unknown Object (File)
Wed, Nov 5, 4:35 PM
Unknown Object (File)
Wed, Nov 5, 1:18 AM
Unknown Object (File)
Wed, Oct 29, 1:13 PM
Unknown Object (File)
Mon, Oct 27, 10:08 PM
Unknown Object (File)
Mon, Oct 27, 2:50 PM

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.