Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752503AbZL3Jof (ORCPT ); Wed, 30 Dec 2009 04:44:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752207AbZL3Joe (ORCPT ); Wed, 30 Dec 2009 04:44:34 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:50413 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752156AbZL3Joe (ORCPT ); Wed, 30 Dec 2009 04:44:34 -0500 Date: Wed, 30 Dec 2009 10:44:17 +0100 From: Ingo Molnar To: Peter Zijlstra Cc: Xiao Guangrong , Frederic Weisbecker , Thomas Gleixner , Steven Rostedt , Paul Mackerras , LKML Subject: Re: [PATCH v3 1/5] perf_event: introduce 'inject' event and get HZ Message-ID: <20091230094417.GC18190@elte.hu> References: <4B27702F.1080507@cn.fujitsu.com> <20091215142325.GC5833@nowhere> <4B30C2D1.4030006@cn.fujitsu.com> <4B30C3A0.909@cn.fujitsu.com> <20091228075417.GB20039@elte.hu> <4B3991C1.6060303@cn.fujitsu.com> <1262164786.7135.166.camel@laptop> <20091230092830.GA18190@elte.hu> <1262165789.7135.170.camel@laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1262165789.7135.170.camel@laptop> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: 0.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=0.0 required=5.9 tests=none autolearn=no SpamAssassin version=3.2.5 _SUMMARY_ Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1475 Lines: 40 * Peter Zijlstra wrote: > On Wed, 2009-12-30 at 10:28 +0100, Ingo Molnar wrote: > > * Peter Zijlstra wrote: > > > > > On Tue, 2009-12-29 at 13:21 +0800, Xiao Guangrong wrote: > > > > 'inject' event is a very useful feature and it's suggested by Ingo > > > > [ See http://lkml.org/lkml/2009/12/28/31 ] > > > > > > I really dislike the name, event injection to me would be like a write() > > > interface where you provide the actual event data to be stuffed in the > > > output stream. > > > > > > This just seems like a very weird way of getting data out. A kind of like > > > sysconf() but done very strange. > > > > What kind of API would you suggest? > > sysconf() seems ideal for getting single, mostly constant variables out > of the kernel, we already have non POSIX (read Linux specific) names in > there. > > _SC_KERNEL_RELOCATION_OFFSET > _SC_KERNEL_HZ > > or somethings like that comes to mind. Nah. HZ might be static here but we'll have more dynamic parameters so the sysconf API is rather inflexible there. I was thinking of something that fits into existing perf API schemes, to keep it simple and self-sufficient, and to allow for extensions/etc. Ingo -- 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/