linux-kernel - RE: [PATCH 6/6] drivers:pci:hv: New paravirtual PCI front-end for Hyper-V VMs

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <DM2PR0301MB12323CC0C1132A7F71C79DD3ABBB0@DM2PR0301MB1232.namprd03.prod.outlook.com>
Date:	Fri, 12 Jun 2015 15:11:14 +0000
From:	Jake Oshins <jakeo@...rosoft.com>
To:	Paul Bolle <pebolle@...cali.nl>
CC:	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
	KY Srinivasan <kys@...rosoft.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"olaf@...fle.de" <olaf@...fle.de>,
	"apw@...onical.com" <apw@...onical.com>,
	"vkuznets@...hat.com" <vkuznets@...hat.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
	Mike Ebersol <Michael.Ebersol@...rosoft.com>,
	Haiyang Zhang <haiyangz@...rosoft.com>
Subject: RE: [PATCH 6/6] drivers:pci:hv: New paravirtual PCI front-end for
 Hyper-V VMs

> -----Original Message-----
> From: Paul Bolle [mailto:pebolle@...cali.nl]
> Sent: Friday, June 12, 2015 1:44 AM
> To: Jake Oshins
> Cc: gregkh@...uxfoundation.org; KY Srinivasan; linux-
> kernel@...r.kernel.org; devel@...uxdriverproject.org; olaf@...fle.de;
> apw@...onical.com; vkuznets@...hat.com; linux-pci@...r.kernel.org;
> bhelgaas@...gle.com; Mike Ebersol; Haiyang Zhang
> Subject: Re: [PATCH 6/6] drivers:pci:hv: New paravirtual PCI front-end for
> Hyper-V VMs
> 
> Greg has already asked you to resend. So here follow a few remarks to
> take into account for that resend.
> 

Thank you.  I'll fix everything you've mentioned before resending.  I do have one more question, below.

> 
> > +EXPORT_SYMBOL(hv_read_config_block);
> 
> > +EXPORT_SYMBOL(hv_write_config_block);
> 
> > +EXPORT_SYMBOL(hv_register_block_invalidate);
> 
> I couldn't spot any users of these exports. Actually, I couldn't even
> spot any users of these three functions. Why were they added?
> 

This driver is intended to support both full PCI Express device pass through and also be the basis for SR-IOV networking on top of Hyper-V.  These functions would allow somebody trying to make their NIC driver work on top of Hyper-V to exchange messages with their back-end Windows driver.

My question is this.  How does somebody delivering a platform usually work with the Linux community to deliver enablement code like this?  I'm trying to work in the open, and go upstream early (or at least I think that understand what these things mean.)  If the community doesn't want functions that have no callers (and I understand that, too) then how should I provide them to the NIC vendors?

Thanks,
Jake Oshins