Re: [Xen-devel] [PATCH] tools/hotplug/Linux/init.d/: added other xen kernel modules on xencommons start

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 10.08.12 at 17:04, Olaf Hering <olaf@xxxxxxxxx> wrote:
> On Wed, Aug 08, Jan Beulich wrote:
> 
>> >>> On 07.08.12 at 19:22, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:
>> >> Jan Beulich writes ("Re: [Xen-devel] [PATCH] tools/hotplug/Linux/init.d/: 
>> >> - not exclusively try the pv-ops kernel's module names.
>> > 
>> > Do you mean that 4.2 should try loading some bigger set of module
>> > names ?  If so then do you have a list ? :-)
>> 
>> - xen-blkback's counterpart is blkbk
>> - xen-netback's counterpart is netbk
>> 
>> xen-evtchn/evtchn and xen-gntdev/gntdev are already taken
>> care of, albeit in a little strange a way (the two entries being
>> separated by an increasing amount of other ones, when it is
>> really pointless to load the second one if the first one's load
>> succeeded).
>> 
>> To not needlessly try everything, it might additionally be worth
>> a thought to
>> - first try loading via module alias rather than module name (if
>>   that succeeds for a carefully chosen module that got its alias
>>   added late - according to our patches, the devname: aliases
>>   got introduced in 2.6.35, and the xen-backend: ones in 3.1 -,
>>   only try loading via module alias for all subsequent ones)
>> - second try loading a (or all) pvops named module(s) (if that/
>>   any of them succeed(s), there's no need to try _any_ non-
>>   pvops names subsequently, i.e. including ones that don't even
>>   exist in the legacy trees)
>> - last try loading the traditional/forward-port named ones
> 
> I think it can be done like this because I'm sure that the xenlinux
> based dom0 kernels have the drivers compiled as modules. So if evtchn.ko
> exists its xenlinux based, otherwise its pvops. I havent runtime tested
> that patch yet.

That's the case for our kernels, but doesn't have to be for any
derived ones (and there are still a few people cloning our patches).

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel