All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Christophe Fergeau <cfergeau@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5] log: Make glib logging go through QEMU
Date: Thu, 24 Jan 2019 16:23:29 +0100	[thread overview]
Message-ID: <871s52dqq6.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20190124124428.GX30040@natto.ory.fergeau.eu> (Christophe Fergeau's message of "Thu, 24 Jan 2019 13:44:28 +0100")

Christophe Fergeau <cfergeau@redhat.com> writes:

> Hey,
>
> On Thu, Jan 24, 2019 at 10:38:37AM +0100, Markus Armbruster wrote:
>> Christophe Fergeau <cfergeau@redhat.com> writes:
>> 
>> > This commit adds a qemu_init_logging() helper which calls
>> > g_log_set_default_handler() so that glib logs (g_log, g_warning, ...)
>> > are handled similarly to other QEMU logs. This means they will get a
>> > timestamp if timestamps are enabled, and they will go through the
>> > monitor if one is configured.
>> > This commit also adds a call to qemu_init_logging() to the binaries
>> > installed by QEMU.
>> > glib debug messages are enabled through G_MESSAGES_DEBUG similarly to
>> > glib default log handler.
>> >
>> > At the moment, this change will mostly impact SPICE logging if your
>> > spice version is >= 0.14.1. With older spice versions, this is not going
>> > to work as expected, but will not have any ill effect, so this call is
>> > not conditional on the SPICE version.
>> >
>> > Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
>> > Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>> > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
>> 
>> Do you expect this to go through my tree?
>
> To be honest, I don't know through whose tree this should go.

The bulk of the patch is in qemu-error.c, which suggests my tree.

>> Hint: if you do, cc'ing me tends to help ;)
>> 
>> scripts/get_maintainer.pl can be your friend.
>
> I ran it, but it returned a few too many names given that it touches
> files in various subsystems, I was not sure I should cc: everyone.

You were right to doubt.

> Now that I look again, at least "(supporter:Error reporting)" would have
> made sense.
>
> Thanks for noticing this patch without the cc: :)

No problem :)

  reply	other threads:[~2019-01-24 15:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 17:04 [Qemu-devel] [PATCH v5] log: Make glib logging go through QEMU Christophe Fergeau
2019-01-22 14:13 ` Stefan Hajnoczi
2019-01-24  9:38 ` Markus Armbruster
2019-01-24 12:44   ` Christophe Fergeau
2019-01-24 15:23     ` Markus Armbruster [this message]
2019-01-24 16:10 ` Markus Armbruster
2019-01-24 18:32   ` Dr. David Alan Gilbert
2019-01-25  6:57     ` Markus Armbruster
2019-01-25 17:19   ` Christophe Fergeau

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=871s52dqq6.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=cfergeau@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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.