From: Ian Campbell Subject: Re: [PATCH] xen: rename gntdev and evtdev modules to be less generic Date: Fri, 11 Dec 2009 08:56:32 +0000 Message-ID: <1260521792.2367.115.camel@localhost.localdomain> References: <1260097645-13477-1-git-send-email-ian.campbell@citrix.com> <4B2163CC.7040005@goop.org> <1260485404.2367.4.camel@localhost.localdomain> <4B218360.4060802@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4B218360.4060802@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Thu, 2009-12-10 at 23:25 +0000, Jeremy Fitzhardinge wrote: > On 12/10/09 14:50, Ian Campbell wrote: > > It never occurred to me that autoloading would work at all for this > > driver, I always just load the module explicitly by listing > > in /etc/modules. What triggers (or is supposed to trigger) autoloading? > > > > Magic earwigs? How to misc drivers get autoloaded in general? In the absence of an explicit request_module or module alias which matches a device on a bus somewhere I don't think anything much has been autoloaded since udev came along since the only other way was the old "open a device node with no driver" method and udev effectively removed those device nodes. A module alias won't work since there is no device on a bus which could match this driver and I can't find a request_module for evtchn anywhere. If we think this driver should always get loaded when Xen is running then I think a late_initcall which calls request_module might be the way to go, although I'm not sure late_initcall is late enough sine it needs to be when the proper root is mounted. Ian.