From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/4] virtio: Convert fprintf() to error_report()
Date: Mon, 15 Nov 2010 20:44:34 +0000 [thread overview]
Message-ID: <1289853878-15188-1-git-send-email-stefanha@linux.vnet.ibm.com> (raw)
The virtio hardware emulation code uses fprintf(stderr, ...) error messages.
Improve things slightly by moving to error_report() so error messages will be
printed to the monitor, if present.
We want to handle device error states properly instead of bailing out with
exit(1) but this series does not attempt to fix that yet.
Leave virtio-9p for now where there are many cases of fprintf(stderr, ...) and
development is still very active.
next reply other threads:[~2010-11-15 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 20:44 Stefan Hajnoczi [this message]
2010-11-15 20:44 ` [Qemu-devel] [PATCH 1/4] virtio-blk: Convert fprintf() to error_report() Stefan Hajnoczi
2010-11-15 20:44 ` [Qemu-devel] [PATCH 2/4] virtio: " Stefan Hajnoczi
2010-11-16 10:01 ` Markus Armbruster
2010-11-15 20:44 ` [Qemu-devel] [PATCH 3/4] virtio-net: " Stefan Hajnoczi
2010-11-15 20:44 ` [Qemu-devel] [PATCH 4/4] virtio-pci: " Stefan Hajnoczi
2010-11-21 15:20 ` [Qemu-devel] [PATCH 0/4] virtio: " Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1289853878-15188-1-git-send-email-stefanha@linux.vnet.ibm.com \
--to=stefanha@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).