From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35300) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xosuy-0003ks-RD for qemu-devel@nongnu.org; Thu, 13 Nov 2014 06:50:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xosut-0000tL-Ti for qemu-devel@nongnu.org; Thu, 13 Nov 2014 06:50:28 -0500 Message-ID: <54649AD4.8040806@huawei.com> Date: Thu, 13 Nov 2014 19:49:40 +0800 From: Gonglei MIME-Version: 1.0 References: <1415846372-12756-1-git-send-email-arei.gonglei@huawei.com> <20141113112734.GN7462@stefanha-thinkpad.redhat.com> In-Reply-To: <20141113112734.GN7462@stefanha-thinkpad.redhat.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] virtio-bus: avoid breaking build when open DEBUG switch List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: "qemu-trivial@nongnu.org" , "mst@redhat.com" , "qemu-devel@nongnu.org" , "Huangpeng (Peter)" On 2014/11/13 19:27, Stefan Hajnoczi wrote: > On Thu, Nov 13, 2014 at 10:39:32AM +0800, arei.gonglei@huawei.com wrote: >> From: Gonglei >> >> Signed-off-by: Gonglei >> --- >> hw/virtio/virtio-bus.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/hw/virtio/virtio-bus.c b/hw/virtio/virtio-bus.c >> index eb77019..dfd2d8c 100644 >> --- a/hw/virtio/virtio-bus.c >> +++ b/hw/virtio/virtio-bus.c >> @@ -58,7 +58,7 @@ void virtio_bus_reset(VirtioBusState *bus) >> { >> VirtIODevice *vdev = virtio_bus_get_device(bus); >> >> - DPRINTF("%s: reset device.\n", qbus->name); >> + DPRINTF("%s: reset device.\n", BUS(bus)->name); > > In general the problem with existing DPRINTF() macros is that they use > #ifdef. This leads to bitrot, such as this instance. > Yes. > A better approach is: > > #define DEBUG_FOO 0 > #define DPRINTF(...) \ > do { \ > if (DEBUG_FOO) { \ > fprintf(stderr, ...); \ > } \ > } while (0) > > Now the compiler always checks the DPRINTF() code. > > Trace events can be a good solution too. If you like stderr output, > build QEMU with ./configure --enable-trace-backend=stderr and all > trace_*() calls are turned into fprintf(stderr). > > The cool thing about trace events is that they are available in > production too. > Hum, trace events is great! :) Best regards, -Gonglei