From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MthXT-0006VR-Sm for qemu-devel@nongnu.org; Fri, 02 Oct 2009 08:47:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MthXP-0006U0-NC for qemu-devel@nongnu.org; Fri, 02 Oct 2009 08:47:11 -0400 Received: from [199.232.76.173] (port=33176 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MthXP-0006Tx-Js for qemu-devel@nongnu.org; Fri, 02 Oct 2009 08:47:07 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51947) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MthXP-0000Mq-25 for qemu-devel@nongnu.org; Fri, 02 Oct 2009 08:47:07 -0400 Message-ID: <4AC5F646.9040800@redhat.com> Date: Fri, 02 Oct 2009 14:47:02 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH v1 00/14]: Initial QObject conversion References: <1254412245-10452-1-git-send-email-lcapitulino@redhat.com> In-Reply-To: <1254412245-10452-1-git-send-email-lcapitulino@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, avi@redhat.com Hi, > Some people have suggested that we should have a better error handling > in the Monitor, in the meaning that error information should be correctly > propagated and handled in order to be used by the Monitor Protocol and > the existing user protocol. A bunch of code paths can be called from both monitor and non-monitor contexts (network configuration, device hotplug). Right now there are the qemu_error*() functions to make sure the error messages appear on the correct place (monitor or stderr) without having to pass through a Monitor pointer all the way down. How do you plan to handle this in the new world of monitor error reporting? cheers, Gerd