public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Roland Dreier <rolandd@cisco.com>, linux-kernel@vger.kernel.org
Subject: Re: What is struct pci_driver.owner for?
Date: Tue, 18 Oct 2005 13:59:08 -0700	[thread overview]
Message-ID: <20051018205908.GA32435@suse.de> (raw)
In-Reply-To: <435560D0.8050205@pobox.com>

On Tue, Oct 18, 2005 at 04:53:36PM -0400, Jeff Garzik wrote:
> Roland Dreier wrote:
> >I just noticed that at some point, struct pci_driver grew a .owner
> >member.  However, only a handful of drivers set it:
> >
> >    $ grep -r -A10 pci_driver drivers/ | grep owner
> >    drivers/block/sx8.c-    .owner          = THIS_MODULE,
> >    drivers/ieee1394/pcilynx.c-     .owner =           THIS_MODULE,
> >    drivers/net/spider_net.c-       .owner          = THIS_MODULE,
> >    drivers/video/imsttfb.c-        .owner          = THIS_MODULE,
> >    drivers/video/kyro/fbdev.c-     .owner          = THIS_MODULE,
> >    drivers/video/tridentfb.c-      .owner  = THIS_MODULE,
> >
> >Should all drivers be setting .owner = THIS_MODULE?  Is this a good
> >kernel janitors task?
> 
> In theory its for module refcounting.  With so many PCI drivers and so 
> few pci_driver::owner users, it makes me wonder how needed it is.

It might in the future be needed for refcounting, I originally added it
when I thought it was needed.

But what it really does today is create the symlink from the driver to
the module that is contained in it, in sysfs.  Which is very invaluable
for people who want to know these things (installer programs, etc.)

For example:
$ tree /sys/bus/pci/drivers/uhci_hcd/
/sys/bus/pci/drivers/uhci_hcd/
|-- 0000:00:1d.0 -> ../../../../devices/pci0000:00/0000:00:1d.0
|-- 0000:00:1d.1 -> ../../../../devices/pci0000:00/0000:00:1d.1
|-- 0000:00:1d.2 -> ../../../../devices/pci0000:00/0000:00:1d.2
|-- 0000:00:1d.3 -> ../../../../devices/pci0000:00/0000:00:1d.3
|-- bind
|-- module -> ../../../../module/uhci_hcd
|-- new_id
`-- unbind


That "module" symlink is created only if the .owner field is set.
That's why people are going through and adding it to all of the drivers
in the system.

Hope this helps,

greg k-h	

  reply	other threads:[~2005-10-18 20:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18 20:47 What is struct pci_driver.owner for? Roland Dreier
2005-10-18 20:53 ` Jeff Garzik
2005-10-18 20:59   ` Greg KH [this message]
2005-10-18 21:04     ` Russell King
2005-10-18 21:06     ` Roland Dreier
2005-10-19 15:42       ` Jiri Slaby
2005-10-19 16:48         ` Roland Dreier
2005-10-19 16:51           ` Jiri Slaby

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=20051018205908.GA32435@suse.de \
    --to=gregkh@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rolandd@cisco.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