[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Propose "xen_init()" call first thing in Xen drivers


  • To: "Hollis Blanchard" <hollisb@xxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Thu, 22 Sep 2005 13:53:39 -0700
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Matt Chapman <matthewc@xxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 22 Sep 2005 20:51:29 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcW/sAxS2saO2GetR7SmmpAVy1ytBgAB0wxA
  • Thread-topic: [Xen-devel] Propose "xen_init()" call first thing in Xen drivers

> Oh, well, there's the problem: module_init(evtchn_init). That means 
> evtchn_init will be called in arbitrary (link) order, 
> intermingled with the 
> actual drivers (which are also using module_init).
> 
> evtchn_init() can be built in and made a subsys_initcall, or 
> there needs to be 
> an explicit module dependency: e.g. request_module("evtchn").
> 
> http://xenbits.xensource.com/ext/xenlinux-ia64-2.6.12.hg?cmd=f
> ile;filenode=769f15e75bbd990900b352a3f9d50562d9e399df;file=dri
> vers/xen/core/xenia64_init.c
> 
> As for xen_start_info in the above URL, why don't you make 
> sure arch code sets 
> that up before drivers are loaded? You can turn your existing 
> xen_init() into 
> an arch_initcall.

Thanks much for the ideas.  We will have a look at this
again (hopefully soon) but are currently broiling bigger
fish, so the current "workaround" is sufficient for now.

Dan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.