This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [PATCH] xen: rename gntdev and evtdev modules to be less

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] xen: rename gntdev and evtdev modules to be less generic
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Fri, 11 Dec 2009 08:56:32 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 11 Dec 2009 00:56:54 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B218360.4060802@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Citrix Systems, Inc.
References: <1260097645-13477-1-git-send-email-ian.campbell@xxxxxxxxxx> <4B2163CC.7040005@xxxxxxxx> <1260485404.2367.4.camel@xxxxxxxxxxxxxxxxxxxxx> <4B218360.4060802@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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.


Xen-devel mailing list