On 02/14/2011 05:42 PM, Hank Janssen wrote:
MY APOLOGIES-I made a typo on James email address. I corrected it and resend.
Sorry for the double email.
Stephen/James/David,
Greetings to you all. As you might be aware, we submitted Hyper-V drivers to the kernel 2009.
We have been extending these drivers with additional functionality and our primary focus now
is doing the work needed to exit the staging area.
To give you some background, the following are Hyper-V specific Linux drivers:
hv_vmbus The vmbus driver that is the bridge between guest and the
host
hv_storvsc The SCSI device driver
hv_blkvsc The IDE driver
Given that the IDE subsystem (drivers/ide) is currently in
maintenance-only mode, and isn't used by modern distributions, you
likely want to make this a libata driver instead.
Though, from what's in current git, it's not clear to me what the HV IDE
(and SCSI) drivers are attempting to do. Is it really something that
looks like an IDE controller from the guest OS point of view? If not,
then having it as an IDE driver would be the wrong thing to do, it
should be more of a generic block driver. In that case, then, why are
there both SCSI and IDE drivers in the first place?
hv_netvsc The network driver
We think our drivers are pretty close to be reviewed by the subsystem maintainers.
We have been working with Greg on hv_vmbus, and several other driver issues as it relates to
exiting staging. And now we are looking for guidance for the other drivers.
1. Most important thing of course, did we contact the correct subsystem
maintainers?
i. IDE/Blkvsc David Miller
ii. SCSI/Storvsc James Bottomley
iii. Network/Netvsc Stephen Hemminger
2. What is the process to submit the code for review?
3. Which mailing list(s) do we need to use for the code reviews
4. I assume normal patch format is required?
5. What additional information is needed
6. Once they leave staging where do they need to go? Because they all
pretty much come as a package we were thinking drivers/hyperv might
be a good place.
There are still a few outstanding items we are currently working on. But they should be
wrapped up shortly. (There are a few remaining FIXME comments in the code we are
cleaning up as I write this). But if possible we would like to get your feedback even
as we are addressing the issues we currently know about.
Thanks
Hank.
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
