From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48756) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UzpJ0-0005XB-4T for qemu-devel@nongnu.org; Thu, 18 Jul 2013 10:35:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UzpIz-000398-2H for qemu-devel@nongnu.org; Thu, 18 Jul 2013 10:35:42 -0400 Received: from mx1.redhat.com ([209.132.183.28]:28099) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UzpIy-00038s-RC for qemu-devel@nongnu.org; Thu, 18 Jul 2013 10:35:40 -0400 Message-ID: <51E7FD2E.5070900@redhat.com> Date: Thu, 18 Jul 2013 16:35:26 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1373885375-13601-5-git-send-email-pl@kamp.de> <20130717084648.GD2458@dhcp-200-207.str.redhat.com> <51E66ACD.70706@redhat.com> <20130717102551.GF2458@dhcp-200-207.str.redhat.com> <51E6C5FC.1030304@redhat.com> <7C1EEB41-E2B3-4186-9188-379F02E76FF9@kamp.de> <51E6CE81.6000400@redhat.com> <36C25446-54C7-4D1F-9D8D-E8A3991489BD@kamp.de> <20130718092316.GG3582@dhcp-200-207.str.redhat.com> <51E7C260.50404@redhat.com> <51E7C707.7010101@kamp.de> <51E7C9C4.5010202@redhat.com> <51E7CBC8.1010804@kamp.de> <51E7E035.3010702@redhat.com> <51E7EDD0.6050001@kamp.de> <51E7F332.9020607@redhat.com> <51E7F715.3020706@kamp.de> <51E7F9CB.7050304@redhat.com> <51E7FC87.1040207@kamp.de> In-Reply-To: <51E7FC87.1040207@kamp.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 4/4] qemu-img: conditionally discard target on convert List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven Cc: Kevin Wolf , Stefan Hajnoczi , qemu-devel , ronnie sahlberg Il 18/07/2013 16:32, Peter Lieven ha scritto: >>> >> (Mis)alignment and granularity can be handled later. We can ignore them >> for now. Later, if we decide the best way to support them is a flag, >> we'll add it. Let's not put the cart before the horse. >> >> BTW, I expect alignment!=0 to be really, really rare. > To explain my concerns: > > I know that my target has internal page size of 15MB. I will check what > happens > if I deallocate this 15MB in chunks of lets say 1MB. If the page gets > unprovisioned > after the last chunk is unmapped it would be fine :-) You're talking of granularity here, not (mis)alignment. Paolo