From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: collect some information when qemu-kvm exit Date: Thu, 23 Jun 2011 12:13:15 +0200 Message-ID: <4E0311BB.2000206@web.de> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF7D4733A0F806E1CF6084A4C" Cc: kvm@vger.kernel.org To: lidong chen Return-path: Received: from fmmailgate02.web.de ([217.72.192.227]:56929 "EHLO fmmailgate02.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758245Ab1FWKNR (ORCPT ); Thu, 23 Jun 2011 06:13:17 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF7D4733A0F806E1CF6084A4C Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-06-23 11:05, lidong chen wrote: > Hi all, >=20 > 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. > is it safe to register another signal handler? > if somebody know the reason, please tell me. >=20 > and is it worth to do this? 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 --------------enigF7D4733A0F806E1CF6084A4C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk4DEbsACgkQitSsb3rl5xQS6gCdGNm4A0SeR5C1Ig/8qm65Y5lD 8iMAoIe9y82AX8FuTlmsdu/5osUwXm10 =bEiX -----END PGP SIGNATURE----- --------------enigF7D4733A0F806E1CF6084A4C--