From: Pavel Emelyanov <xemul@parallels.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
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: [PATCH 0/3] posix timers: Extend kernel API to report more info about timers (v2)
Date: Thu, 21 Feb 2013 22:21:46 +0400 [thread overview]
Message-ID: <512665BA.9040802@parallels.com> (raw)
Hi.
Here's another approach to address the problems with insufficient API
of posix timers.
Currently kernel doesn't provide any API for getting information about
what timers are currently created by process and in which state they
are. Initially the proposal was to add a couple of system calls that
would list timers owned by a task and provide info about sigevent
configuration of particular timer.
Matthew pointed out, that fixing the API in _that_ way should better be
left to POSIX people :) and we'd better go with new /proc files. So
here's how the /proc file can look like to provide info about timers
(patches 2 and 3).
And, yet again, I'd like to fix the way timer IDs are generated by
replacing global IDR with hashtable and making IDs generation
per-signal_struct (patch 1). A note: mentioned by Matthew important
patches about timers IDR are "don't feed negative ID into idr_xxx
engine". Since I remove the whole IDR stuff from timers, I do
conflict with them, but this is easy to fix :)
Thanks,
Pavel
next reply other threads:[~2013-02-21 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 18:21 Pavel Emelyanov [this message]
2013-02-21 18:22 ` [PATCH 1/3] posix timers: Allocate timer id per process (v2) Pavel Emelyanov
2013-03-08 12:50 ` Thomas Gleixner
2013-02-21 18:22 ` [PATCH 2/3] posix-timers: Introduce /proc/<pid>/timers file Pavel Emelyanov
2013-02-21 18:22 ` [PATCH 3/3] posix-timers: Show sigevent info in proc file Pavel Emelyanov
2013-03-08 8:40 ` [PATCH 0/3] posix timers: Extend kernel API to report more info about timers (v2) Pavel Emelyanov
2013-03-08 9:56 ` Thomas Gleixner
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=512665BA.9040802@parallels.com \
--to=xemul@parallels.com \
--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=peterz@infradead.org \
--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