From: Gleb Natapov <gleb@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] optionally specify vm stop message
Date: Fri, 16 Jan 2009 09:14:37 +0200 [thread overview]
Message-ID: <20090116071437.GB27165@redhat.com> (raw)
In-Reply-To: <496FA08E.4060806@codemonkey.ws>
On Thu, Jan 15, 2009 at 02:46:06PM -0600, Anthony Liguori wrote:
> Gleb Natapov wrote:
>> Should be applied on top of ENOSPC series.
>>
>
> How about just adding a new vm_stop reason? That will work out better
> when we introduce the improved monitor.
>
We may want to specify different message for the same reason. For
instance we may want to print the name of the file we failed to write
to. Also non zero reasons a handled differently by vm_stop. Don't know
why.
--
Gleb.
next prev parent reply other threads:[~2009-01-16 7:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 10:37 [Qemu-devel] [PATCH] optionally specify vm stop message Gleb Natapov
2009-01-15 20:46 ` Anthony Liguori
2009-01-16 7:14 ` Gleb Natapov [this message]
2009-01-16 15:26 ` Anthony Liguori
2009-01-16 16:24 ` [Qemu-devel] " Jan Kiszka
2009-01-16 16:27 ` Anthony Liguori
2009-01-16 16:36 ` Jan Kiszka
2009-01-16 16:45 ` Jan Kiszka
2009-01-16 17:02 ` Jan Kiszka
2009-01-16 17:14 ` Anthony Liguori
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=20090116071437.GB27165@redhat.com \
--to=gleb@redhat.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 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).