All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Derrick <jonathan.derrick@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Bjorn Helgaas <helgaas@kernel.org>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Alan Cox <alan@linux.intel.com>,
	Dan J Williams <dan.j.williams@intel.com>,
	Jon Derrick <jonathan.derrick@intel.com>
Subject: [RFC 3/3] Documentation: Add pci device delete_id interface
Date: Wed, 27 Sep 2017 16:40:22 -0400	[thread overview]
Message-ID: <1506544822-2632-4-git-send-email-jonathan.derrick@intel.com> (raw)
In-Reply-To: <1506544822-2632-1-git-send-email-jonathan.derrick@intel.com>

Document the <driver>.delete_id= cmdline interface for masking built-in
and module device id tables.

Signed-off-by: Jon Derrick <jonathan.derrick@intel.com>
---
 Documentation/admin-guide/kernel-parameters.txt | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index 0549662..862c8b5 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -789,6 +789,19 @@
 			Defaults to the default architecture's huge page size
 			if not specified.
 
+	driver.delete_id=
+			[PCI]
+			Specified pci device format(s) will mask built-in
+			driver id tables, preventing devices from
+			automicatically attaching to built-in or module
+			drivers.  Later attachment should be done by adding the
+			deleted id back through the "new_id" sysfs interface.
+			Format: <vendor>:<device>[:<subvendor>:<subdevice>]\
+					[:class][:class_mask][, ...]
+			PCI_ANY_ID masks should use the full 32-bit format.
+			Examples: virtio-pci.delete_id=ffffffff:ffffffff
+				  nvme.delete_id=1234:5678,1111:ffffffff
+
 	dhash_entries=	[KNL]
 			Set number of hash buckets for dentry cache.
 
-- 
1.8.3.1

      parent reply	other threads:[~2017-09-27 20:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27 20:40 [RFC 0/3] Introduce PCI device blacklisting Jon Derrick
2017-09-27 20:40 ` [RFC 1/3] PCI: pci-driver: Introduce pci device delete list Jon Derrick
2017-09-28  9:09   ` Greg Kroah-Hartman
2017-09-28 15:53     ` Jon Derrick
2017-09-28 15:58     ` Dan Williams
2017-09-27 20:40 ` [RFC 2/3] module: Ignore delete_id parameter Jon Derrick
2017-09-28  6:03   ` Dan Williams
2017-09-28 15:57     ` Jon Derrick
2017-09-28  9:02   ` Greg Kroah-Hartman
2017-09-28 15:57     ` Jon Derrick
2017-09-27 20:40 ` Jon Derrick [this message]

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=1506544822-2632-4-git-send-email-jonathan.derrick@intel.com \
    --to=jonathan.derrick@intel.com \
    --cc=alan@linux.intel.com \
    --cc=arjan@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@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 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.