mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Chiang <achiang@hp.com>
To: jbarnes@virtuousgeek.org
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alex Chiang <achiang@hp.com>
Subject: [RFC PATCH v2 11/12] PCI Hotplug: schedule fakephp for feature removal
Date: Fri, 13 Feb 2009 13:19:49 -0700	[thread overview]
Message-ID: <20090213201949.19262.9913.stgit@bob.kio> (raw)
In-Reply-To: <20090213201135.19262.67924.stgit@bob.kio>

Now that the PCI core is capable of function-level remove and rescan
as well as bus-level rescan, there's no functional need to keep fakephp
anymore.

We keep it around for userspace compatibility reasons, schedule removal
in three years.

Signed-off-by: Alex Chiang <achiang@hp.com>
---

 Documentation/feature-removal-schedule.txt |   32 ++++++++++++++++++++++++++++
 1 files changed, 32 insertions(+), 0 deletions(-)

diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 5ddbe35..fc3505b 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -335,3 +335,35 @@ Why:	In 2.6.18 the Secmark concept was introduced to replace the "compat_net"
 	Secmark, it is time to deprecate the older mechanism and start the
 	process of removing the old code.
 Who:	Paul Moore <paul.moore@hp.com>
+
+---------------------------
+
+What:	fakephp and associated sysfs files in /sys/bus/pci/slots/
+When:	2011
+Why:	In 2.6.27, the semantics of /sys/bus/pci/slots was redefined to
+	represent a machine's physical PCI slots. The change in semantics
+	had userspace implications, as the hotplug core no longer allowed
+	drivers to create multiple sysfs files per physical slot (required
+	for multi-function devices, e.g.). fakephp was seen as a developer's
+	tool only, and its interface changed. Too late, we learned that
+	there were some users of the fakephp interface.
+
+	In 2.6.30, the original fakephp interface was restored. At the same
+	time, the PCI core gained the ability that fakephp provided, namely
+	function-level hot-remove and hot-add.
+
+	Since the PCI core now provides the same functionality, exposed in:
+
+		/sys/bus/pci/rescan
+		/sys/bus/pci/devices/.../remove
+		/sys/bus/pci/devices/.../rescan
+
+	there is no functional reason to maintain fakephp as well.
+
+	We will keep the existing module so that 'modprobe fakephp' will
+	present the old /sys/bus/pci/slots/... interface for compatibility,
+	but users are urged to migrate their applications to the API above.
+
+	After a reasonable transition period, we will remove the legacy
+	fakephp interface.
+Who:	Alex Chiang <achiang@hp.com>


  parent reply	other threads:[~2009-02-13 20:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 20:18 [RFC PATCH v2 00/12] PCI core learns hotplug Alex Chiang
2009-02-13 20:18 ` [RFC PATCH v2 01/12] PCI: don't scan existing devices Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 02/12] PCI: pci_scan_slot() returns newly found devices Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 03/12] PCI: always scan child buses Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 04/12] PCI: properly clean up ASPM link state on device remove Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 05/12] PCI: beef up pci_do_scan_bus() Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 06/12] PCI: Introduce /sys/bus/pci/rescan Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 07/12] PCI: Introduce /sys/bus/pci/devices/.../remove Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 08/12] PCI: Introduce /sys/bus/pci/devices/.../rescan Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 09/12] PCI Hotplug: restore fakephp interface with complete reimplementation Alex Chiang
2009-02-13 20:19 ` [RFC PATCH v2 10/12] PCI Hotplug: rename legacy_fakephp to fakephp Alex Chiang
2009-02-13 20:19 ` Alex Chiang [this message]
2009-02-13 20:19 ` [RFC PATCH v2 12/12] PCI: more whitespace cleanups Alex Chiang

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=20090213201949.19262.9913.stgit@bob.kio \
    --to=achiang@hp.com \
    --cc=jbarnes@virtuousgeek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome