[v2.7-auditable] X86: direct MSI message to proper processor #43691
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
March 11, 2022 09:33
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
requested review from
jhedberg,
dcpleung,
nashif and
aasthagr
as code owners
github-actions
bot
added
area: API
dcpleung
approved these changes
Mar 11, 2022
jhedberg
approved these changes
Mar 13, 2022
|
CI failed but not because of the commits, can someone restart a CI check? |
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#43854 Signed-off-by: Tomasz Bursztyka <[email protected]>
tbursztyka
force-pushed
the
backport-42480-to-v2.7-auditable-branch
branch
from
6b11db3 to
138e417
Compare
tbursztyka
changed the title
pqueirosint
reviewed
Mar 16, 2022
|
Who is in charge of merging to 2.7-auditable? These commits have been already merged to 2.7. |
|
@nashif are you able to merge this one? (I could not figure out who's in charge of this branch). Thanks |
|
@pqueirosint can you re-approve? |
why do you need to merge this into this branch? it should go into 2.7 and it will be taken from there, you should not backport directly to the auditable branch. |
nashif
requested changes
Apr 12, 2022
|
@nashif ok good to know, hard to guess an undocumented process (unless I missed it) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport #42480 to v2.7 auditable branch
Fixes #43854
Fixes #44797