ltp : KVM_EXIT_INTR - Githubissues

Martins3 / loongson-dune

:zap: Process virtualization based on KVM. More useable, stable and practical than Stanford Dune.

20 stars 3 forks source link

Closed Martins3 closed 3 years ago

Martins3 commented 3 years ago

[x] create a program that we will come across KVM_EXIT_INTR 100%
[x] If I define a signal handler, will it handled in guest space or host space? (host)

Martins3 commented 3 years ago

I think the signal(Ctrl-C) will no captured immediately after it happened, but in fact, it's doesn't work as expected.

    while (true) {
        sleep(4);
        printf("sleep\n");
    }

No, the assumption is wrong, the sleep causes the process to jump into kernel space, so the signal will be captured immediately.

Martins3 commented 3 years ago

[x] sighandler executed when syscall returns, so it's IOCTL return or just WRITE return?
- I think it doesn't matter, now that sighandler will not obstruct the syscall, so it just makes no difference whether is executed after ioctl or not.