-Original Message-
From: Christoph Hellwig [mailto:h...@infradead.org]
Sent: Sunday, May 01, 2011 4:53 PM
To: KY Srinivasan
Cc: Greg KH; gre...@suse.de; linux-ker...@vger.kernel.org;
de...@linuxdriverproject.org; virtualizat...@lists.osdl.org
Subject: Re: [PATCH 00/25] Staging: hv
On Mon, May 02, 2011 at 07:48:38PM +, KY Srinivasan wrote:
By setting up appropriate modprobe rules, this can be addressed.
That assumes libata is a module, which it is not for many popular
distributions.
___
Virtualization mailing list
00/25] Staging: hv: Cleanup vmbus driver code
On Mon, May 02, 2011 at 07:48:38PM +, KY Srinivasan wrote:
By setting up appropriate modprobe rules, this can be addressed.
That assumes libata is a module, which it is not for many popular
distributions.
As long as you can prevent
On Mon, May 02, 2011 at 09:16:36PM +, KY Srinivasan wrote:
That assumes libata is a module, which it is not for many popular
distributions.
As long as you can prevent ata_piix from loading, it should be fine.
Again, this might very well be built in, e.g. take a look at:
-Original Message-
From: Christoph Hellwig [mailto:h...@infradead.org]
Sent: Monday, May 02, 2011 5:35 PM
To: KY Srinivasan
Cc: Greg KH; gre...@suse.de; linux-ker...@vger.kernel.org;
de...@linuxdriverproject.org; virtualizat...@lists.osdl.org
Subject: Re: [PATCH 00/25] Staging: hv
On Fri, Apr 29, 2011 at 04:32:35PM +, KY Srinivasan wrote:
On the host-side, as part of configuring a guest you can specify block
devices
as being under an IDE controller or under a
SCSI controller. Those are the only options you have. Devices configured under
the IDE controller cannot
On Fri, Apr 29, 2011 at 09:40:25AM -0700, Greg KH wrote:
Are you sure the libata core can't see this ide controller and connect
to it? That way you would use the scsi system if you do that and you
would need a much smaller ide driver, perhaps being able to merge it
with your scsi driver.
: [PATCH 00/25] Staging: hv: Cleanup vmbus driver code
On Fri, Apr 29, 2011 at 09:40:25AM -0700, Greg KH wrote:
Are you sure the libata core can't see this ide controller and connect
to it? That way you would use the scsi system if you do that and you
would need a much smaller ide driver
On Sun, May 01, 2011 at 11:39:21AM -0400, Christoph Hellwig wrote:
On Fri, Apr 29, 2011 at 04:32:35PM +, KY Srinivasan wrote:
On the host-side, as part of configuring a guest you can specify block
devices
as being under an IDE controller or under a
SCSI controller. Those are the
On Sun, May 01, 2011 at 03:46:23PM +, KY Srinivasan wrote:
What is the issue here? This is no different than what is done in other
Virtualization platforms. For instance, the Xen blkfront driver is no
different - if you specify the block device to be presented to the guest
as an ide
: [PATCH 00/25] Staging: hv: Cleanup vmbus driver code
On Sun, May 01, 2011 at 03:46:23PM +, KY Srinivasan wrote:
What is the issue here? This is no different than what is done in other
Virtualization platforms. For instance, the Xen blkfront driver is no
different - if you specify the block
-Original Message-
From: Greg KH [mailto:g...@kroah.com]
Sent: Sunday, May 01, 2011 11:48 AM
To: KY Srinivasan
Cc: Christoph Hellwig; gre...@suse.de; linux-ker...@vger.kernel.org;
de...@linuxdriverproject.org; virtualizat...@lists.osdl.org
Subject: Re: [PATCH 00/25] Staging: hv
On Sun, May 01, 2011 at 06:56:58PM +, KY Srinivasan wrote:
Yeah, it seems to me that no matter how the user specifies the disk
type for the guest configuration, we should use the same Linux driver,
with the same naming scheme for both ways.
As Christoph points out, it's just a
On Sun, May 01, 2011 at 06:08:37PM +, KY Srinivasan wrote:
Could you elaborate on the problems/issues when the block driver registers
for the
IDE majors. On the Qemu side, we have a mechanism to disable the emulation
when
PV drivers load. I don't think there is an equivalent mechanism
On Fri, Apr 29, 2011 at 02:26:13PM +, KY Srinivasan wrote:
Perhaps I did not properly formulate my question here. The review
process itself may be open-ended, and that is fine - we will fix all
legitimate
issues/concerns in our drivers whether they are in the staging area or not.
My
: [PATCH 00/25] Staging: hv: Cleanup vmbus driver code
On Wed, Apr 27, 2011 at 11:47:03AM +, KY Srinivasan wrote:
On the host side, Windows emulates the standard PC hardware
to permit hosting of fully virtualized operating systems.
To enhance disk I/O performance, we support a virtual
;
de...@linuxdriverproject.org; virtualizat...@lists.osdl.org
Subject: Re: [PATCH 00/25] Staging: hv: Cleanup vmbus driver code
On Wed, Apr 27, 2011 at 11:47:03AM +, KY Srinivasan wrote:
On the host side, Windows emulates the standard PC hardware
to permit hosting of fully virtualized
; linux-
ker...@vger.kernel.org;
de...@linuxdriverproject.org; virtualizat...@lists.osdl.org
Subject: Re: [PATCH 00/25] Staging: hv: Cleanup vmbus driver code
On Wed, Apr 27, 2011 at 11:47:03AM +, KY Srinivasan wrote:
On the host side, Windows emulates the standard PC hardware
On Tue, Apr 26, 2011 at 09:19:45AM -0700, K. Y. Srinivasan wrote:
This patch-set addresses some of the bus/driver model cleanup that
Greg sugested over the last couple of days. In this patch-set we
deal with the following issues:
1) Cleanup unnecessary state in struct hv_device and
-Original Message-
From: Greg KH [mailto:g...@kroah.com]
Sent: Tuesday, April 26, 2011 7:29 PM
To: KY Srinivasan
Cc: gre...@suse.de; linux-ker...@vger.kernel.org;
de...@linuxdriverproject.org; virtualizat...@lists.osdl.org
Subject: Re: [PATCH 00/25] Staging: hv: Cleanup vmbus
On Wed, Apr 27, 2011 at 01:54:02AM +, KY Srinivasan wrote:
I would prefer that we go through the review process. What is the process for
this review? Is there a time window for people to respond. I am hoping I will
be able
to address all the review comments well in advance of the next
] Staging: hv: Cleanup vmbus driver code
On Wed, Apr 27, 2011 at 01:54:02AM +, KY Srinivasan wrote:
I would prefer that we go through the review process. What is the process
for
this review? Is there a time window for people to respond. I am hoping I
will be
able
to address all
On Wed, Apr 27, 2011 at 11:47:03AM +, KY Srinivasan wrote:
On the host side, Windows emulates the standard PC hardware
to permit hosting of fully virtualized operating systems.
To enhance disk I/O performance, we support a virtual block driver.
This block driver currently handles disks
On Wed, Apr 27, 2011 at 01:54:02AM +, KY Srinivasan wrote:
After that, do you want another round of review of the code, or do
you have more things you want to send in (like the name[64] removal?)
I would prefer that we go through the review process. What is the process for
this
Do you have a repository containing the current state of your patche
somewhere? There's been so much cleanup that it's hard to review these
patches against the current mainline codebase.
___
Virtualization mailing list
-Original Message-
From: Christoph Hellwig [mailto:h...@infradead.org]
Sent: Tuesday, April 26, 2011 12:57 PM
To: KY Srinivasan
Cc: gre...@suse.de; linux-ker...@vger.kernel.org;
de...@linuxdriverproject.org; virtualizat...@lists.osdl.org
Subject: Re: [PATCH 00/25] Staging: hv
; virtualizat...@lists.osdl.org
Subject: Re: [PATCH 00/25] Staging: hv: Cleanup vmbus driver code
Do you have a repository containing the current state of your patche
somewhere? There's been so much cleanup that it's hard to review these
patches against the current mainline codebase
27 matches
Mail list logo
