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

Ensure popcorn cleanly handles failures #56

Open
bxatnarf opened this issue Oct 30, 2018 · 4 comments
Open

Ensure popcorn cleanly handles failures #56

bxatnarf opened this issue Oct 30, 2018 · 4 comments

Comments

@bxatnarf
Copy link
Collaborator

Popcorn doesn't cleanly handle all use cases. For example, it will block the kernel from shutting down while it is waiting for a page. We need to enumerate and fix other such failures/behaviors.

@bxatnarf
Copy link
Collaborator Author

bxatnarf commented Nov 26, 2018

Related issues:
#58
#59
#60

@bxatnarf
Copy link
Collaborator Author

With regards to failure enumeration: we should check how popcorn fails in every combination of popcorn protocol states among multiple hosts: one acting as host where process is spawned, a host from which the process is being migrated, and a host to which a process is being migrated.

@bxatnarf
Copy link
Collaborator Author

Related issue: #64

@bxatnarf
Copy link
Collaborator Author

Question: when a multithreaded and non-migrated process invokes syscalls such as mmap and munmap or page fault handlers, do other threads block? Is it ok that all threads block when when a remote thread invokes the same kernel operations?

@jnarf jnarf added enhancement and removed task labels Nov 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants