From: Robert Love <rml@tech9.net>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: "David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: calling schedule() from interupt context
Date: 24 Nov 2002 17:41:43 -0500 [thread overview]
Message-ID: <1038177703.777.62.camel@phantasy> (raw)
In-Reply-To: <20021124223234.7C5EB2C111@lists.samba.org>
On Sun, 2002-11-24 at 16:42, Rusty Russell wrote:
> > Oh we can't kill module references from interrupts?
>
> Err, no, that would be insane. get_cpu() & put_cpu() should work
> perfectly fine inside interrupts, no?
Yes, they do.
Since the preempt_count is bumped on entry to the interrupt handler, it
is always at least one, and thus put_cpu() will never call schedule.
Robert Love
next prev parent reply other threads:[~2002-11-24 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 8:54 dan carpenter
2002-11-22 9:09 ` David S. Miller
2002-11-22 9:16 ` Robert Love
2002-11-24 21:42 ` Rusty Russell
2002-11-24 22:41 ` Robert Love [this message]
2002-11-22 9:14 ` Robert Love
2002-11-22 16:04 dan carpenter
2002-11-22 16:11 ` Robert Love
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=1038177703.777.62.camel@phantasy \
--to=rml@tech9.net \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®