From: David Mosberger <davidm@napali.hpl.hp.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: "David S. Miller" <davem@redhat.com>,
davidm@napali.hpl.hp.com, davidm@hpl.hp.com,
linux-arch@vger.kernel.org
Subject: Re: remove irq_enter()/irq_exit() from hardirq.h
Date: Mon, 1 Mar 2004 11:59:53 -0800 [thread overview]
Message-ID: <16451.38457.951988.853182@napali.hpl.hp.com> (raw)
In-Reply-To: <OF6F51D31D.962B15AE-ONC1256E4A.00424524-C1256E4A.00434172@de.ibm.com>
>>>>> On Mon, 1 Mar 2004 13:14:36 +0100, Martin Schwidefsky <schwidefsky@de.ibm.com> said:
>> > but I'm wondering whether
>> > leaving irq_enter()/irq_exit() in hardirq.h might invite someone to
>> > use it outside of architecture-specific code (which is not the case at
>> > the moment, as far as I can see).
>>
>> I agree with you, it shouldn't be publicly visible. The s390 guys will
>> need to do some work as their drivers reference these two routines (ie.
>> grep under drivers/s390/)
Martin> Well, drivers/s390/cio is not really a driver. The main
Martin> interrupt function for i/o interrupts do_IRQ lives in
Martin> driver/s390/cio/cio.c and not in arch/s390/kernel/irq.c
Martin> where you might expect to find it. The irq_enter/ irq_exit
Martin> pair we just added in the sclp driver can be replaced with a
Martin> local_bh_enable/local_bh_disable pair. So we are pretty
Martin> clean.
OK, it sounds like there is no good reason to keep them in hardirq.h.
For ia64, I'll move them to irq_ia64.c. I won't touch other arches,
but for consistency's sake, it probably would be good to do a similar
thing on the other arches.
--david
next prev parent reply other threads:[~2004-03-01 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 12:14 remove irq_enter()/irq_exit() from hardirq.h Martin Schwidefsky
2004-03-01 19:59 ` David Mosberger [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-27 22:39 David Mosberger
2004-02-29 0:29 ` David S. Miller
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=16451.38457.951988.853182@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=linux-arch@vger.kernel.org \
--cc=schwidefsky@de.ibm.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