From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
Heinz Graalfs <graalfs@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Einar Lueck <elelueck@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 4/5] s390: sclp signal quiesce support
Date: Fri, 12 Oct 2012 06:12:47 +0200 [thread overview]
Message-ID: <507798BF.60800@de.ibm.com> (raw)
In-Reply-To: <56E47479-7480-48C9-84B3-96A960155CEA@suse.de>
On 12/10/12 02:36, Alexander Graf wrote:
>
> On 02.10.2012, at 09:33, Jens Freimann wrote:
>
>> From: Heinz Graalfs <graalfs@linux.vnet.ibm.com>
>>
>> This implements the sclp signal quiesce event via the SCLP Event
>> Facility.
>> This allows to gracefully shutdown a guest by using system_powerdown
>> notifiers. It creates a service interrupt that will trigger a
>> Read Event Data command from the guest. This code will then add an
>> event that is interpreted by linux guests as ctrl-alt-del.
>
> Doesn't ctrl-alt-del usually reboot the machine, not shut it down?
On my 390 systems it seems to shutdown, at least that happens on lpar and
z/VM as well as under KVM.
next prev parent reply other threads:[~2012-10-12 4:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 7:33 [Qemu-devel] [PATCH 0/5] s390: current patches Jens Freimann
2012-10-02 7:33 ` [Qemu-devel] [PATCH 1/5] s390: use sync regs for register transfer Jens Freimann
2012-10-03 20:08 ` Blue Swirl
2012-10-04 7:56 ` [Qemu-devel] [PATCH] " Jens Freimann
2012-10-02 7:33 ` [Qemu-devel] [PATCH 2/5] s390: sclp base support Jens Freimann
2012-10-02 7:33 ` [Qemu-devel] [PATCH 3/5] s390: sclp event support Jens Freimann
2012-10-02 7:33 ` [Qemu-devel] [PATCH 4/5] s390: sclp signal quiesce support Jens Freimann
2012-10-12 0:36 ` Alexander Graf
2012-10-12 4:12 ` Christian Borntraeger [this message]
2012-10-02 7:33 ` [Qemu-devel] [PATCH 5/5] s390: sclp ascii console support Jens Freimann
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=507798BF.60800@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=agraf@suse.de \
--cc=cornelia.huck@de.ibm.com \
--cc=elelueck@linux.vnet.ibm.com \
--cc=graalfs@linux.vnet.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.