From: Paolo Bonzini <pbonzini@redhat.com>
To: minyard@acm.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/3] Clean up non-blocking error reporting
Date: Wed, 08 Oct 2014 14:56:20 +0200 [thread overview]
Message-ID: <54353474.2070503@redhat.com> (raw)
In-Reply-To: <1412770316-5241-1-git-send-email-minyard@acm.org>
Il 08/10/2014 14:11, minyard@acm.org ha scritto:
> This version makes the error message reporting more sane and
> adds a error_vreport() to make that easier.
>
> It also cleans up the bool handling.
>
> This depends on the previos non-blocking socket changes, which
> should hopefully be in qemu soon.
Looks good, but let's unify the error message like this:
+static void check_report_connect_error(CharDriverState *chr,
+ Error *err)
+{
+ TCPCharDriver *s = chr->opaque;
+
+ if (!s->connect_err_reported) {
+ error_report("Unable to connect character device %s: %s",
+ chr->label, error_get_pretty(err));
+ s->connect_err_reported = true;
+ }
+ qemu_chr_socket_restart_timer(chr);
+}
+
This is an error on connecting the character device to the backend. The
error on the socket is already detailed after the colon, thanks to your
patch 2.
I'll send a pull request today or tomorrow.
Thanks,
Paolo
prev parent reply other threads:[~2014-10-08 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 12:11 [Qemu-devel] [PATCH v2 0/3] Clean up non-blocking error reporting minyard
2014-10-08 12:11 ` [Qemu-devel] [PATCH 1/3] qemu-error: Add error_vreport() minyard
2014-10-08 14:38 ` Eric Blake
2014-10-08 12:11 ` [Qemu-devel] [PATCH 2/3] qemu-char: Fix reconnect socket error reporting minyard
2014-10-08 12:11 ` [Qemu-devel] [PATCH 3/3] qemu-sockets: Add error to non-blocking connect handler minyard
2014-10-09 10:07 ` Paolo Bonzini
2014-10-09 17:48 ` Corey Minyard
2014-10-08 12:56 ` Paolo Bonzini [this message]
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=54353474.2070503@redhat.com \
--to=pbonzini@redhat.com \
--cc=minyard@acm.org \
--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).