-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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.
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
[v2.7] X86: direct MSI message to proper processor #43690
[v2.7] X86: direct MSI message to proper processor #43690
Conversation
This will centralize CPUID related accessors. There was no need for it so far, but this is going to change. Signed-off-by: Tomasz Bursztyka <[email protected]>
Depending on whether X2APIC is enabled or not, it will be safer to grab such ID from the right place. Signed-off-by: Tomasz Bursztyka <[email protected]>
@tbursztyka - please create an issue for the backport. |
When Zephyr runs directly on actual hardware, it will be always directing MSI messages to BSP (BootStrap Processor). This was fine until Zephyr could be ran on virtualizor that may NOT run it on BSP. So directing MSI messages on current processor. If Zephyr runs on actual hardware, it will be BSP since such setup is always made at boot time by the BSP. On other use case it will be whatever is relevant at that time. Fixes zephyrproject-rtos#43853 Signed-off-by: Tomasz Bursztyka <[email protected]>
304d870
to
27b3acc
Compare
@cfriedt done, I added the "Fixes" line in last commit |
@tbursztyka @cfriedt GitHub doesn't recognize such references in commit messages. It works only by chance for single-commit PRs, since the message is replicated in the PR description (which is, AFAIK, the only place where those references are recognized). You can see this by the fact that as of writing this message the issue still isn't closed, even though this PR got merged. |
#43853 is the issue ID by the looks of it |
Backport of #42480 to 2.7.
Fixes #43853