From: Matthew Wilcox <willy@debian.org>
To: Grant Grundler <grundler@dsl2.external.hp.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] rp2470 hang...getting closer
Date: Mon, 21 Oct 2002 03:21:13 +0100 [thread overview]
Message-ID: <20021021032113.G5285@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20021021005716.B27384829@dsl2.external.hp.com>; from grundler@dsl2.external.hp.com on Sun, Oct 20, 2002 at 06:57:16PM -0600
On Sun, Oct 20, 2002 at 06:57:16PM -0600, Grant Grundler wrote:
> Lastly, use of IPI to set_eiem() on all CPUs can probably go away.
> In 2.5, I was under the impression we no longer require globally
> disabling of interrupts - only on the local CPU. For both 2.4
> and 2.5, parisc only needs to mask/unmask the EIEM bit on the CPU
> that is the target of that IRQ, not all CPUs. ie if the IPI
> is needed, it should just target the same CPU which will handle the
> specific external intr.
hmm.. not sure about disable_irq() -- certainly sti() is gone and __sti()
is local_irq_disable() in 2.5; but i think enable/disable_irq still act
globally. i think this is because it's supposed to go and enable/disable
delivery of interrupts in the (io)(s)(a)pic, rather than playing with
the cpu interrupt masks.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-10-21 2:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 4:40 [parisc-linux] rp2470 hang...getting closer Grant Grundler
2002-10-13 13:56 ` Thibaut VARENE
2002-10-21 0:57 ` Grant Grundler
2002-10-21 2:21 ` Matthew Wilcox [this message]
2002-10-21 3:33 ` Grant Grundler
2002-10-21 14:59 ` Matthew Wilcox
2002-10-21 15:26 ` Matthew Wilcox
2002-10-21 21:58 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2002-10-22 0:41 John Marvin
2002-10-23 1:19 ` Grant Grundler
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=20021021032113.G5285@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=grundler@dsl2.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.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