Skip to content

VMM signaling interrupts were not reaching MigTD #372

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
Open
jyao1 opened this issue Apr 14, 2025 · 0 comments
Open

VMM signaling interrupts were not reaching MigTD #372

jyao1 opened this issue Apr 14, 2025 · 0 comments
Assignees
@gaojiaqi7

Comments

@jyao1
Copy link
Contributor

jyao1 commented Apr 14, 2025

VMCALL_VECTOR (0x52) callback is not getting registered for send/receive in concurrent (async_multiple_session as well as Main) branch; send/receive were still working because of the reply.status() check in poll_fn that the VMM code updates; VMM signaling interrupts were not reaching MigTD.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gaojiaqi7 gaojiaqi7

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jyao1 @gaojiaqi7