From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756286Ab3BUSW2 (ORCPT ); Thu, 21 Feb 2013 13:22:28 -0500 Received: from mailhub.sw.ru ([195.214.232.25]:2113 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754238Ab3BUSWZ (ORCPT ); Thu, 21 Feb 2013 13:22:25 -0500 Message-ID: <512665BA.9040802@parallels.com> Date: Thu, 21 Feb 2013 22:21:46 +0400 From: Pavel Emelyanov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0 MIME-Version: 1.0 To: Thomas Gleixner , Ingo Molnar , Peter Zijlstra , Michael Kerrisk , Matthew Helsley , linux-api@vger.kernel.org, Linux Kernel Mailing List Subject: [PATCH 0/3] posix timers: Extend kernel API to report more info about timers (v2) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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