From: Ingo Molnar <mingo@elte.hu>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: appearance of /proc/interrupts ?
Date: Thu, 11 Jan 2007 10:50:55 +0100 [thread overview]
Message-ID: <20070111095055.GA29844@elte.hu> (raw)
In-Reply-To: <45A608A0.1050407@imc-berlin.de>
* Steven Scholz <steven.scholz@imc-berlin.de> wrote:
> with Linux 2.6.17-rt3 /proc/interrupts looks as described on
>
> http://rt.wiki.kernel.org/index.php/RT_PREEMPT_HOWTO
>
> CPU0
> 0: 11188 XT-PIC [........N/ 0]-level pit
> 1: 8 XT-PIC [........./ 0]-level i8042
> 2: 0 XT-PIC [........N/ 0]-level cascade
> 4: 131 XT-PIC [........./ 10]-level serial
> 11: 10 XT-PIC [........./ 0]-level eth0
> 14: 4087 XT-PIC [........./ 0]-level ide0
>
> But when using a Linux 2.6.19.1-rt15 it looks like
>
> CPU0
> 0: 15499 IO-APIC-edge timer
> 1: 8 IO-APIC-edge i8042
> 4: 161 IO-APIC-edge serial
> 9: 0 IO-APIC-fasteoi acpi
> 12: 3 IO-APIC-edge i8042
> 14: 4082 IO-APIC-edge ide0
> 16: 93 IO-APIC-fasteoi eth0
>
> which is pretty much the same as a vanilla 2.6.19.
>
> What does it mean? Is RT PREEMPT not working correctly?
i restored it to be as compatible with upstream as possible. You have a
PREEMPT_RT kernel if you have this message in the dmesg:
Real-Time Preemption Support (C) 2004-2006 Ingo Molnar
Ingo
next prev parent reply other threads:[~2007-01-11 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 9:51 appearance of /proc/interrupts ? Steven Scholz
2007-01-11 9:50 ` Ingo Molnar [this message]
2007-01-11 11:04 ` Steven Scholz
2007-01-11 11:50 ` Robert Schwebel
2007-01-11 15:19 ` Steven Scholz
2007-01-12 9:13 ` Luotao Fu
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=20070111095055.GA29844@elte.hu \
--to=mingo@elte.hu \
--cc=linux-rt-users@vger.kernel.org \
--cc=steven.scholz@imc-berlin.de \
/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;
as well as URLs for NNTP newsgroup(s).