qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Uri Lublin <uril@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] migration: adding migration to/from a file (v2)
Date: Thu, 19 Feb 2009 18:14:28 +0200	[thread overview]
Message-ID: <499D8564.1070007@redhat.com> (raw)
In-Reply-To: <499D652D.60803@codemonkey.ws>

Anthony Liguori wrote:
> Uri Lublin wrote:
>>
>> Migration to file, uses migration-to-fd (supports live migration).
>> Migration from file, uses qemu-fopen directly.
> 
> Eh?  Haven't we already talked about why this doesn't work?  Maybe 
> there's a v3 that you meant to send?
> 

Actually I do have a v3 which uses posix-aio-compat.c
It's a much more complicated solution then just writing to a file though.
Also I am not sure if I need to use a signal or not as the migration (to-fd) 
code is polling. And if I use signal should I use SIGUSR2 or a different one and 
use a pipe similar to block-raw-posix.c ?

Your concern in the previous patch was that write() to a regular file might 
block. That's why I'm calling select before calling write. Do you think select 
will mark the fd as writeable but write would still block ?

Thanks,
     Uri.

  reply	other threads:[~2009-02-19 16:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19 11:45 [Qemu-devel] migration: adding migration to/from a file (v2) Uri Lublin
2009-02-19 13:57 ` Anthony Liguori
2009-02-19 16:14   ` Uri Lublin [this message]
2009-02-19 16:51     ` Anthony Liguori
2009-02-19 19:06       ` Uri Lublin
2009-02-19 20:05         ` Anthony Liguori
2009-02-19 20:28           ` Jamie Lokier
2009-02-19 23:36             ` M. Warner Losh
2009-02-19 23:59               ` Anthony Liguori
2009-02-20  0:36                 ` M. Warner Losh
2009-02-19 20:45           ` Uri Lublin
2009-02-19 19:37       ` Jamie Lokier
2009-02-19 20:06         ` Anthony Liguori
2009-02-19 19:33     ` 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=499D8564.1070007@redhat.com \
    --to=uril@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).