Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

arch/x86: QEMU doesn't appear to support x2APIC #19353

Closed
ghost opened this issue Sep 24, 2019 · 1 comment
Closed

arch/x86: QEMU doesn't appear to support x2APIC #19353

ghost opened this issue Sep 24, 2019 · 1 comment
Labels
area: X86 x86 Architecture (32-bit) bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@ghost
Copy link

ghost commented Sep 24, 2019 •
edited by ghost
Loading

Even with +x2apic, QEMU in the Zephyr SDK reports no x2APIC support in CPUID. This might be a matter of needing additional flags or lack of support in the build in the Zephyr SDK.

In any case this makes it necessary to test x2APIC on real hardware and thus x2APIC tests are excluded in CI runs.
@ghost ghost added bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug area: X86 x86 Architecture (32-bit) labels Sep 24, 2019
@ghost ghost self-assigned this Sep 24, 2019
@galak
Copy link
Collaborator

galak commented Sep 24, 2019

Even with +x2apic, QEMU in the Zephyr SDK reports no x2APIC support in CPUID. This might be a matter of needing additional flags or lack of support in the build in the Zephyr SDK.

In any case this makes it necessary to test x2APIC on real hardware and thus x2APIC tests are excluded in CI runs.

As far as I can tell the support should be in the SDK qemu, so its probably a flag passing/enabling issue.

@ghost ghost closed this as completed Oct 18, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: X86 x86 Architecture (32-bit) bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@galak