From: Anthony Liguori <aliguori@us.ibm.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [PATCH][RESEND] Add monitor command for system_reboot
Date: Wed, 08 Jul 2009 11:02:04 -0500 [thread overview]
Message-ID: <4A54C2FC.1000109@us.ibm.com> (raw)
In-Reply-To: <20090708155810.GU11590@us.ibm.com>
Ryan Harper wrote:
>> It's a different class of non-determinism though. With
>> system_powerdown, you make a request to the guest. You don't know
>> whether the guest will comply with the request. The same level of
>> non-determinism exists with ballooning.
>>
>> With system_reboot, you're taking an action (system_reset) and what's
>> not deterministic is whether you're taking that action based on what
>> someone requested on the monitor (system_reboot) verses whether you're
>> taking that action based on something the user did (shutdown). In the
>> later case, you're action is functionally incorrect.
>>
>
> Only if the shutdown from the user occurs in timeout period. So, yes,
> it's still present, but the window of the behavior can be much
> smaller.
>
> I still think this is a reasonable approach even with that window.
>
It's still a policy decision and the question is whether QEMU is the
right place to implement that policy. QEMU provides a mechanism today
to implement this policy (system_powerdown followed by polling via info
status followed by system_reset).
I tend to agree with Avi that we don't want to implement these sort of
policies in QEMU and that we instead want to take a PV approach that can
let us eliminate the nastier non-determinism.
--
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-07-08 16:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 19:26 [Qemu-devel] [PATCH][RESEND] Add monitor command for system_reboot Ryan Harper
2009-07-08 5:06 ` Avi Kivity
2009-07-08 13:07 ` Anthony Liguori
2009-07-08 13:11 ` Avi Kivity
2009-07-08 13:16 ` Anthony Liguori
2009-07-08 13:28 ` Avi Kivity
2009-07-08 7:56 ` Gleb Natapov
2009-07-08 13:05 ` Anthony Liguori
2009-07-08 13:26 ` Daniel P. Berrange
2009-07-08 13:47 ` Anthony Liguori
2009-07-08 13:56 ` Daniel P. Berrange
2009-07-08 13:59 ` Anthony Liguori
2009-07-08 15:43 ` Ryan Harper
2009-07-08 15:49 ` Anthony Liguori
2009-07-08 15:58 ` Ryan Harper
2009-07-08 16:02 ` Anthony Liguori [this message]
2009-07-08 16:02 ` Avi Kivity
2009-07-16 8:58 ` Amit Shah
2009-07-16 14:39 ` Jamie Lokier
2009-07-16 14:49 ` Amit Shah
2009-07-08 13:49 ` Gleb Natapov
2009-07-08 14:04 ` Avi Kivity
2009-07-08 14:10 ` Daniel P. Berrange
2009-07-08 15:16 ` Avi Kivity
2009-07-08 15:47 ` Stefano Stabellini
2009-07-08 15:54 ` Daniel P. Berrange
2009-07-08 15:59 ` Stefano Stabellini
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=4A54C2FC.1000109@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=gleb@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.ibm.com \
/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.