You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you absolutely hammer the shortcut script with multiple vm cores & a nop program, you can trigger a silent barf, perhaps a deadlock w/ the core nop was running on in the page fault handler (including the mitigation) and the other core
Shell for i in $(seq 1 5000); do make run_be; done
Ali thinks this is about an IPI during a tlb shootdown which is prepared on a user stack & inaccessible to the remote core (b/c it doesn't have the user pg table loaded).
The text was updated successfully, but these errors were encountered:
If you absolutely hammer the shortcut script with multiple vm cores & a nop program, you can trigger a silent barf, perhaps a deadlock w/ the core nop was running on in the page fault handler (including the mitigation) and the other core
Makefile:
Shell
for i in $(seq 1 5000); do make run_be; done
Ali thinks this is about an IPI during a tlb shootdown which is prepared on a user stack & inaccessible to the remote core (b/c it doesn't have the user pg table loaded).
The text was updated successfully, but these errors were encountered: