This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] RE: hv block drivers

To: Arnd Bergmann <arnd@xxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] RE: hv block drivers
From: Hank Janssen <hjanssen@xxxxxxxxxxxxx>
Date: Mon, 30 Aug 2010 17:31:10 +0000
Accept-language: en-US
Cc: "'virtualization@xxxxxxxxxxxxxx'" <virtualization@xxxxxxxxxxxxxx>, "Xen-devel@xxxxxxxxxxxxxxxxxxx" <Xen-devel@xxxxxxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Tue, 31 Aug 2010 12:34:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <201008301908.51521.arnd@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <201008301643.42253.arnd@xxxxxxxx> <4C7BD9A6.1090108@xxxxxxxx> <201008301908.51521.arnd@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AQHLSFHcnkjYB5qn30uR65rFUVBeSJL6onMAgAAOS4D//47G0A==
Thread-topic: hv block drivers
>On Monday 30 August 2010 Arnd Bergmann wrote: 
>>On Monday 30 August 2010, Jeremy Fitzhardinge wrote:
>> Have you investigated making virtio a scsi device?
>I doubt that there is much value in changing it now, and it's not something 
>I'd be interested in working on.
>For the HyperV drivers, it probably makes sense because half of it is trying 
>to look 
>like SCSI anyway, while the other half is trying to look like ATA. For the ATA 
>the obvious choice would be to make it a libata backend, though my impression 
>from a brief look at the driver was that it's better to copy some of the 
>libata code 
>and integrate it into the hv SCSI driver.


Thanks for following up! I was cleaning up some other part of the drivers (not 
related to IDE/SCSI) 
And on my todo list is to clean up the IDE/SCSI drivers. I will go through the 
libata code and see
If there is anything in there that I can use to make these drivers somewhat 

I am not sure if I can combine them into one yet, Hyper-V treats both drivers 
differently. And there
Are some rumored changes to Hyper-V that would make these changes maybe even a 
bit more difficult.

I will use this mailing list to bounce ideas off of. 

I still need to clean up your other suggestion as well, the static declarations 

For a more general question, When/if we make it out of staging, where should 
these drivers live?

        drivers/hyper-v or drivers/scsi and drivers/ide.

Is there a standard that is being followed?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>