From: Robert Love <rml@tech9.net>
To: Arjan Filius <iafilius@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Feedback on preemptible kernel patch
Date: 15 Sep 2001 13:57:44 -0400 [thread overview]
Message-ID: <1000576671.32708.23.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.33.0109151131320.32167-100000@sjoerd.sjoerdnet>
In-Reply-To: <Pine.LNX.4.33.0109151131320.32167-100000@sjoerd.sjoerdnet>
On Sat, 2001-09-15 at 05:44, Arjan Filius wrote:
> Hi Robert,
Hi Arjan,
> Didn't discover yet, the only "strange" thing is when using <TAB>
> autocompleteion in a kterm in kde i get every time a kde crash-bug-report
> popup message. however, no kernel messages or whatsoever.
Odd. This does not occur without preemption enabled?
> Well it's a fpu patch, and as far as i know i don't use the fpu that much
> at the moment but i'll try that.
Its a patch for when the kernel uses the FPU, specifically during MMX or
3DNow instructions. That is why iys for Athlon-optimized kernels,
because the Athlon uses 3DNow instructions for some fast page copies.
When the kernel uses FPU, it does not use SMP locks, since that is a per
CPU condition. However, preemption can occur in the middle of a CPU
doing that stuff, and that messes stuff up very much. The Athlon patch
fixes it, it is much needed if your kernel is Athlon-optimized.
Userspace FPU is controlled by the kernel already, so we don't need to
worry about that. In userspace, the kernel handles everything ... in
kernel land, if we want to go play with something (like 3DNow), we need
to take care to set it up and restore ourselves properly.
> in the hope finding the usage of fpu-irq:
> sjoerd:/usr/src/linux # cat /proc/interrupts
> CPU0
> 0: 13374740 XT-PIC timer
> 1: 14581 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 9: 238018 XT-PIC usb-uhci, usb-uhci, EMU10K1
> 10: 601500 XT-PIC ide2, sym53c8xx
> 11: 87300 XT-PIC eth0
> 12: 230338 XT-PIC PS/2 Mouse
> 14: 331764 XT-PIC ide0
> 15: 39468 XT-PIC ide1
> NMI: 0
> ERR: 0
>
> But /proc/interrupts shows only those irq's which are currently in use, is
> there any way to show usage of currenlty unused interrupts?
cat /proc/stat, see the `intr' line, each field is an increasing
interrupt value.
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next prev parent reply other threads:[~2001-09-15 17:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0109140838040.21992-100000@sjoerd.sjoerdnet>
2001-09-14 15:04 ` Feedback on preemptible kernel patch Robert Love
2001-09-15 9:44 ` Arjan Filius
2001-09-15 10:38 ` Erik Mouw
2001-09-15 17:57 ` Robert Love [this message]
2001-09-15 19:18 Robert Love
2001-09-16 1:28 ` Daniel Phillips
2001-09-16 1:54 ` Daniel Phillips
[not found] <200109140302.f8E32LG13400@zero.tech9.net>
2001-09-14 4:35 ` Robert Love
2001-09-15 4:25 ` Dieter Nützel
[not found] ` <200109150444.f8F4iEG19063@zero.tech9.net>
2001-09-15 5:14 ` Robert Love
2001-09-18 4:06 ` Dieter Nützel
2001-09-18 8:35 ` Daniel Phillips
2001-09-18 18:18 ` Roger Larsson
2001-09-18 23:31 ` Robert Love
2001-09-20 6:40 ` Dieter Nützel
[not found] ` <200109180406.f8I46LG02238@zero.tech9.net>
2001-09-18 23:31 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-09-14 2:47 Dieter Nützel
2001-09-11 22:53 Robert Love
2001-09-08 5:22 grue
2001-09-08 5:47 ` Robert Love
2001-09-08 17:33 ` Arjan Filius
2001-09-08 18:22 ` safemode
2001-09-09 4:40 ` Robert Love
2001-09-09 17:09 ` Robert Love
2001-09-09 21:07 ` Arjan Filius
2001-09-09 21:26 ` Robert Love
2001-09-09 21:23 ` Arjan Filius
2001-09-09 21:37 ` Robert Love
2001-09-10 3:24 ` Daniel Phillips
2001-09-10 3:37 ` Jeremy Zawodny
2001-09-10 5:09 ` Robert Love
2001-09-10 18:25 ` Daniel Phillips
2001-09-10 21:29 ` Arjan Filius
2001-09-13 17:27 ` Robert Love
2001-09-14 7:30 ` george anzinger
2001-09-14 15:01 ` Robert Love
2001-09-11 19:47 ` Arjan Filius
2001-09-09 18:57 ` grue
2001-09-09 21:44 ` Robert Love
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=1000576671.32708.23.camel@phantasy \
--to=rml@tech9.net \
--cc=iafilius@xs4all.nl \
--cc=linux-kernel@vger.kernel.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