All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC] qemu-file: output data directly if possible
Date: Mon, 10 Oct 2011 11:25:57 +0200	[thread overview]
Message-ID: <4E92BA25.807@redhat.com> (raw)
In-Reply-To: <20111010131639.GB23679@redhat.com>

On 10/10/2011 03:16 PM, Michael S. Tsirkin wrote:
> Yes, it does look sane. QEMUFile doesn't seem to ever be used without
> QEMUBufferedFile - is that true?

I think savevm does use it that way.  With migration thread it will be 
much easier, because the migration thread can just block.  I'd hold it 
off until Juan's patches are in and then I can rebase Umesh's patches 
for migration thread.

Paolo

  reply	other threads:[~2011-10-10  9:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09 23:56 [Qemu-devel] [PATCH RFC] qemu-file: output data directly if possible Michael S. Tsirkin
2011-10-10  7:42 ` Paolo Bonzini
2011-10-10 13:16   ` Michael S. Tsirkin
2011-10-10  9:25     ` Paolo Bonzini [this message]
2011-10-11  9:19     ` Juan Quintela

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=4E92BA25.807@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=mst@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 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.