qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [5524] Fix windows build after migration changes
Date: Fri, 24 Oct 2008 14:11:42 +0000	[thread overview]
Message-ID: <E1KtNOA-0007AN-7Z@cvs.savannah.gnu.org> (raw)

Revision: 5524
          http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5524
Author:   aliguori
Date:     2008-10-24 14:11:41 +0000 (Fri, 24 Oct 2008)

Log Message:
-----------
Fix windows build after migration changes

The live migration code broke the windows build.  As part of this 
change, I've switched the BIOS path to C:\Program Files\Qemu instead of 
/c/Program Files/Qemu.  The later is only valid when launching from MSYS 
but the former is always valid.

Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>

Modified Paths:
--------------
    trunk/configure
    trunk/migration-tcp.c
    trunk/vl.c

Modified: trunk/configure
===================================================================
--- trunk/configure	2008-10-24 13:12:52 UTC (rev 5523)
+++ trunk/configure	2008-10-24 14:11:41 UTC (rev 5524)
@@ -953,7 +953,7 @@
 
 if test "$mingw32" = "yes" ; then
   if test -z "$prefix" ; then
-      prefix="/c/Program Files/Qemu"
+      prefix="c:\\\\Program Files\\\\Qemu"
   fi
   mansuffix=""
   datasuffix=""

Modified: trunk/migration-tcp.c
===================================================================
--- trunk/migration-tcp.c	2008-10-24 13:12:52 UTC (rev 5523)
+++ trunk/migration-tcp.c	2008-10-24 14:11:41 UTC (rev 5524)
@@ -84,7 +84,7 @@
     ssize_t ret;
 
     do {
-        ret = write(s->fd, data, size);
+        ret = send(s->fd, data, size, 0);
     } while (ret == -1 && errno == EINTR);
 
     if (ret == -1)
@@ -262,7 +262,7 @@
 	return NULL;
     }
 
-    fcntl(s->fd, F_SETFL, O_NONBLOCK);
+    socket_set_nonblock(s->fd);
 
     if (s->detach == 1) {
         dprintf("detaching from monitor\n");

Modified: trunk/vl.c
===================================================================
--- trunk/vl.c	2008-10-24 13:12:52 UTC (rev 5523)
+++ trunk/vl.c	2008-10-24 14:11:41 UTC (rev 5524)
@@ -6224,9 +6224,8 @@
         len = announce_self_create(buf, nd_table[i].macaddr);
         vlan = nd_table[i].vlan;
         for(vc = vlan->first_client; vc != NULL; vc = vc->next) {
-            if (vc->fd_read == tap_receive)  /* send only if tap */
-                for (j=0; j < SELF_ANNOUNCE_ROUNDS; j++)
-                    vc->fd_read(vc->opaque, buf, len);
+            for (j=0; j < SELF_ANNOUNCE_ROUNDS; j++)
+                vc->fd_read(vc->opaque, buf, len);
         }
     }
 }

             reply	other threads:[~2008-10-24 14:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 14:11 Anthony Liguori [this message]
2008-10-24 14:18 ` [Qemu-devel] [5524] Fix windows build after migration changes Robert Riebisch
2008-10-24 14:22   ` Glauber Costa
2008-10-24 14:55     ` Robert Riebisch
2008-10-24 15:05       ` Glauber Costa
2008-10-24 15:08         ` Robert Riebisch
2008-10-24 15:13           ` Glauber Costa
2008-10-24 14:25   ` Anthony Liguori
2008-10-24 15:01     ` Robert Riebisch
2008-10-24 15:11       ` Anthony Liguori
2008-10-24 15:13         ` Glauber Costa
2008-10-24 15:37         ` Paul Brook
2008-10-24 16:49           ` Anthony Liguori
2008-10-24 18:44           ` Andreas Färber

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=E1KtNOA-0007AN-7Z@cvs.savannah.gnu.org \
    --to=anthony@codemonkey.ws \
    --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).