Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Does LKL (Linux Kernel Library) fail to perform context switching when multiple threads invoke syscalls simultaneously? #600

@lotoohe-space

Description

@lotoohe-space

I found that when using it, if multiple threads are performing syscall simultaneously, LKL must wait until the kthread itself hangs before switching to other kthreads, and can only proactively give up the CPU. I checked UML and it seems that it supports actively giving up the CPU and implementing it through signals? Does LKL have any planned support for this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions