Limit MAXCPU <= MAX_APIC_ID assertion to i386
AbandonedPublic
Actions

Authored by emaste on Oct 19 2022, 7:32 PM.

Tags

None

Referenced Files

	F149532011: D37060.id112006.diff
	Wed, Mar 25, 1:49 AM

	Unknown Object (File)
	Tue, Mar 24, 1:35 AM

	Unknown Object (File)
	Fri, Mar 13, 5:29 PM

	Unknown Object (File)
	Thu, Mar 12, 8:40 PM

	Unknown Object (File)
	Wed, Mar 11, 10:36 AM

	Unknown Object (File)
	Sun, Mar 8, 6:42 PM

	Unknown Object (File)
	Sun, Mar 8, 6:42 PM

	Unknown Object (File)
	Sat, Mar 7, 10:00 PM

View All 98 Files

Subscribers

kib

Details

Reviewers

jhb
royger

Diff Detail

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

From @jhb in D36838: the assertion about MAXCPU being <= MAX_APIC_ID is no longer relevant with x2APIC and can be removed I think. I'm not sure if we support x2APIC on i386, so maybe the assertion has to stay for i386 still

emaste mentioned this in D36838: amd64: Bump MAXCPU to 1024 (from 256).Oct 19 2022, 7:33 PM

No, MAX_APIC_ID is also relevant for amd64, as it's used by madt_parse_cpu(), it needs to be bumped to twice the value of MAXCPU I think.

I guess you could have a i386 system with APIC IDs > 0x200, but it's unlikely such system doesn't support amd64.

i386 also uses x2APIC when supported by hardware and not disabled by BIOS.

emaste abandoned this revision.Oct 20 2022, 11:57 AM

Revision Contents
Changeset List

Path

Size

sys/

x86/

mp_x86.c

2 lines

Diff 112006

View Options

Limit MAXCPU <= MAX_APIC_ID assertion to i386AbandonedPublicActions