From: Eric Blake <eblake@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>,
"dle-develop@lists.sourceforge.net"
<dle-develop@lists.sourceforge.net>,
Seiji Aguchi <seiji.aguchi@hds.com>,
Satoru Moriya <satoru.moriya@hds.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC][PATCH]Add timestamp to error message
Date: Fri, 01 Feb 2013 14:35:25 -0700 [thread overview]
Message-ID: <510C351D.3040807@redhat.com> (raw)
In-Reply-To: <510C0935.2020902@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
On 02/01/2013 11:28 AM, Laszlo Ersek wrote:
> Hello Seiji-san,
>
> On 02/01/13 15:53, Seiji Aguchi wrote:
>
>> A logic calculating a time is copied from libvirt, src/util/virtime.c.
>
>> +static void error_print_timestamp(void)
>
> Are gmtime() + strftime() unsuitable for some reason?
They are not async-signal safe, so they are not usable in between a
fork() and exec*(). Libvirt avoids them because it DOES log information
including timestamps in between fork/exec (and prior to writing
libvirt's virtime.c, we DID hit cases where libvirt would deadlock a
child process due to the non-safe use of a more naive timestamp
generator), but I don't know if qemu suffers from the same restriction
of when it has anything worth logging.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-02-01 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 14:53 [Qemu-devel] [RFC][PATCH]Add timestamp to error message Seiji Aguchi
2013-02-01 18:28 ` Laszlo Ersek
2013-02-01 20:25 ` Seiji Aguchi
2013-02-01 21:35 ` Eric Blake [this message]
2013-02-01 22:41 ` Seiji Aguchi
2013-02-02 7:23 ` Markus Armbruster
2013-02-02 7:31 ` Markus Armbruster
2013-04-04 14:54 ` Laszlo Ersek
2013-04-04 15:20 ` Paolo Bonzini
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=510C351D.3040807@redhat.com \
--to=eblake@redhat.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=satoru.moriya@hds.com \
--cc=seiji.aguchi@hds.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.