Re: RFC: new utility, kmodpatch

From: Gary Jennejohn <gary.jennejohn_at_freenet.de>
Date: Sat, 3 Jan 2009 12:44:24 +0100
On Fri, 2 Jan 2009 23:17:19 +0100
Luigi Rizzo <rizzo_at_iet.unipi.it> wrote:

> On Thu, Jan 01, 2009 at 07:19:12PM -0500, Ben Kaduk wrote:
> > On Thu, Jan 1, 2009 at 2:17 PM, Oliver Pinter <oliver.pntr_at_gmail.com> wrote:
> > > Hi!
> > >
> > > Do You think for this project: http://www.ksplice.com/ ?
> > >
> > > On 1/1/09, Luigi Rizzo <rizzo_at_iet.unipi.it> wrote:
> > >> I mentioned this utility a couple of months ago, and it's now working
> > >> so i would like to receive feedback on whether this is good to have
> > >> as part of the system, or just keep it as a port (which is what
> > >> i plan to do by default).
> > >>
> > >> In a nutshell, the kmodpatch utility can print or alter the content
> > >> of device/quirk tables in kernel modules (I think Linux has some
> > >> similar tool, though i don't remember the name -- or perhaps it is
> > >> a feature of insmod ?).
> > >>
> > 
> > 
> > Ksplice is not yet in the linux kernel tree, so it's probably not
> > what Luigi was referring to.  However, it is a pretty impressive
> 
> correct, i think there is some feature (in insmod or whatever the
> utility to load a module is) to configure the module so it uses
> certain variables (perhaps including recognising a given USB vendor-id pair?)
> 

These are called moduler parameters in Linux parlance and must be built
into the drivers themselves.  insmod merely provides a mehcanism for
passing them to the drivers.

---
Gary Jennejohn
Received on Sat Jan 03 2009 - 10:44:29 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:39 UTC