From: Jes Sorensen <Jes.Sorensen@cern.ch>
To: torvalds@transmeta.com
Cc: x-linux-kernel@vger.rutgers.edu
Subject: irq.h changes in 2.3.14
Date: Thu, 19 Aug 1999 11:14:10 +0200 [thread overview]
Message-ID: <199908190914.LAA15538@lxp03.cern.ch> (raw)
Hi
I noticed the moving of arch/i386/kernel/irq.h to include/linux/irq.h in
the 2.3.14 final patch.
I really don't think it is a good idea to move this very i386 specific
definitions in there since the interrupt subsystems on other
architectures are very different from that of the i386. Ie. on the m68k
we do not use the same types or irq descriptors, the IRQ line statuses
make no sense etc. and I am sure it is the same for some of the other
non x86 architectures.
I see that it expects asm/hw_irq.h to be the architecture dependant
stuff, but even the things that made it into include/linux/irq.h are way
to architecture specific.
Putting this include file in include/linux/irq.h with a generic name
like that means someone is going to use it in the generic kernel code at
some point. Having the common kernel code relying on such x86 specific
features is going to be a pain for us to handle at that point.
The only things I can see being architecture independant is the
irq_{enter,exit}() stuff and even then I am not sure the SMP versions
are portable enough for non x86 machines (being able to do test_bit() on
a spin lock is fairly implementation specific).
I really think those bits should be moved out of the generic header
files to avoid problems.
Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~1999-08-19 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-19 9:14 Jes Sorensen [this message]
1999-08-19 17:45 ` Linus Torvalds
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=199908190914.LAA15538@lxp03.cern.ch \
--to=jes.sorensen@cern.ch \
--cc=torvalds@transmeta.com \
--cc=x-linux-kernel@vger.rutgers.edu \
/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®