From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mr016-0004Ee-FN for qemu-devel@nongnu.org; Thu, 24 Sep 2009 21:54:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mr012-0004D0-F9 for qemu-devel@nongnu.org; Thu, 24 Sep 2009 21:54:36 -0400 Received: from [199.232.76.173] (port=39185 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mr012-0004Cv-Af for qemu-devel@nongnu.org; Thu, 24 Sep 2009 21:54:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60284) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mr011-0000fK-OB for qemu-devel@nongnu.org; Thu, 24 Sep 2009 21:54:32 -0400 Received: from int-mx08.intmail.prod.int.phx2.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n8P1sUcu009588 for ; Thu, 24 Sep 2009 21:54:30 -0400 Subject: Re: [Qemu-devel] [PATCH] Fix exit on 'pci_add' Monitor command References: <20090924111601.1d3668d2@doriath> <87iqf8ciup.fsf@pike.pond.sub.org> <1253822824.32256.55.camel@blaa> From: Markus Armbruster Date: Fri, 25 Sep 2009 03:51:42 +0200 In-Reply-To: <1253822824.32256.55.camel@blaa> (Mark McLoughlin's message of "Thu\, 24 Sep 2009 21\:07\:04 +0100") Message-ID: <87eipv6bbl.fsf@pike.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mark McLoughlin Cc: qemu-devel@nongnu.org, Luiz Capitulino Mark McLoughlin writes: > On Thu, 2009-09-24 at 20:12 +0200, Markus Armbruster wrote: >> My major complaint is that I'd rather see the code cleaned up there. >> It's perfectly fine for code that can run only during startup to >> terminate the program on configuration error. Code to be used after >> startup (used from monitor, in particular) must not do that. Instead, >> it should return failure up the call chain, until we reach either >> startup code or monitor code, where the policy how to handle the error >> resides. > > Agree, I'd like to see it cleaned up. > > However, Luiz's patch fixes the most serious side effect without a major > re-factoring, so I'd like to see that go in first (and stable-0.11) and > do the re-factoring later. Certainly fine with me if my cleanup is deemed to invasive for stable.