Home › Forums › Linux Support › Linux Kernel ›

Query about "Function call interrupts" entry in /proc/interrupts file

Dec 02, 2009  By cyclops.xmen
 in

Hi all,

In the /proc/interrupts file, there is one entry called the Function
call interrupts.
Can anyone please explain to me how this interrupt is generated or
what it does?
Thanks!

$ cat /proc/interrupts

CPU0 CPU1
0: 7555 0 IO-APIC-edge timer
1: 2 0 IO-APIC-edge i8042
4: 2 0 IO-APIC-edge
6: 5 0 IO-APIC-edge floppy
7: 0 0 IO-APIC-edge parport0
8: 1 0 IO-APIC-edge rtc0
9: 0 0 IO-APIC-fasteoi acpi
12: 4 0 IO-APIC-edge i8042
14: 5184503 0 IO-APIC-edge ata_piix
15: 0 0 IO-APIC-edge ata_piix
16: 10030496 0 IO-APIC-fasteoi ohci1394, HDA Intel
17: 33961000 0 IO-APIC-fasteoi eth0
18: 0 0 IO-APIC-fasteoi uhci_hcd:usb4
21: 2710967 0 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2
22: 0 0 IO-APIC-fasteoi uhci_hcd:usb3
23: 0 0 IO-APIC-fasteoi uhci_hcd:usb5
2299: 2594538 0 PCI-MSI-edge ahci
NMI: 0 0 Non-maskable interrupts
LOC: 175008553 173744798 Local timer interrupts
RES: 1503295 3085980 Rescheduling interrupts
CAL: 1361 2486 Function call interrupts
TLB: 546223 608398 TLB shootdowns
SPU: 0 0 Spurious interrupts
ERR: 0
MIS: 0

‹ Change in GRUB menu.lst does not take effect mmap'd physical memory not updating user virtual ›
Webcast
More Resources
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers

Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.

Learn More

Sponsored by AMD

White Paper
More Resources
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions