lkml.org 
[lkml]   [2002]   [Apr]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectprivate fops plug-in point
[kernel-bloat_argument_awareness_on]

Hello

An idea: I presume, I am not the first and not the only one, who wants to
add some arch / implementation features to some driver, being absolutely
sure, even a possibility of such a extension would never make it into the
kernel and rightly so - there's no need for it there. So, I believe, most
of people in this situation just create (and maintain) a local
kernel-patch. That's fine, but somewhat ugly. So, the idea is - wouldn't
it be useful to have some private fops plug-in points in "all"
(shields_maximum_power) device drivers. E.g., a driver open function would
check if the device' private_fops.open pointer is not NULL and then run
that function. A good point, perhaps, would be after all normal actions
are done. But, I am sure, some users would want to do some stuff BEFORE
standard actions... Asking for 2 plug-in points would be FAR TOO impudent
of me:-) Then it would just suffice to load a module to add some specific
actions to a specific driver / function... Maybe a
CONFIG_EXTENDIBLE_KERNEL option could be used to switch these plug-in
points on / off... That would avoid any overhead at all. Ok, some
performance-critical drivers / functions may chose not to include these
plug-in points at all. Just a raw idea. Any improvements most welcome.

Guennadi
---------------------------------
Guennadi Liakhovetski, Ph.D.
DSA Daten- und Systemtechnik GmbH
Pascalstr. 28
D-52076 Aachen
Germany

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:22    [W:0.085 / U:4.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site