netdev - RE: Process for subsystem maintainers to get Hyper-V code out of staging.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 16 Feb 2011 17:43:34 +0000
From:	Hank Janssen <hjanssen@...rosoft.com>
To:	Robert Hancock <hancockrwd@...il.com>
CC:	"shemminger@...ux-foundation.org" <shemminger@...ux-foundation.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"davem@...emloft.net" <davem@...emloft.net>,
	ide <linux-ide@...r.kernel.org>,
	KY Srinivasan <kys@...rosoft.com>,
	Hashir Abdi <habdi@...rosoft.com>,
	Mike Sterling <Mike.Sterling@...rosoft.com>,
	Haiyang Zhang <haiyangz@...rosoft.com>,
	"gregkh@...e.de\" \"" <gregkh@...e.de>
Subject: RE: Process for subsystem maintainers to get Hyper-V code out of
 staging. - CORRECTED RECIPIENTS


> From: Robert Hancock [mailto:hancockrwd@...il.com]
> Sent: Monday, February 14, 2011 4:46 PM
> 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?
> 

Robert,

Thank you very much for your responses, today Hyper-V host only supports 
IDE and SCSI, and the code was initially written against 2.6.9 kernel.

Hyper-V still treats them a separate interface and is designed to emulate
A pretty old BIOS.

What my approach will be is to dig into libsata (something I have not
Much knowledge of) and see if we can use it and find a way to more sanely
Merge the behavior of Hyper-V's IDE and SCSI.

Hank.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html