From: kernel-stuff <kernel-stuff@comcast.net>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, acurrid@nvidia.com
Subject: Re: X86_64: Many Lost ticks
Date: Fri, 19 Nov 2004 19:17:12 -0500 [thread overview]
Message-ID: <200411191917.13165.kernel-stuff@comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0411190856121.7201@musoma.fsmlabs.com>
On Friday 19 November 2004 10:57, Zwane Mwaikambo wrote:
> Thanks for confirming that Parry, so your system definitely is using the
> IOAPIC now (/proc/interrupts output should suffice)?
>
Yes it does seem so. Here goes /proc/interrupts
CPU0
0: 138237 IO-APIC-edge timer
1: 77 IO-APIC-edge i8042
8: 0 IO-APIC-edge rtc
9: 198 IO-APIC-level acpi
12: 1427 IO-APIC-edge i8042
14: 11445 IO-APIC-edge ide0
15: 193 IO-APIC-edge ide1
177: 0 IO-APIC-level ehci_hcd
185: 382 IO-APIC-level NVidia nForce3, ohci_hcd
193: 0 IO-APIC-level NVidia nForce3 Modem, ohci_hcd
201: 4 IO-APIC-level yenta, ohci1394
209: 289 IO-APIC-level yenta, eth0
225: 7247 IO-APIC-level nvidia
NMI: 59
LOC: 138123
ERR: 0
MIS: 0
next prev parent reply other threads:[~2004-11-20 0:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 17:02 kernel-stuff
2004-11-18 17:08 ` Zwane Mwaikambo
2004-11-18 17:10 ` Alan Cox
2004-11-18 18:24 ` Zwane Mwaikambo
2004-11-18 18:50 ` Andi Kleen
2004-11-18 18:49 ` Andi Kleen
2004-11-19 1:56 ` kernel-stuff
2004-11-19 15:57 ` Zwane Mwaikambo
2004-11-20 0:17 ` kernel-stuff [this message]
2004-11-20 2:39 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2004-11-22 15:11 Chuck Ebbert
2004-11-19 8:19 Chuck Ebbert
2004-11-19 16:11 ` Zwane Mwaikambo
2004-11-18 19:30 kernel-stuff
2004-11-18 19:03 kernel-stuff
2004-11-18 17:19 kernel-stuff
2004-11-18 4:14 kernel-stuff
2004-11-18 4:02 kernel-stuff
2004-11-18 5:06 ` Andi Kleen
2004-11-18 15:54 ` Zwane Mwaikambo
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=200411191917.13165.kernel-stuff@comcast.net \
--to=kernel-stuff@comcast.net \
--cc=acurrid@nvidia.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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
Powered by JetHome