From: Christoph Hellwig <hch@infradead.org>
To: sbates@raithlin.com
Cc: corbet@lwn.net, bhelgaas@google.com, paulmck@linux.vnet.ibm.com,
tglx@linutronix.de, akpm@linux-foundation.org, mingo@kernel.org,
cdall@linaro.org, marc.zyngier@arm.com, zohar@linux.vnet.ibm.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, logang@deltatee.com, tom@talpey.com
Subject: Re: [PATCH] pci: Add a acs_disable option for pci kernel parameter
Date: Thu, 26 Oct 2017 23:37:45 -0700 [thread overview]
Message-ID: <20171027063745.GA19799@infradead.org> (raw)
In-Reply-To: <1509071869-18771-1-git-send-email-sbates@raithlin.com>
On Thu, Oct 26, 2017 at 08:37:49PM -0600, sbates@raithlin.com wrote:
> From: Stephen Bates <sbates@raithlin.com>
>
> On some servers the BIOS sets up ACS on any valid pci_dev in the
> system. The kernel has no way of backing this out since the kernel
> only turns ACS capabilities on.
>
> This patch adds a new boot option to the pci kernel parameter called
> "acs_disable" that will disable ACS. This is useful for PCI peer to
> peer communication but can cause problems when IOVA isolation is
> required and an IOMMU is enabled. Use with care.
Eww. Can we please add smbios quirks for the systems where you've
observed this? (we probably also want to keep the option just in case).
next prev parent reply other threads:[~2017-10-27 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 2:37 [PATCH] pci: Add a acs_disable option for pci kernel parameter sbates
2017-10-27 6:37 ` Christoph Hellwig [this message]
2017-10-30 1:04 ` Stephen Bates
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=20171027063745.GA19799@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=cdall@linaro.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=marc.zyngier@arm.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sbates@raithlin.com \
--cc=tglx@linutronix.de \
--cc=tom@talpey.com \
--cc=zohar@linux.vnet.ibm.com \
/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).