From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Reset system before loadvm
Date: Tue, 14 Jun 2011 14:14:58 +0300 [thread overview]
Message-ID: <4DF742B2.9010006@redhat.com> (raw)
In-Reply-To: <4DF73E52.8090004@siemens.com>
On 06/14/2011 01:56 PM, Jan Kiszka wrote:
> >
> > I believe it is not. But regardless, we shouldn't add more incorrect
> > behaviour.
>
> It depends on how the reset event is defined in QMP. As I see it, there
> is nothing stated about reset reasons or sources. So emitting
> information about the actually happening reset can't be incorrect. Just
> like emitting the information about the VM stop/start around loadvm.
I don't think so. Theoretically we could stop the vm, save a bit of
state, reset it, and load the state back. Did a reset occur? Not from
the user's point of view.
If a reset event is interesting (personally I don't think it is, so
much, perhaps just for logging purposes), we should restrict it to user
visible events (so it means either the user pressed the reset button or
the guest reset itself).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-06-14 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 9:05 [Qemu-devel] [PATCH] Reset system before loadvm Jan Kiszka
2011-06-12 17:13 ` Avi Kivity
2011-06-14 6:19 ` Jan Kiszka
2011-06-14 10:50 ` Avi Kivity
2011-06-14 10:56 ` Jan Kiszka
2011-06-14 11:14 ` Avi Kivity [this message]
2011-06-14 15:45 ` Luiz Capitulino
2011-06-12 17:42 ` Peter Maydell
2011-06-14 6:16 ` Jan Kiszka
2011-06-14 16:29 ` [Qemu-devel] [PATCH 1/2] Allow silent system resets Jan Kiszka
2011-06-15 14:32 ` Luiz Capitulino
2011-06-14 16:29 ` [Qemu-devel] [PATCH v2 2/2] Reset system before loadvm Jan Kiszka
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=4DF742B2.9010006@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=lcapitulino@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).