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.

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

Question about the priority order for handling interrupts from multiple supervisor domains #113

Open
xlxxxxxl opened this issue Nov 21, 2024 · 0 comments

Comments

@xlxxxxxl
Copy link

The default interrupt handling priority described in Section 6.4. And with the Note below, RDSM will clear the bit corresponding to that interrupt controller selected by msdcfg.SDICN in msdeie prior to resuming execution of the supervisor domain.

Here I have a question:
When both a "non-active supervisor domain interrupt (LSDEIP)" and an "active supervisor domain interrupt (VSEI)" occur simultaneously, why is the default to prioritize handling interrupts from other domains rather than prioritizing TVM interrupts within the current active domain?
If currently in the confidential supervisor domain, TSM needs to perform a TEERET to the VMM, leaving the scheduling decision to the VMM.

When interrupts occur in multiple supervisor domains simultaneously, if each domain prioritizes handling interrupts from other domains, could this lead to a "domain scheduling storm" where no interrupt is actually processed to completion?

Looking forward to your answer, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant