public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: lidong chen <chen.lidong.kernel@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: collect some information when qemu-kvm exit
Date: Thu, 23 Jun 2011 12:13:15 +0200	[thread overview]
Message-ID: <4E0311BB.2000206@web.de> (raw)
In-Reply-To: <BANLkTikoUbu7X8buGznVgis+f+zqANRF1w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

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.

> is it safe to register another signal handler?
> if somebody know the reason, please tell me.
> 
> 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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2011-06-23 10:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 12:27 collect some information when qemu-kvm exit lidong chen
2011-06-23  9:05 ` lidong chen
2011-06-23 10:13   ` Jan Kiszka [this message]
2011-06-23 13:56     ` lidong chen
2011-06-23 14:51       ` Jan Kiszka
2011-06-24  8:24         ` lidong chen
2011-06-24  8:55           ` Jan Kiszka
2011-06-24  8:58             ` Jan Kiszka
2011-06-24 13:26               ` lidong chen
2011-07-02 11:22                 ` lidong chen
2011-07-07  1:20                   ` lidong chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E0311BB.2000206@web.de \
    --to=jan.kiszka@web.de \
    --cc=chen.lidong.kernel@gmail.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox