acrn_ehl_crb does not work with CPUs >1

[jenmwms]

Describe the bug
The new APIC TSC Deadline Timer supports SMP=y configuration, which allows us to start working with number CPUs >1. With Initial tests of CPUS=2, Zephyr fails to boot as the pre-launched guest VM on ACRN. hello_world even fails to boot.

To Reproduce
Steps to reproduce the behavior:

1. Configure acrn_ehl_crb_defconfig with CONFIG_MP_NUM_CPUs=2
2. west build -p -b acrn_ehl_crb zephyr/tests/kernel/smp (hello_world even fails to boot)
3. Flash and observe console.

Expected behavior
Build successfully and use CONFIG_MP_NUM_CPUs >1 without issue, platform-wide tests. This is just example.

Impact
cannot use SMP with more than 1 CPU with APIC timer. showstopper.

Logs and console output

DEBUG   - DEVICE: ACRN:\>vm_console 0
DEBUG   - DEVICE: VM is not valid
DEBUG   - DEVICE: 
DEBUG   - DEVICE: Error: Invalid parameters.
DEBUG   - Timed out while monitoring serial output on acrn_ehl_crb

Environment (please complete the following information):

• OS: Linux
• Toolchain Zephyr SDK 2.4
• Commit SHA 4ee6130

[andyross]

FWIW: it's very unlikely to be the timer driver if the system is dead or faulted or whatever state it's in by the time get get to the ACRN prompt. Most likely it's being terminated for sending a startup IPI to a bad APIC ID or some other kind of misbehavior. Timer setup happens later.

[jenmwms]

Thanks Andy! I'll have to work on better description here, then. Sounds like moving to the APIC timer driver which supports SMP enabled us to start trying > 1 CPUs on this board?

[jenmwms]

Found out that ACRN does not use the same values for local APIC IDs as the native EHL CRB. They use use virtualized APIC ID.
For a quad-core CPU: { 0x0, 0x1, 0x2, 0x3 };

• this should work ok with our __weak definition in arch/x86/core/intel64/cpu.c if I understand correctly.