netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <roland@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Emil Tantilov <emil.s.tantilov@intel.com>
Subject: Re: [PATCH] PCI: Update ACS quirk for more Intel 10G NICs
Date: Fri, 4 Aug 2017 14:47:10 -0700	[thread overview]
Message-ID: <CAG4TOxOt=dtUW8q+G-ZRdF-ik19jp2Luw1K8dxHaH2f6AMTZLA@mail.gmail.com> (raw)
In-Reply-To: <20170803161623.31e5fb86@w520.home>

> I think the conclusion is that a hard-wired ACS capability is a
> positive indication of isolation for a multifunction device, the code
> is intended to support this and appears to do so, and Roland was going
> to investigate the sightings that inspired this patch in more detail.
> Dropping for now is appropriate.  Thanks,

That's right.  I confirmed that the issue we found was due to another PCI quirk.

It may make sense to add more 82599 variants to the table, but the X540 and X550
work without a quirk.

Sorry for the noise.

 - R.

  reply	other threads:[~2017-08-04 21:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20 21:41 [PATCH] PCI: Update ACS quirk for more Intel 10G NICs Roland Dreier
2017-07-20 22:15 ` Alex Williamson
2017-07-20 22:53   ` Roland Dreier
2017-07-24 16:45     ` Alex Williamson
2017-07-24 17:18       ` Roland Dreier
2017-07-24 19:01         ` Alex Williamson
2017-07-24 19:31           ` Roland Dreier
2017-07-24 20:57             ` Alex Williamson
2017-07-20 22:50 ` Tantilov, Emil S
2017-08-03 21:49 ` Bjorn Helgaas
2017-08-03 22:16   ` Alex Williamson
2017-08-04 21:47     ` Roland Dreier [this message]
2017-08-04 13:28   ` David Laight
2017-08-04 14:28     ` Alex Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAG4TOxOt=dtUW8q+G-ZRdF-ik19jp2Luw1K8dxHaH2f6AMTZLA@mail.gmail.com' \
    --to=roland@kernel.org \
    --cc=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=emil.s.tantilov@intel.com \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).