linux-kernel - Re: [PATCH v12 1/8] PCI: initialize and release SR-IOV capability

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]

Date:	Fri, 20 Mar 2009 10:54:09 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Yu Zhao <yu.zhao@...el.com>
Cc:	linux-pci@...r.kernel.org, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org, Yu Zhao <yu.zhao@...el.com>
Subject: Re: [PATCH v12 1/8] PCI: initialize and release SR-IOV capability

On Fri, 20 Mar 2009 11:25:11 +0800
Yu Zhao <yu.zhao@...el.com> wrote:

> If a device has the SR-IOV capability, initialize it (set the ARI
> Capable Hierarchy in the lowest numbered PF if necessary; calculate
> the System Page Size for the VF MMIO, probe the VF Offset, Stride
> and BARs). A lock for the VF bus allocation is also initialized if
> a PF is the lowest numbered PF.
> 
> Reviewed-by: Matthew Wilcox <willy@...ux.intel.com>
> Signed-off-by: Yu Zhao <yu.zhao@...el.com>

I applied this series to my linux-next branch, but there were a few
conflicts here and there, so please check it out.  Looks like from
start to finish this took about 6 months to get banged into shape,
thanks for staying on it, Yu!

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/