mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Brice Goglin <Brice.Goglin@ens-lyon.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: AGP module removal impossible ?
Date: Mon, 14 Mar 2005 20:06:32 -0500	[thread overview]
Message-ID: <20050315010631.GA8512@redhat.com> (raw)
In-Reply-To: <42361E33.4020903@ens-lyon.org>

On Tue, Mar 15, 2005 at 12:28:51AM +0100, Brice Goglin wrote:
 > Hi Dave,
 > 
 > I can't remove the AGP chipset module on my boxes.
 > Looks like the AGP chipset driver holds a reference on itself and
 > thus makes removal impossible.
 > 
 > From what I understand, as soon as intel_agp is loaded, agp_intel_probe
 > is called. It gets a reference on intel_agp module through
 > !try_module_get(bridge->driver->owner) in agp_add_bridge.
 > Then this reference can only be released through module_put in
 > agp_remove_bridge which is called agp_intel_remove which is only called
 > when removing the module.
 > 
 > Thus it looks impossible to remove this module at all.
 > And I think the problem occurs with all other AGP chipset drivers.
 > 
 > I hope the reason is not just that module removal support is not important
 > in 2.6 :) It looks strange to implement a module removal routine if we
 > know it can't be used :)

The locking is screwed up and has been for some time.
I've been meaning to take a look at it for a while, but keep finding
more important things to do.  It should be fixed to lock/unlock when
the device is opened, as it was in 2.4

		Dave


      reply	other threads:[~2005-03-15  1:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 23:28 Brice Goglin
2005-03-15  1:06 ` Dave Jones [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=20050315010631.GA8512@redhat.com \
    --to=davej@redhat.com \
    --cc=Brice.Goglin@ens-lyon.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®