public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: Alex Chiang <achiang@hp.com>,
	"Darrick J. Wong" <djwong@us.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	linux-pci <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] fakephp: Allocate PCI resources before adding the	device
Date: Fri, 28 Nov 2008 11:57:23 -0700	[thread overview]
Message-ID: <20081128185722.GU25548@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0811280151230.24816@shell4.speakeasy.net>

On Fri, Nov 28, 2008 at 02:11:49AM -0800, Trent Piepho wrote:
> On Wed, 26 Nov 2008, Matthew Wilcox wrote:
> > Because fakephp was the odd one out.  Every other hotplug driver
> > registers a slot number and puts the address in the directory.  We're
> > making hotplug drivers simpler (by sharing more of the logic in the
> > core) and so fakephp had to change to match the other drivers.  I'm
> > sorry for your inconvenience, but it's necessary.
> 
> Seems like changing a long established interface like this should be put on
> the feature removable schedule.

sysfs is more fluid than other interfaces.  Large parts of it
change without warning.  I suppose it could have gone through
feature-removal-schedule, and perhaps we should try to do that in future.

> > We can discuss other ways to make your life better, but it can't be
> > changed back to one 'slot' per PCI function.
> 
> Why not have a slot per pci function with each hotplug driver adding
> attributes to the slot?  The slot would be registered by the hotplug core.

What we have now is the 'address' file managed by the core.  This
doesn't include the function number.

> Is there any reason the fakephp driver should not be allowed to enable and
> disable individual functions?  There a lot of mutli-function devices that
> allow individual functions to be enabled and disabled with registers on the
> primary function.  For instance, it would be possible to work around a BIOS
> that doesn't have an option to disabled a southbridge's USB controller by
> doing so in Linux and then using fakephp to remove the device, and thus
> free address space that other devices might need.

There are lots of circumstances where enabling and disabling individual
functions is a good idea, but I don't think that fakephp is the right
way to do it.  We need a better interface.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2008-11-28 18:57 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 21:24 [PATCH] fakephp: Allocate PCI resources before adding the device Darrick J. Wong
2008-11-25 21:43 ` Greg KH
2008-11-26  4:46 ` Trent Piepho
2008-11-26  7:48   ` Darrick J. Wong
2008-11-26  9:56     ` Trent Piepho
2008-11-26 18:18       ` Darrick J. Wong
2008-11-26 22:23         ` Trent Piepho
2008-11-26 22:55           ` Alex Chiang
2008-11-27  1:44             ` Trent Piepho
2008-11-27  2:42               ` Matthew Wilcox
2008-11-28 10:11                 ` Trent Piepho
2008-11-28 18:57                   ` Matthew Wilcox [this message]
2008-11-28 21:21                     ` Trent Piepho
2008-11-28 21:30                       ` Matthew Wilcox
2008-12-01  1:10                         ` Problems with fakephp Trent Piepho
2008-12-16 20:28                           ` fixup PCI device booleans in sysfs Jesse Barnes
2008-11-28 23:18               ` [PATCH] fakephp: Allocate PCI resources before adding the device Alex Chiang
2008-12-01 13:00                 ` Problems with fakephp Trent Piepho
2008-12-02  3:16                   ` Alex Chiang
2008-12-03  4:07                     ` Trent Piepho
2008-12-03  4:38                       ` Alex Chiang
2008-12-03 17:22                         ` Rolf Eike Beer
2008-12-03 17:43                           ` Alex Chiang
2008-12-03 17:55                             ` Rolf Eike Beer
2008-12-03 18:22                               ` Alex Chiang
2008-12-08 21:09                                 ` Rolf Eike Beer
2008-12-01 13:36                 ` Trent Piepho
2008-12-01 14:08                   ` [PATCH] PCI: Method for removing PCI devices Trent Piepho
2008-12-01 14:40                     ` Greg KH
2008-12-01 14:08                   ` [PATCH] PCI: Legacy fakephp driver Trent Piepho
2008-11-27  1:52             ` [PATCH] fakephp: Allocate PCI resources before adding the device Darrick J. Wong
2008-11-28  9:51               ` Trent Piepho
2008-11-28 18:42                 ` Rolf Eike Beer
2008-11-28 21:06                   ` Trent Piepho
2008-12-01 17:08                     ` Rolf Eike Beer
2008-12-16 19:33                       ` Jesse Barnes
2008-12-16 20:56                         ` [PATCH] fakephp: Allocate PCI resources before adding the?device Darrick J. Wong
2008-12-21  2:23                           ` Trent Piepho

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=20081128185722.GU25548@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=achiang@hp.com \
    --cc=djwong@us.ibm.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=xyzzy@speakeasy.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