various vmbus review comments
greg at kroah.com
Wed May 4 09:32:28 PDT 2011
On Wed, May 04, 2011 at 04:20:11PM +0000, KY Srinivasan wrote:
> > -----Original Message-----
> > From: Greg KH [mailto:greg at kroah.com]
> > Sent: Tuesday, May 03, 2011 4:47 PM
> > To: KY Srinivasan
> > Cc: gregkh at suse.de; linux-kernel at vger.kernel.org;
> > devel at linuxdriverproject.org; virtualization at lists.osdl.org
> > Subject: various vmbus review comments
> > I just took a quick look at the vmbus code, and have the following
> > comments:
> > - why is count_hv_channel() even a function?
> I will fix this.
> > - your .h files need to be consolidated and renamed. You will
> > need a single hyperv.h file for include/linux/ that will
> > contain some of what the vmbus*.h files have in it, but not
> > all. Please merge things together to have:
> > - include/linux/hyperv.h
> > What is needed to build the drivers that attach to
> > the bus
> > - drivers/staging/hv/hyperv.h
> > The local .h file will have the vmbus*.h remaining
> > stuff that is only needed by the hv_vmbus.ko module
> > to be build.
> I have currently consolidated all the header files as follows:
> 1) hyperv.h - this will have all the vmbus related definitions
> needed to build drivers that attach to the bus (as you have suggested).
> 2) hyperv_storage.h - this has all the definitions needed to build storage
> drivers for Hyper-V. Storage drivers will include hyperv.h and
> 3) hyperv_net.h - this has all the definitions needed to build the network
> driver for Hyper-V. The netvsc driver will include hyperv.h and hyperv_net.h.
> 4) hyperv_utils.h - this has all the definitions needed to build the util driver.
> The util driver would include hyperv.h and hyperv_utils.h.
No for all 3 of these. Why would a simple driver need a .h file at all?
Just include the structures within the .c file, making it nice and
self-contained. There's no need to clutter things up, and individual
driver .h files should _never_ be in include/linux.
> All these four header files could potentially be under include/linux.
> I have also created a private header file that has the definitions to
> build the vmbus driver - hyperv_vmbus.h.
Sure, you can call it that, but as it will be local to the hyperv bus
directory, the name isn't all that important.
> Let me know if this is what you had in mind.
> > - the instances of hv_driver structures need to be static and
> > not programatically defined, like all other USB and PCI
> > drivers are handled.
> > - module reference counting. Are you sure you got it all right
> > for the individual modules that attach to the bus? I don't
> > see any reference counting happening, is that correct?
> For this round, I want to concentrate on just the vmbus driver. So,
> module reference counting is I don't think an issue for the vmbus driver
> given that the driver is not unlodable. Once I am done with the vmbus driver
> I will address the module reference counting issues for other drivers.
No, I am referring to the module reference counting of the bus drivers
that register with the vmbus core. You aren't doing that at all, and
you probably need to make sure that this isn't needed. That is
concentrating on the vmbus driver.
> I will also address your comment on static initialization hv_driver instances
> as part of other driver cleanup.
No, please do this now as it will show how to properly interact with the
vmbus core code in the correct manner. Hopefully that will be correct,
but I have a feeling that it will show you some places in the API that
need to be changed...
More information about the devel