On Mon, May 10, 2010 at 05:05:02PM +0000, Hank Janssen wrote: > > >Sent: Saturday, May 08, 2010 7:27 AM - Hank Janssen > >>On Sat, May 08, 2010 at 01:52:01PM +0000, Hank Janssen wrote:> > >> > >> I am not sure if this is the right approach. hv_netvsc takes a dependency on hv_vmbus. > >> hv_vmbus does have the same DMI detection logic in it. But unless hv_vmbus has loaded > >> up competely, hv_netvsc will fail on loadup. And I do not think we can guarantee that > >> hv_vmbus has loaded yet. > > > >Yes you can, the dependancies in the module will take care of it. Try > >it, if you try to load the hv_netvsc module before hv_vmbus, modprobe > >will load hv_vmbus first. > > In my testing I have seen issues with timing. It takes a little while for VMBus to start > getting the initialization taken care of with Hyper-V. And I have seen netvsc error with > unresolved symbols because vmbus had not completed the initialization yet. Odd, that shouldn't happen, unless you are loading modules in parallel. If we switch to a proper discovery type bus, this should not be an issue. thanks, greg k-h _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
