Bug#652014: Linux 3.2: Enable Hyper-V kernel modules

[Mathieu Simon <mathieu.sim@gmail.com>]

Hi (forwarding to the bugtracker this time)

> There is no need to wait for drivers to leave staging, in general.
Great. In this case please consider enabling the following modules too:

Have both left staging-next, not made into 3.2:
Microsoft Hyper-V virtual network driver
Microsoft Hyper-V virtual mouse driver

Still in staging also in staging-next:
Microsoft Hyper-V virtual storage driver

> I think there was some problem with them earlier that meant we didn't
> enable them (possibly limitations on building as modules?).  Also, MS
> abandoned them for a while.  But it seems that they are being properly
> maintained now.
True, there were quite unstable at least until 2.6.38. I wouldn't
favour to enable them on earlier kernels (especially the storave driver)
(This is based on my experience driver-related crashes using
self-built mainline kernel)

>> Currently they are not unloadable, if that is a problem, I know there is
>> a patch floating in the upstream.
>
> Do you have a reference for that?  (Commit hash, message ID, URL...)
The patch seems not to be integrated yet anywhere, but the discussion mentions
the patch here

http://www.spinics.net/lists/linux-driver-devel/msg21785.html

Thanks for your positive answer.

- Mathieu