mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Boerner, Brian" <Brian_Boerner@adaptec.com>
To: "'Andi Kleen'" <ak@suse.de>,
	"Boerner, Brian" <Brian_Boerner@adaptec.com>
Cc: "'linux-kernel@vger.redhat.com'" <linux-kernel@vger.kernel.org>
Subject: RE: Disabling interrupts in 2.4.x
Date: Mon, 18 Dec 2000 15:24:01 -0500	[thread overview]
Message-ID: <E9EF680C48EAD311BDF400C04FA07B612D4DA5@ntcexc02.ntc.adaptec.com> (raw)

It's a UP configured system.

-bmb-


> -----Original Message-----
> From: Andi Kleen [mailto:ak@suse.de]
> Sent: Monday, December 18, 2000 3:18 PM
> To: Boerner, Brian
> Cc: 'linux-kernel@vger.redhat.com'
> Subject: Re: Disabling interrupts in 2.4.x
> 
> 
> > The only thing I am sure of is that interrupts are simply 
> not disabled.
> 
> They are only disabled on the local CPU, they could still 
> occur on other 
> CPUs. This is not different from 2.2.
> 
> > 
> > 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?
> 
> unsigned flag; 
> asm volatile("pushfl ; popfl %0" : "=r" (flag)); 
> printk(KERN_DEBUG "local interrupts are %s\n", (flag & 
> (1<<9)) ? "enabled" : "disabled"); 
> 
> -Andi
> 
-
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/

             reply	other threads:[~2000-12-18 21:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-18 20:24 Boerner, Brian [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-18 19:57 Boerner, Brian
2000-12-18 20:17 ` Andi Kleen
2000-12-18 21:39 ` Alan Cox

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=E9EF680C48EAD311BDF400C04FA07B612D4DA5@ntcexc02.ntc.adaptec.com \
    --to=brian_boerner@adaptec.com \
    --cc=ak@suse.de \
    --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®