All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Francis <alistair.francis@xilinx.com>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: Alistair Francis <alistair.francis@xilinx.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [RFC v1 3/3] char-socket: Report TCP socket waiting as a warning
Date: Wed, 28 Jun 2017 09:18:07 -0700	[thread overview]
Message-ID: <CAKmqyKPw0F=SgBhd_a-rpQ566RSivMHw3Xiyb0GXY5EY3yy4jg@mail.gmail.com> (raw)
In-Reply-To: <20170628061540.GL4859@toto>

On Tue, Jun 27, 2017 at 11:15 PM, Edgar E. Iglesias
<edgar.iglesias@gmail.com> wrote:
> On Tue, Jun 27, 2017 at 05:17:58PM -0700, Alistair Francis wrote:
>> On Tue, Jun 27, 2017 at 2:10 PM, Edgar E. Iglesias
>> <edgar.iglesias@gmail.com> wrote:
>> > On Tue, Jun 27, 2017 at 01:45:48PM -0700, Alistair Francis wrote:
>> >> When QEMU is waiting for a TCP socket connection it reports that message as
>> >> an error. This isn't an error it is a warnign so let's change the report to
>> >> use warning_report() instead.
>> >
>> > Hi Alistair,
>> >
>> > Isn't this more like an informational message rather than a warning?
>> >
>> > A warning would indicate to me that something unexpected and perhaps wrong happened.
>> > In this case, there's nothing wrong going on.
>> >
>> > We may need more classes, like 'info:' and/or maybe others...
>>
>> Hey Edgar,
>>
>> That is a good point. I can add a info_report() as well then that
>> copies the warning_report() function but prefixes with 'info: '.
>
>
> Hi,
>
> Yes, or another way is to pass the class of message as an argument,
> e.g like qemu_log_mask does it.

Ah! That is a good idea.

Something like this:
    report(ERROR, "message, ...)
    report(WARN, "message, ...)
    report(INFO, "message, ...)

which gets converted to adding prefixes to the message.

Thanks,
Alistair

>
> Best regards,
> Edgar
>
>
>
>
>>
>> Thanks,
>> Alistair
>>
>> >
>> > Cheers,
>> > Edgar
>> >
>> >
>> >
>> >>
>> >> Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
>> >> ---
>> >>
>> >>  chardev/char-socket.c | 2 +-
>> >>  1 file changed, 1 insertion(+), 1 deletion(-)
>> >>
>> >> diff --git a/chardev/char-socket.c b/chardev/char-socket.c
>> >> index ccc499cfa1..5a56628e74 100644
>> >> --- a/chardev/char-socket.c
>> >> +++ b/chardev/char-socket.c
>> >> @@ -765,7 +765,7 @@ static int tcp_chr_wait_connected(Chardev *chr, Error **errp)
>> >>       * in TLS and telnet cases, only wait for an accepted socket */
>> >>      while (!s->ioc) {
>> >>          if (s->is_listen) {
>> >> -            error_report("QEMU waiting for connection on: %s",
>> >> +            warning_report("QEMU waiting for connection on: %s",
>> >>                           chr->filename);
>> >>              qio_channel_set_blocking(QIO_CHANNEL(s->listen_ioc), true, NULL);
>> >>              tcp_chr_accept(QIO_CHANNEL(s->listen_ioc), G_IO_IN, chr);
>> >> --
>> >> 2.11.0
>> >>
>> >>
>

  reply	other threads:[~2017-06-28 16:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27 20:45 [Qemu-devel] [RFC v1 0/3] Implement a warning_report function Alistair Francis
2017-06-27 20:45 ` [Qemu-devel] [RFC v1 1/3] util/qemu-error: Rename error_print_loc() to be more generic Alistair Francis
2017-06-28  4:32   ` Philippe Mathieu-Daudé
2017-06-27 20:45 ` [Qemu-devel] [RFC v1 2/3] util/qemu-error: Add a warning_report() function Alistair Francis
2017-06-27 22:21   ` Thomas Huth
2017-06-28  0:16     ` Alistair Francis
2017-06-28  9:04   ` Daniel P. Berrange
2017-06-28 16:16     ` Alistair Francis
2017-06-28 16:19       ` Daniel P. Berrange
2017-06-29  7:38         ` Markus Armbruster
2017-06-27 20:45 ` [Qemu-devel] [RFC v1 3/3] char-socket: Report TCP socket waiting as a warning Alistair Francis
2017-06-27 21:10   ` Edgar E. Iglesias
2017-06-28  0:17     ` Alistair Francis
2017-06-28  6:15       ` Edgar E. Iglesias
2017-06-28 16:18         ` Alistair Francis [this message]
2017-06-28  9:07 ` [Qemu-devel] [RFC v1 0/3] Implement a warning_report function Daniel P. Berrange
2017-06-28 15:49   ` Alistair Francis

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='CAKmqyKPw0F=SgBhd_a-rpQ566RSivMHw3Xiyb0GXY5EY3yy4jg@mail.gmail.com' \
    --to=alistair.francis@xilinx.com \
    --cc=armbru@redhat.com \
    --cc=edgar.iglesias@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.