Re: Feedback on preemptible kernel patch

Robert Love (rml@tech9.net)
15 Sep 2001 13:57:44 -0400


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

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/