Handling of Interrupts as Threads

  • Pedro Mejia-Alvarez
  • Luis Eduardo Leyva-del-Foyo
  • Arnoldo Diaz-Ramirez
Part of the SpringerBriefs in Computer Science book series (BRIEFSCOMPUTER)


An alternative to a two level interrupt handling scheme is interrupt handling in asynchronous concurrent activities (threads, tasks or processes). The general idea of this scheme is that the operating system kernel is responsible for placing a generic low-level interrupt handler, which activates an asynchronous activity (thread, task or process) to handle the interrupt. From this scheme two variants can be identified: interrupt signals as inter-process communication events (IPC), common in systems with microkernel architectures and interrupts as kernel threads, such as those in Solaris 2.0 [46] and Real-Time Linux [4].


  1. 46.
    J. Mauro, R. McDougall, Solaris Internals, Core Kernel Architecture (Sun Microsystems Press, 2001)Google Scholar
  2. 4.
    G. Anzinger y N. Gamble (MontaVista Software), Design of a Fully Preemptable Linux Kernel. Embedded Linux Journal (2000)Google Scholar
  3. 8.
    P. Brinch-Hansen, The nucleus of a multiprogramming system. Communication of the ACM 13(4), 238–241 and 250 (1970)CrossRefGoogle Scholar
  4. 9.
    P. Brinch-Hansen, Operating System Principles (Prentice Hall, New Delhi, 1973)zbMATHGoogle Scholar
  5. 3.
    M. Accetta, R. Baron, W. Bolosky, D. Golub, R. Rashid, A. Tevanian, M. Young, “Mach: A new kernel foundation for UNIX development”, 93–113, USENIX Association Conference Proceedings, USENIX Association, June 1986Google Scholar
  6. 5.
    F. Armand, I. Boule, M. Gien, M. Guillemont, F. Herrmann, C. Kaiser, S. Langlois, P. Leonard, and W. Neuhauser, Chorus distributed operating systems, M. Rozier, V. Abrossimov, 305–370, USENIX Computing Systems, 1, 4, Fall 1988Google Scholar
  7. 23.
    J.R. Eykholt, S.R. Kleiman, S. Barton, R. Faulkner, A. Shivalingiah, M. Smith, D. Stein, J. Voll, M. Weeks, D. Williams, Beyond multiprocessing: Multithreading the SunOs kernel, in Proceedings of the Summer 1992 USENIX Technical Conference, (1992)Google Scholar
  8. 34.
    S. Kleiman, J. Eykholt, Interrupts as threads. ACM SIGOPS Operating Systems Review 29(2), 21–26 (1995)CrossRefGoogle Scholar
  9. 55.
    R. Rajkumar, Synchronization in Real-Time Systems: A Priority Inheritance Approach (Kluwer Academic Publishers, 1991). 208 pp, ISBN 0-7923-9211-6Google Scholar
  10. 58.
    M. Saksena, Linux as a Real-Time Operating System (TymeSys White Paper, 2003)Google Scholar
  11. 20.
    S.-T. Dietrich, D. Walker, The evolution of real-time linux. 7th Real-Time Linux Workshop: The Evolution of Real-Time Linux 17 (2005)Google Scholar
  12. 28.
    A.C. Heursch, D. Grambow, D. Roedel, H. Rzehak, Time-critical tasks in Linux 2.6, concepts to increase the preemptablity of Linux kernel. Linux Automation Konferenz, University of Hannover, Germany, March 2004Google Scholar
  13. 78.
    J. Yang, Y. Chen, H. Wang, B. Wang, A linux kernel with fixed interrupt latency for embedded real-time system, in Proceedings of the Second International Conference on Embedded Software and Systems (ICESS’05), (2005)Google Scholar
  14. 27.
    A.C. Heursch, A. Horstkotte, H. Rzehak, Preemption concepts, Rhealstone Benchmark and scheduler analysis of Linux 2.4, on the Real-Time & Embedded Computing Conference, Milan, November 27–28, 2001Google Scholar
  15. 71.
    TimeSys Corporation, “A TimeSys Perspective on the Linux Preemptible Kernel”, 2003Google Scholar
  16. 79.
    Y.-C. Wang, K.-J. Lin, Some discussion on the low latency patch for linux, in Conf. Proc. of the Second Annual Real-Time Linux Workshop, Orlando, Florida, November 27–28, (Florida, 2000)Google Scholar

Copyright information

© The Author(s), under exclusive license to Springer Nature Switzerland AG 2018

Authors and Affiliations

  • Pedro Mejia-Alvarez
    • 1
  • Luis Eduardo Leyva-del-Foyo
    • 2
  • Arnoldo Diaz-Ramirez
    • 3
  1. 1.Departamento de ComputacionCINVESTAV-IPNMexico CityMexico
  2. 2.Universidad Autónoma MetropolitanaMexico CityMexico
  3. 3.Departamento de Sistemas y ComputaciónInstituto Tecnológico de MexicaliMexicaliMexico

Personalised recommendations