On Thu, Jun 27, 2013 at 04:39:41PM -0600, Alex Williamson wrote:
> v2:
>
> Revised patch 1/ to match comments from Bjorn. PCIe event collectors
> and PCIe-to-PCI bridges now indicate that they do not support ACS.
> I've reached out to try to get clarification on this, but I think it's
> reasonabl
This series was ack'd by Don. I haven't heard reports of any problems.
What more needs to be done here? Bjorn? Thanks,
Alex
On Mon, 2013-07-08 at 10:17 -0600, Alex Williamson wrote:
> Ping. Comments?
>
> On Thu, 2013-06-27 at 16:39 -0600, Alex Williamson wrote:
> > v2:
> >
> > Revised pat
On 07/08/2013 12:17 PM, Alex Williamson wrote:
Ping. Comments?
As I read the PCIe & SRIOV specs wrt ACS, this patch set appears
to fix the nuances we have learned about whether a device (MFD or bridge)
implements (the equiv. of) ACS, or not, as required (for secure, device
assignment).
Like t
Ping. Comments?
On Thu, 2013-06-27 at 16:39 -0600, Alex Williamson wrote:
> v2:
>
> Revised patch 1/ to match comments from Bjorn. PCIe event collectors
> and PCIe-to-PCI bridges now indicate that they do not support ACS.
> I've reached out to try to get clarification on this, but I think it's
v2:
Revised patch 1/ to match comments from Bjorn. PCIe event collectors
and PCIe-to-PCI bridges now indicate that they do not support ACS.
I've reached out to try to get clarification on this, but I think it's
reasonable to proceed with a conservative approach until then. I also
added PCI-to-PC
5 matches
Mail list logo