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] [6998] create qemu_file_set_error (Glauber Costa)
Date: Sun, 05 Apr 2009 19:30:51 +0000	[thread overview]
Message-ID: <E1LqY3P-0000n8-Fl@cvs.savannah.gnu.org> (raw)

Revision: 6998
          http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6998
Author:   aliguori
Date:     2009-04-05 19:30:51 +0000 (Sun, 05 Apr 2009)
Log Message:
-----------
create qemu_file_set_error (Glauber Costa)

This is mainly for consistency, since we don't want
anything outside of savevm setting it explicitly. There
are current no users of that in qemu tree, but there
are potential candidates on kvm-userspace. And avi
is a nice guy, let's be nice with him.

Based on a patch by Yaniv Kamay

Signed-off-by: Glauber Costa <glommer@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>

Modified Paths:
--------------
    trunk/hw/hw.h
    trunk/savevm.c

Modified: trunk/hw/hw.h
===================================================================
--- trunk/hw/hw.h	2009-04-05 19:30:33 UTC (rev 6997)
+++ trunk/hw/hw.h	2009-04-05 19:30:51 UTC (rev 6998)
@@ -67,6 +67,7 @@
 uint64_t qemu_get_be64(QEMUFile *f);
 int qemu_file_rate_limit(QEMUFile *f);
 int qemu_file_has_error(QEMUFile *f);
+void qemu_file_set_error(QEMUFile *f);
 
 /* Try to send any outstanding data.  This function is useful when output is
  * halted due to rate limiting or EAGAIN errors occur as it can be used to

Modified: trunk/savevm.c
===================================================================
--- trunk/savevm.c	2009-04-05 19:30:33 UTC (rev 6997)
+++ trunk/savevm.c	2009-04-05 19:30:51 UTC (rev 6998)
@@ -370,6 +370,11 @@
     return f->has_error;
 }
 
+void qemu_file_set_error(QEMUFile *f)
+{
+    f->has_error = 1;
+}
+
 void qemu_fflush(QEMUFile *f)
 {
     if (!f->put_buffer)

                 reply	other threads:[~2009-04-05 19:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E1LqY3P-0000n8-Fl@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).