linux-kernel - Re: [PATCH 0/6] Front-end driver for PCIe Pass-through on Hyper-V

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: <20150611174726.GD22639@kroah.com>
Date:	Thu, 11 Jun 2015 10:47:26 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	jakeo@...rosoft.com
Cc:	kys@...rosoft.com, 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, mebersol@...rosoft.com, haiyangz@...rosoft.com
Subject: Re: [PATCH 0/6] Front-end driver for PCIe Pass-through on Hyper-V

On Thu, Jun 11, 2015 at 04:22:21PM +0000, jakeo@...rosoft.com wrote:
> From: Jake Oshins <jakeo@...rosoft.com>
> 
> This patch does some slight refactoring on the hv_vmbus driver and its
> dependents and then introduces a new paravirtual front-end driver for PCI
> which supports PCI Express devices passed through to a Linux guest running
> in a Hyper-V VM.
> 
> To support this front-end, several new mechanisms are introduced:
> 
> 1 - A common way of finding free memory-mapped I/O space in a Hyper-V VM, 
>     available to all Hyper-V-related drivers.
> 
> 2 - A way of handling PCI Message-Signaled Interrupt (MSI and MSI-X)
>     creation and formatting when Hyper-V is running.
> 
> 3 - A mapping function from Linux processor number to Hyper-V virtual
>     processor number, available to drivers, which is necessary for MSI(-X)
>     creation.
> 
> The Hyper-V Frame Buffer driver is modified to use the MMIO space
> allocation function so that its allocations both don't collide with the
> PCI front end and so that the chosen range can come from any available
> part of MMIO space.
> 
> Finally, the new PCI front-end driver is the last patch in the series.

All of this information needs to be in the patches themselves, they all
do not have any changelog information in them at all, making them not
acceptable at all.

Please fix all of this up and resend.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/