From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Stefan Weil <sw@weilnetz.de>
Subject: Re: [Qemu-devel] [PATCH] event: Add signal information to SHUTDOWN
Date: Wed, 12 Apr 2017 09:48:06 -0500 [thread overview]
Message-ID: <a2b472b4-6ec6-6f23-87e4-22b95169834b@redhat.com> (raw)
In-Reply-To: <87zifl3dcs.fsf@dusky.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
On 04/12/2017 09:33 AM, Markus Armbruster wrote:
>>> Additional ways to terminate QEMU: HMP and QMP command "quit", and the
>>> various GUI controls such "close SDL window".
>>
>> Good points. I have no idea what exit path those take (if they
>> raise(SIGINT) internally, it's quite easy - but if they go through some
>> other exit path, then I'll need to wire in something else).
>
> Chasing down all host-initiated terminations looks like a fool's errand
> to me. But if we can reliably detect guest-initiated, we don't have to,
> do we?
I don't know if we can reliably detect guest-initiated. Host-signal
initiated was easy because of the modification to a global variable.
But hopefully I'll find some easy common point, and maybe have to add
another global variable to track whether we went through that point (as
the reporting point is different than the request point). At any rate,
this conversation is useful, to make sure I find the right place.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-04-12 14:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 21:09 [Qemu-devel] [PATCH] event: Add signal information to SHUTDOWN Eric Blake
2017-04-07 9:35 ` Daniel P. Berrange
2017-04-07 13:45 ` Eric Blake
2017-04-13 6:04 ` Paolo Bonzini
2017-04-12 11:02 ` Markus Armbruster
2017-04-12 11:05 ` Daniel P. Berrange
2017-04-12 13:15 ` Eric Blake
2017-04-12 13:52 ` Markus Armbruster
2017-04-12 14:03 ` Eric Blake
2017-04-12 14:33 ` Markus Armbruster
2017-04-12 14:48 ` Eric Blake [this message]
2017-04-13 6:11 ` Paolo Bonzini
2017-04-13 6:11 ` Paolo Bonzini
2017-04-13 7:30 ` Markus Armbruster
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=a2b472b4-6ec6-6f23-87e4-22b95169834b@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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;
as well as URLs for NNTP newsgroup(s).