From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:51671) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T8mxi-0000kW-6E for qemu-devel@nongnu.org; Tue, 04 Sep 2012 02:50:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T8mxc-0006o6-Ew for qemu-devel@nongnu.org; Tue, 04 Sep 2012 02:50:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46691) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T8mxc-0006kt-6H for qemu-devel@nongnu.org; Tue, 04 Sep 2012 02:50:08 -0400 Message-ID: <5045A499.1030505@redhat.com> Date: Tue, 04 Sep 2012 08:50:01 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1346663926-20188-1-git-send-email-xiawenc@linux.vnet.ibm.com> <1346663926-20188-2-git-send-email-xiawenc@linux.vnet.ibm.com> <5044AE18.5030503@redhat.com> <50457267.2080806@linux.vnet.ibm.com> In-Reply-To: <50457267.2080806@linux.vnet.ibm.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 1/6] libqblock APIs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Wenchao Xia Cc: kwolf@redhat.com, stefanha@gmail.com, aliguori@us.ibm.com, eblake@redhat.com, qemu-devel@nongnu.org Il 04/09/2012 05:15, Wenchao Xia ha scritto: >> >> Can you use GError instead? >> > read through the GError doc, GError is defined as following: > struct GError { > GQuark domain; > gint code; > gchar *message; > }; > I am worried about the message member, I guess program would be > aborted if OOM, which I was tring to avoid, so I used char err_msg[1024] > in my code, and make things simpler. That's true. On the other hand, and IMHO, not aborting in the library code is a non-goal as long as the rest of the block layer still does. >>> 3 QBlockInfoImageStatic. Now it is not folded with location and >>> format. >> >> What does "Static" mean? >> > It is about sorting the information into following kinds: > 1) static. It is values that defined at creating time/modifying time, > mostly some settings, and it would not be automatically changed in I/O. > 2) dynamic. Some information that would changes in I/O and other > operations, such as allocated_size, snapshots. > 3) statistics. > Now only static one is provided, so I added _static suffix. Makes sense, thanks for the clarification. Perhaps QBlockStaticInfo is a shorter and simpler name? Paolo