From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Oleg Nesterov" <oleg@tv-sign.ru>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Bart Van Assche" <bart.vanassche@gmail.com>,
"Roland McGrath" <roland@redhat.com>
Subject: Re: [patch] make siginfo_t si_utime + si_sstime report times in USER_HZ, not HZ
Date: Thu, 26 Jun 2008 17:09:48 +0200 [thread overview]
Message-ID: <cfd18e0f0806260809n4370c6eqc07c05ff93029658@mail.gmail.com> (raw)
In-Reply-To: <20080625153806.GA499@tv-sign.ru>
On Wed, Jun 25, 2008 at 5:38 PM, Oleg Nesterov <oleg@tv-sign.ru> wrote:
> On 06/25, Michael Kerrisk wrote:
>>
>> --- /home/mtk/ARCHIVE/KERNEL/linux-2.6.26-rc7/kernel/signal.c.orig 2008-06-24
>> 16:20:39.000000000 +0200
>> +++ /home/mtk/ARCHIVE/KERNEL/linux-2.6.26-rc7/kernel/signal.c 2008-06-24
>> 16:22:17.000000000 +0200
>> @@ -1379,10 +1379,9 @@
>>
>> info.si_uid = tsk->uid;
>>
>> - /* FIXME: find out whether or not this is supposed to be c*time. */
>> - info.si_utime = cputime_to_jiffies(cputime_add(tsk->utime,
>> + info.si_utime = cputime_to_clock_t(cputime_add(tsk->utime,
>> tsk->signal->utime));
>> - info.si_stime = cputime_to_jiffies(cputime_add(tsk->stime,
>> + info.si_stime = cputime_to_clock_t(cputime_add(tsk->stime,
>> tsk->signal->stime));
>>
>> info.si_status = tsk->exit_code & 0x7f;
>> @@ -1450,9 +1449,8 @@
>>
>> info.si_uid = tsk->uid;
>>
>> - /* FIXME: find out whether or not this is supposed to be c*time. */
>> - info.si_utime = cputime_to_jiffies(tsk->utime);
>> - info.si_stime = cputime_to_jiffies(tsk->stime);
>> + info.si_utime = cputime_to_clock_t(tsk->utime);
>> + info.si_stime = cputime_to_clock_t(tsk->stime);
>>
>> info.si_code = why;
>> switch (why) {
>
> This looks like the obviously good fix to me.
Tested now, and it does what I expect.
> The patch also deletes the comment about signal_struct->cXtime,
> this also looks right: why should we use cutime/cstime ?
Hmmm -- maybe I was wrong to delete that comment. I think the point
of the comment was: should the time returned vie these fields of the
signinfo structure also include the times for (grand)children of the
process that had terminated and been wait()ed for. My first take on
that was "no". But now I'm not 100% sure. A quick test on Solaris 8
suggests that these fields *do* include the times of waited for
children. (None of this is specified in POSIX.1, which doesn't
specify si_utime and si_stime.) I've not yet tested FreeBSD (not sure
if it supports these fields or not).
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
next prev parent reply other threads:[~2008-06-26 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 14:49 Michael Kerrisk
2008-06-25 15:38 ` Oleg Nesterov
2008-06-25 20:26 ` Roland McGrath
2008-06-26 15:09 ` Michael Kerrisk [this message]
2008-06-27 8:06 ` Michael Kerrisk
2008-06-27 16:33 ` Oleg Nesterov
2008-06-27 20:27 ` Roland McGrath
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=cfd18e0f0806260809n4370c6eqc07c05ff93029658@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=bart.vanassche@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®