From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Adam Litke <agl@us.ibm.com>
Subject: Re: [Qemu-devel] Re: virtio: Report new guest memory statistics pertinent to memory ballooning (V4)
Date: Mon, 23 Nov 2009 12:47:34 -0600 [thread overview]
Message-ID: <4B0AD8C6.7030103@codemonkey.ws> (raw)
In-Reply-To: <4B056C17.1020003@redhat.com>
Avi Kivity wrote:
> The new monitor will support async command completion but even then I
> don't think we should allow a guest to stop command execution
> indefinitely (it would tie up resources at the client).
Well, I think we're going to end up pushing this to 0.13 as we're
quickly approaching the 0.12 freeze. In that case, let's not bother
doing two commands and let's rely on adding asynchronous result
reporting in qmp.
Freezing the monitor isn't really a DoS today as we support multiple
monitors.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-11-23 18:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 15:06 [Qemu-devel] virtio: Report new guest memory statistics pertinent to memory ballooning (V4) Adam Litke
2009-11-19 15:19 ` [Qemu-devel] virtio: Add memory statistics reporting to the balloon driver (V3) Adam Litke
2009-11-19 15:22 ` [Qemu-devel] " Avi Kivity
2009-11-19 15:58 ` Adam Litke
2009-11-19 16:13 ` Avi Kivity
2009-11-19 16:29 ` Adam Litke
2009-11-19 23:53 ` Rusty Russell
2009-11-23 9:44 ` Michael S. Tsirkin
2009-11-23 11:00 ` Dor Laor
2009-11-23 11:31 ` Vadim Rozenfeld
2009-11-19 15:19 ` [Qemu-devel] Re: virtio: Report new guest memory statistics pertinent to memory ballooning (V4) Avi Kivity
2009-11-19 15:56 ` Adam Litke
2009-11-19 16:02 ` Avi Kivity
2009-11-23 18:47 ` Anthony Liguori [this message]
2009-11-20 1:24 ` Jamie Lokier
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=4B0AD8C6.7030103@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agl@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=avi@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).