2011/6/23 Jan Kiszka <jan.kiszka@xxxxxx>: > On 2011-06-23 11:05, lidong chen wrote: >> Hi all, >> >> I didn't understand why need block all signal except SIGBUS SIGIPI for >> vcpu thread? > > For simplicity reasons: All other expected signals are handled by the > io-thread or other helper threads. Those must never be processed by the > vcpus. So we block everything except the required ones. > the signals like SIGSEGV,SIGTRAP, didn't used for io-thread. and if vcpu thread cause segmentation fault, it's better handle by vcpu thread itself. >> is it safe to register another signal handler? >> if somebody know the reason, please tell me. >> >> and is it worth to do this? > because the core dump file is too big, and the time of core dump is too long. I do a test, for a guest which have 9.7G memory, the coredump file is 9.7G, and the time of core dump is 1 minute. for the compute node in my system, there are a lot of cpu and memory resource, but no disk. total 4.5G -rw------- 1 root root 9.7G Jun 23 21:31 core-qemu-kvm-24090-1308835893 -rw------- 1 root root 3.9G Jun 23 21:34 core-qemu-kvm-24098-1308835996 > Better configure your host to create a core dump of the dying process. > That contains more information than you could ever collect ad-hoc by > patching qemu itself. > > Jan > > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
