Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751354AbVLFFKW (ORCPT ); Tue, 6 Dec 2005 00:10:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751367AbVLFFKV (ORCPT ); Tue, 6 Dec 2005 00:10:21 -0500 Received: from e3.ny.us.ibm.com ([32.97.182.143]:15534 "EHLO e3.ny.us.ibm.com") by vger.kernel.org with ESMTP id S1751354AbVLFFKV (ORCPT ); Tue, 6 Dec 2005 00:10:21 -0500 Subject: [RFC][PATCH 000/002] Add timestamp to process event connector message From: Matt Helsley To: LKML Cc: Andrew Morton , Jean-Pierre Dion , Guillaume Thouvenin , Badari Pulavarty , Ram Pai , CKRM-Tech , Erich Focht , elsa-devel , Jay Lan , Erik Jacobson , Jack Steiner Content-Type: text/plain Date: Mon, 05 Dec 2005 21:00:25 -0800 Message-Id: <1133845225.25202.1373.camel@stark> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1095 Lines: 28 This series of patches adds a timestamp field to the events sent via the process event connector. The timestamp allows listeners to accurately account the duration(s) between a process' events and offers strong means with which to determine the order of events while also avoiding the addition of per-task data. Series: getnstimestamp.patch proc-events-timestamp.patch The first patch adds a new generic function, getnstimestamp(), which gets an SMP-safe high-resolution monotonic timestamp. The second patch adds a timestamp field to the events sent via the process event connector and fills the field using the new timestamp function. It alters the size and layout of the event structure and hence would break compatibility if not incorporated with the first release of process events connector in a mainline kernel. Cheers, -Matt Helsley - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/