From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MWFOy-0003Xv-Gr for qemu-devel@nongnu.org; Wed, 29 Jul 2009 16:05:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MWFOt-0003Xj-SF for qemu-devel@nongnu.org; Wed, 29 Jul 2009 16:05:28 -0400 Received: from [199.232.76.173] (port=52162 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MWFOt-0003Xg-Py for qemu-devel@nongnu.org; Wed, 29 Jul 2009 16:05:23 -0400 Received: from mx20.gnu.org ([199.232.41.8]:41007) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MWFOs-0006SE-UL for qemu-devel@nongnu.org; Wed, 29 Jul 2009 16:05:23 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MWFOr-0003nB-WF for qemu-devel@nongnu.org; Wed, 29 Jul 2009 16:05:22 -0400 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH v2] make windows notice media change Date: Wed, 29 Jul 2009 21:05:18 +0100 References: <20090729120719.GN30449@redhat.com> <200907292052.35755.paul@codesourcery.com> <5b31733c0907291256r734416d2ifbe8b72105eba27c@mail.gmail.com> In-Reply-To: <5b31733c0907291256r734416d2ifbe8b72105eba27c@mail.gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907292105.19006.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Filip Navara Cc: qemu-devel@nongnu.org, Gleb Natapov > >> BTW, why would there be the version parameter in the first place if it > >> wasn't supposed to load older versions?! > > > > Like I already said: it's there to prevent an old version being loaded > > accidentally. Without this an incompatible change will result in > > anything from a crash to corrupt/inconsistent guest state. Versioning > > allows us to reject the snapshot and fail safely. > > If that was the case then the if (version != x) return -EINVAL check could > have been in the generic code and there would be no need for the version > parameter in the load function. Preventing loading bad snapshots is the primary goal. Allowing loading old snapshots is a secondary feature. Personally I think it's not worth the effort, and in practice is unlikely to be feasible for whole machines over any significant length of time. However I don't feel strongly enough to actually rip the code out. Paul