From: "Boerner, Brian" <Brian_Boerner@adaptec.com>
To: "'linux-kernel@vger.redhat.com'" <linux-kernel@vger.kernel.org>
Subject: Disabling interrupts in 2.4.x
Date: Mon, 18 Dec 2000 14:57:19 -0500 [thread overview]
Message-ID: <E9EF680C48EAD311BDF400C04FA07B612D4DA4@ntcexc02.ntc.adaptec.com> (raw)
I'm still trying to get the aacraid driver up and running on 2.4 and have
worked it down to this final problem. It appears that interrupts are not
being disabled properly using spin_lock_irqsave. I'm using 2.4.0-test11.
I make this call:
spin_lock_irqsave ( &(SpinLock->spin_lock), SpinLock->cpu_flags);
where SpinLock is of type pointer to an OS_SPINLOCK structure defined as:
typedef _OS_SPINLOCK {
spinlock_t spin_lock;
unsigned cpu_lock_count[NR_CPUS];
long cpu_flag;
long lockout_count;
} OS_SPINLOCK;
This is the same call that I was making in 2.2.x kernel and don't have any
problems.
I would expect this function to disable interrupts, but given the scale of
change between 2.2.x spinlock.h and 2.4.x spinlock.h I'm just not sure
anymore.
The only thing I am sure of is that interrupts are simply not disabled.
I've also looked at some other scsi drivers that are disabling interrupts
and they appear to be making similar calls to spin_lock_irqsave.
Does anyone have any suggestions for debugging this? Is there a call that
can be made to find out if interrupts are actually disabled?
Brian M. Boerner
System Software Developer
Adaptec, Inc.
Nashua, NH 03060
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-18 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-18 19:57 Boerner, Brian [this message]
2000-12-18 20:17 ` Andi Kleen
2000-12-18 21:39 ` Alan Cox
2000-12-18 20:24 Boerner, Brian
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=E9EF680C48EAD311BDF400C04FA07B612D4DA4@ntcexc02.ntc.adaptec.com \
--to=brian_boerner@adaptec.com \
--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®