From: Rusty Russell <rusty@rustcorp.com.au>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Module Refcount & Stuff mini-FAQ
Date: Mon, 25 Nov 2002 11:26:25 +1100 [thread overview]
Message-ID: <20021125003005.130DA2C087@lists.samba.org> (raw)
In-Reply-To: Your message of "Sat, 23 Nov 2002 23:23:34 BST." <20021123222334.GB5170@elf.ucw.cz>
In message <20021123222334.GB5170@elf.ucw.cz> you write:
> Hi!
>
> > Q: How does the module remove code work?
> > A: It stops the machine by scheduling threads for every other CPU,
> > then they all disable interrupts. At this stage we know that noone
> > is in try_module_get(), so we can reliably read the counter. If
> > zero, or the rmmod user specified --wait, we set the live flag to
> > false. After this, the reference count should not increase, and
> > each module_put() will wake us up, so we can check the counter
> > again.
>
> Where is this implemented? I guess I need this for swsusp...
I'm not so sure, but it's worth a look. Look for stop_refcounts() in
module.c. BTW, I call this a "bogolock".
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-11-25 0:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 22:58 Rusty Russell
2002-11-19 2:30 ` Werner Almesberger
2002-11-24 22:50 ` Rusty Russell
2002-11-25 2:07 ` Werner Almesberger
2002-11-25 2:27 ` Rusty Russell
2002-11-25 6:39 ` Werner Almesberger
2002-11-25 22:43 ` Rusty Russell
2002-11-26 2:26 ` Werner Almesberger
2002-11-26 3:16 ` Rusty Russell
2002-11-26 7:12 ` Werner Almesberger
2002-11-26 22:56 ` Rusty Russell
2002-11-19 2:40 ` John Levon
2002-11-24 23:02 ` Rusty Russell
2002-11-25 0:38 ` John Levon
2002-11-19 3:10 ` kksymoops Jeff Garzik
2002-11-19 3:50 ` kksymoops Jeff Garzik
2002-11-19 21:10 ` kksymoops Rusty Russell
2002-11-20 15:46 ` kksymoops Kai Germaschewski
2002-11-23 22:23 ` Module Refcount & Stuff mini-FAQ Pavel Machek
2002-11-25 0:26 ` Rusty Russell [this message]
2002-11-19 19:18 Adam J. Richter
2002-11-20 12:25 Adam J. Richter
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=20021125003005.130DA2C087@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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®