Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 23 Oct 2002 12:47:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 23 Oct 2002 12:47:15 -0400 Received: from d06lmsgate-4.uk.ibm.com ([195.212.29.4]:63934 "EHLO d06lmsgate-4.uk.ibm.COM") by vger.kernel.org with ESMTP id ; Wed, 23 Oct 2002 12:47:14 -0400 Subject: Re: 2.4 Ready list - Kernel Hooks To: Werner Almesberger Cc: Rob Landley , linux-kernel@vger.kernel.org, S Vamsikrishna X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Richard J Moore" Date: Wed, 23 Oct 2002 17:47:11 +0100 X-MIMETrack: Serialize by Router on D06ML023/06/M/IBM(Release 5.0.9a |January 7, 2002) at 23/10/2002 17:53:22 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1359 Lines: 37 > Is the idea that people would deploy hooks locally, i.e. while > profiling or debugging, or that some hooks would be put permanently > in the kernel ? Our principle reasons for using hooks is: 1) We simplify the integration of related facilities that would share a number of common hook points, e.g. kdb, dprobes, ltt etc 2) We don't bloat the kernel with these feature but still have the ability to turn them on dynamically when the need (or the pain) is sufficient for us to do something about it. 2a) we can reduce the overhead of the extra function when dormant to almost nil if it can be unhooked from the kernel. 3) We used them during development to extricate a function from the kernel into a loadable module. This avoided many reboots and kernel builds. >By the way, those hooks look like an excellent mechanism for >circumventing the GPL, so you might want to export them with >EXPORT_SYMBOL_GPL. We already do that. I don't envisage having an arbitrary set of hook points scattered throughout the kernel. It's only when, for example, dprobes needed certain hooks that we added them. Richard - 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/