From: Avi Kivity <avi@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
dlaor@redhat.com, Chris Wright <chrisw@sous-sol.org>,
Juan Quintela <quintela@redhat.com>,
chrisw@redhat.com,
"Venkateswararao Jujjuri (JV)" <jvrao@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
Ayal Baron <abaron@redhat.com>
Subject: Re: [Qemu-devel] Re: KVM call agenda for Oct 19
Date: Tue, 19 Oct 2010 15:55:19 +0200 [thread overview]
Message-ID: <4CBDA347.6030509@redhat.com> (raw)
In-Reply-To: <AANLkTikAeWo-HXSSSHHEOmKzVw=zuX8iamFPxOHvnRS3@mail.gmail.com>
On 10/19/2010 03:38 PM, Stefan Hajnoczi wrote:
> bdrv_aio_freeze() or any mechanism to deal with pending requests in
> the generic block code would be a good step for future "live" support
> of other operations like truncate.
+ logical disk grow, etc.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-10-19 13:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 15:43 KVM call agenda for Oct 19 Juan Quintela
2010-10-19 2:11 ` Chris Wright
2010-10-19 12:48 ` [Qemu-devel] " Dor Laor
2010-10-19 12:55 ` Avi Kivity
2010-10-19 12:58 ` Dor Laor
2010-10-19 13:03 ` Avi Kivity
2010-10-19 13:18 ` Anthony Liguori
2010-10-19 13:22 ` Anthony Liguori
2010-10-19 13:27 ` Avi Kivity
2010-10-19 13:33 ` Anthony Liguori
2010-10-19 13:38 ` Stefan Hajnoczi
2010-10-19 13:55 ` Avi Kivity [this message]
2010-10-19 13:28 ` Anthony Liguori
[not found] <314565543.45891287507100965.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2010-10-19 16:54 ` Ayal Baron
2010-10-19 17:09 ` Anthony Liguori
2010-10-20 9:18 ` Kevin Wolf
2010-10-20 9:41 ` Ayal Baron
2010-10-20 13:05 ` Anthony Liguori
[not found] <512838278.79671287521779658.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2010-10-19 20:57 ` Ayal Baron
2010-10-19 21:19 ` 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=4CBDA347.6030509@redhat.com \
--to=avi@redhat.com \
--cc=abaron@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=chrisw@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=dlaor@redhat.com \
--cc=jvrao@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox