> > > void error_report(const char *fmt, ...)
> > > {
> > > va_list ap;
> > > +char timestr[TIMESTAMP_LEN];
> > > +
> > > +if (enable_timestamp_msg) {
> > > +qemu_get_timestamp_str(×tr);
> > > +error_printf("%s ", timestr);
> > > +}
> > >
> > > error_print_lo
> >>
> >> I wonder if TIME_H is maybe a bit too nondescript and could conflict
> >> with other guards.
OK.
I will use QEMU_TIME_H.
Apologies for my curt reply.
Seiji
On 06/28/13 20:54, Seiji Aguchi wrote:
>
>>> diff --git a/include/qemu/time.h b/include/qemu/time.h
>>> new file mode 100644
>>> index 000..f70739b
>>> --- /dev/null
>>> +++ b/include/qemu/time.h
>>> @@ -0,0 +1,11 @@
>>> +#ifndef TIME_H
>>> +#define TIME_H
>>
>> I wonder if TIME_H is maybe a b
> > diff --git a/include/qemu/time.h b/include/qemu/time.h
> > new file mode 100644
> > index 000..f70739b
> > --- /dev/null
> > +++ b/include/qemu/time.h
> > @@ -0,0 +1,11 @@
> > +#ifndef TIME_H
> > +#define TIME_H
>
> I wonder if TIME_H is maybe a bit too nondescript and could conflict
> wi
On 06/27/2013 04:21 AM, Laszlo Ersek wrote:
> comments below
>
> On 06/27/13 04:08, Seiji Aguchi wrote:
>> [Issue]
>> When we offer a customer support service and a problem happens
>> in a customer's system, we try to understand the problem by
>> comparing what the customer reports with message lo
comments below
On 06/27/13 04:08, Seiji Aguchi wrote:
> [Issue]
> When we offer a customer support service and a problem happens
> in a customer's system, we try to understand the problem by
> comparing what the customer reports with message logs of the
> customer's system.
>
> In this case, we o
[Issue]
When we offer a customer support service and a problem happens
in a customer's system, we try to understand the problem by
comparing what the customer reports with message logs of the
customer's system.
In this case, we often need to know when the problem happens.
But, currently, there is
