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: <20150615195027.GA5257@kroah.com>
Date:	Mon, 15 Jun 2015 12:50:27 -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, bhelgaas@...gle.com,
	linux-pci@...r.kernel.org, pebolle@...cali.nl,
	haiyangz@...rosoft.com, mebersol@...rosoft.com
Subject: Re: [PATCH v2 6/6] drivers:pci:hv: New paravirtual PCI front-end for
 Hyper-V VMs

On Mon, Jun 15, 2015 at 05:06:39PM +0000, jakeo@...rosoft.com wrote:
> From: Jake Oshins <jakeo@...rosoft.com>
> 
> This patch supplies a new driver, hv_pcifront, which exposes new root PCI
> buses.  When a Hyper-V VM running Linux is offered a paravirtual PCI bus
> in order to expose a device passed through on that bus, this drver
> registers a new bus with the PCI driver.  This new bus is bus "zero"
> within a new PCI domain.  This is done so that there's no overlap between
> the emulated, or fully virtualized, PCI that may be in the VM and a real
> PCIe device that will be exposed.
> 
> This PCI front-end only supports PCIe devices which do not use I/O BARs and
> which do not need a legacy INTx# interrupt (relying on MSI or MSI-X).
> Multifunction devices are supported, but devices with Type 1 or Type 2
> config headers are not supported.  (These are bridges to other PCI buses.)
> 
> The content of this patch differs from the one sent previously in that it
> incorporates feedback related to unused code (which has been removed) and
> GPL license (which has been updated.)  It also removes Kconfig lines that
> had been copied from the Xen PCI front-end entry, but which shouldn't be
> used here.

This paragraph goes below the --- line, we don't need it in the
changelog :(

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ