From: Chris Friesen <chris.friesen@windriver.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] PCI ACS quirk for X710/XL710?
Date: Tue, 1 Dec 2015 10:19:01 -0600 [thread overview]
Message-ID: <565DC875.1020902@windriver.com> (raw)
In-Reply-To: <565DC5D4.70300@windriver.com>
On 12/01/2015 10:07 AM, Chris Friesen wrote:
> Hi all,
>
> The three of you in the "to" list were involved with adding commits d748804 and
> 100ebb2 to address the fact that these multi-port NICs will not do peer-to-peer
> between functions, but do not report this via ACS.
>
> We've got an X710 device (PCI device 0x1572, driver version 1.3.1-k, firmware
> 4.40) and we're seeing all the ports being assigned to the same IOMMU group.
>
> I'm guessing that this is due to a lack of ACS, and that it would be valid to
> add the X710/XL710 PCI IDs to the pci_dev_acs_enabled table. Could someone from
> Intel confirm this?
Looking at the datasheet (I suppose I should have done that first, sorry) it
looks like this device supports ACS. However, we're still seeing all the ports
being placed into the same IOMMU group.
Is there a way to prevent/disable this behaviour? We want to be able to assign
each port to a separate VM, and thus for our purposes they need to be in
separate IOMMU groups.
Chris
next prev parent reply other threads:[~2015-12-01 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 16:07 [Intel-wired-lan] PCI ACS quirk for X710/XL710? Chris Friesen
2015-12-01 16:19 ` Chris Friesen [this message]
2015-12-01 17:57 ` Alex Williamson
2015-12-01 19:31 ` Chris Friesen
2015-12-02 15:21 ` Alex Williamson
2015-12-02 15:37 ` Chris Friesen
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=565DC875.1020902@windriver.com \
--to=chris.friesen@windriver.com \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.