From: Pavel Emelyanov <xemul@parallels.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Pavel Tikhomirov <snorcht@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Matthew Helsley <matt.helsley@gmail.com>,
linux-api@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] posix-timers: Show clock ID in proc file
Date: Fri, 17 May 2013 20:12:55 +0400 [thread overview]
Message-ID: <51965707.5010305@parallels.com> (raw)
In-Reply-To: <20130517155916.GA24976@kroah.com>
On 05/17/2013 07:59 PM, Greg KH wrote:
> On Fri, May 17, 2013 at 02:12:03AM +0400, Pavel Tikhomirov wrote:
>> Expand information about posix-timers in /proc/<pid>/timers by adding
>> info about clock, with which the timer was created. I.e. in the forth
>> line of timer info after "notify:" line go "ClockID: <clock_id>".
>>
>> Signed-off-by: Pavel Tikhomirov <snorcht@gmail.com>
>> ---
>> fs/proc/base.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/fs/proc/base.c b/fs/proc/base.c
>> index 2dad4a9..8a38eef 100644
>> --- a/fs/proc/base.c
>> +++ b/fs/proc/base.c
>> @@ -2079,6 +2079,7 @@ static int show_timer(struct seq_file *m, void *v)
>> nstr[notify & ~SIGEV_THREAD_ID],
>> (notify & SIGEV_THREAD_ID) ? "tid" : "pid",
>> pid_nr_ns(timer->it_pid, tp->ns));
>> + seq_printf(m, "ClockID: %d\n", timer->it_clock);
>
> What userspace tool just broke by adding a new field to this file?
Zero for two reasons:
1. this proc file appeared this merge window
2. this file format is
<name>: <value>
and should be parsed line-by-line by applications like e.g. /proc/pid/status
or /proc/pid/smaps. Both these files were extended with fields in the past with
no worries to tools, so should be this new one.
> thanks,
>
> greg k-h
> .
>
Thanks,
Pavel
next prev parent reply other threads:[~2013-05-17 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 22:12 [PATCH 0/1] posix timers: Expand exitsting info in proc file Pavel Tikhomirov
[not found] ` <1368742323-46949-1-git-send-email-snorcht-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-16 22:12 ` [PATCH 1/1] posix-timers: Show clock ID " Pavel Tikhomirov
[not found] ` <1368742323-46949-2-git-send-email-snorcht-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-17 15:59 ` Greg KH
2013-05-17 16:12 ` Pavel Emelyanov [this message]
[not found] ` <51965707.5010305-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-05-17 16:22 ` Greg KH
2013-05-17 16:10 ` Pavel Emelyanov
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=51965707.5010305@parallels.com \
--to=xemul@parallels.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.helsley@gmail.com \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=snorcht@gmail.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;
as well as URLs for NNTP newsgroup(s).