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] [6820] Revert r6405
Date: Wed, 11 Mar 2009 20:16:13 +0000	[thread overview]
Message-ID: <E1LhUqb-0005lX-CB@cvs.savannah.gnu.org> (raw)

Revision: 6820
          http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6820
Author:   aliguori
Date:     2009-03-11 20:16:12 +0000 (Wed, 11 Mar 2009)
Log Message:
-----------
Revert r6405

This series is broken by design as it requires expensive IO operations at
open time causing very long delays when starting a virtual machine for the
first time.

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

Modified Paths:
--------------
    branches/stable_0_10_0/block-qcow2.c
    branches/stable_0_10_0/block.h

Modified: branches/stable_0_10_0/block-qcow2.c
===================================================================
--- branches/stable_0_10_0/block-qcow2.c	2009-03-11 20:16:05 UTC (rev 6819)
+++ branches/stable_0_10_0/block-qcow2.c	2009-03-11 20:16:12 UTC (rev 6820)
@@ -1645,7 +1645,6 @@
     bdi->cluster_size = s->cluster_size;
     bdi->vm_state_offset = (int64_t)s->l1_vm_state_index <<
         (s->cluster_bits + s->l2_bits);
-    bdi->highest_alloc = s->highest_alloc << s->cluster_bits;
     return 0;
 }
 

Modified: branches/stable_0_10_0/block.h
===================================================================
--- branches/stable_0_10_0/block.h	2009-03-11 20:16:05 UTC (rev 6819)
+++ branches/stable_0_10_0/block.h	2009-03-11 20:16:12 UTC (rev 6820)
@@ -26,7 +26,6 @@
     int cluster_size;
     /* offset at which the VM state can be saved (0 if not possible) */
     int64_t vm_state_offset;
-    int64_t highest_alloc; /* highest allocated block offset (in bytes) */
 } BlockDriverInfo;
 
 typedef struct QEMUSnapshotInfo {

                 reply	other threads:[~2009-03-11 20:16 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=E1LhUqb-0005lX-CB@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).