• Navigation überspringen
  • Zur Navigation
  • Zum Seitenende
Organisationsmenü öffnen Organisationsmenü schließen
Friedrich-Alexander-Universität Lehrstuhl für Informatik 4 (Systemsoftware)
  • FAUZur zentralen FAU Website
  1. Friedrich-Alexander-Universität
  2. Technische Fakultät
  3. Department Informatik
Suche öffnen
  • English
  • Campo
  • StudOn
  • FAUdir
  • Stellenangebote
  • Lageplan
  • Hilfe im Notfall
  1. Friedrich-Alexander-Universität
  2. Technische Fakultät
  3. Department Informatik
Friedrich-Alexander-Universität Lehrstuhl für Informatik 4 (Systemsoftware)
Menu Menu schließen
  • Lehrstuhl
    • Team
    • Aktuelles
    • Kontakt und Anfahrt
    • Leitbild
    • 50-jähriges Jubiläum
    Portal Lehrstuhl
  • Forschung
    • Forschungsbereiche
      • Betriebssysteme
      • Confidential Computing
      • Embedded Systems Software
      • Verteilte Systeme
    • Projekte
      • AIMBOS
      • BALu
      • BFT2Chain
      • DOSS
      • Mirador
      • NEON
      • PAVE
      • ResPECT
      • Watwa
    • Projektkampagnen
      • maRE
    • Seminar
      • Systemsoftware
    Portal Forschung
  • Publikationen
  • Lehre
    • Sommersemester 2025
      • Applied Software Architecture
      • Ausgewählte Kapitel der Systemsoftware
      • Betriebssystemtechnik
      • Projekt angewandte Systemsoftwaretechnik
      • System-Level Programming
      • Systemnahe Programmierung in C
      • Systemprogrammierung 1
      • Verteilte Systeme
    • Wintersemester 2025/26
      • Systemprogrammierung 2
      • Betriebssysteme
      • Middleware – Cloud Computing
      • Echtzeitsysteme
      • Virtuelle Maschinen
      • Web-basierte Systeme
      • Projekt angewandte Systemsoftwaretechnik
      • Aktuelle Entwicklung in Verteilten und Objektorientierten Betriebssystemen (für Bachelor-/Masterarbeit)
    Portal Lehre
  • Examensarbeiten
  1. Startseite
  2. Extern

Extern

Bereichsnavigation: Lehre
  • Betriebssysteme
    • Vorlesung
      • Folien
    • Übung
      • Seminar
      • Aufgaben
      • Aufgabe 0: C++ Streams
        • Aufgabe 1: Ein-/Ausgabe
          • Aufgabe 2: Unterbrechungen
            • Aufgabe 3: Pro-/Epilog
              • Aufgabe 4: Kontextwechsel
                • Aufgabe 5: Zeitscheiben
                  • Assembler Crashkurs
                    • C++ Crashkurs
                      • Entwicklungsumgebung
                        • FAQ
                          • Ruhmeshalle

                        Aufgabe 5: Zeitscheiben

                        Public Member Functions | Friends | List of all members
                        Gate Class Referenceabstract
                        Interrupt Handling

                        Class of objects that are capable of handling interrupts. More...

                        #include <interrupt/gate.h>

                        + Inheritance diagram for Gate:
                        [legend]

                        Public Member Functions

                         Gate ()
                         Constructor.
                         
                        virtual ~Gate ()
                         Destructor. More...
                         
                        virtual bool prologue ()=0
                         Device-specific interrupt handling routine that is executed immediately after the interrupt occurs (asynchronously). More...
                         
                        virtual void epilogue ()
                         Possibly delayed, synchronously executed Device-specific interrupt handling routine. More...
                         

                        Friends

                        class GateQueue
                         

                        Detailed Description

                        Class of objects that are capable of handling interrupts.

                        All objects to be assigned in Plugbox must be derived from this class.

                        Each inheriting class must now define the virtual method Gate::prologue(). For the virtual method Gate::epilogue() an empty implementation can be specified in this parent class, so derived device classes do not necessarily have to define an Gate::epilogue() on their own.

                        Note
                        To be able to enqueue each class inheriting from Gate into the linked list(s) implemented by GateQueue this class has to contain a member acting as next pointer (for MPStuBS, each of the Core::MAX CPU cores will need its own pointer)

                        Constructor & Destructor Documentation

                        virtual Gate::~Gate ( )
                        inlinevirtual

                        Destructor.

                        Classes with virtual methods should always have a virtual destructor (which can be empty as well). In StuBS this will calm the compiler, on other systems this will guarantee that delete will free the memory for objects of the derived classes correctly.

                        Member Function Documentation

                        virtual bool Gate::prologue ( )
                        pure virtual

                        Device-specific interrupt handling routine that is executed immediately after the interrupt occurs (asynchronously).

                        Returns
                        true if the epilogue has to be executed.

                        Implemented in Assassin, Clock, Keyboard, Mouse, Panic, SerialStream, Ticker, and Watch.

                        virtual void Gate::epilogue ( )
                        inlinevirtual

                        Possibly delayed, synchronously executed Device-specific interrupt handling routine.

                        Reimplemented in Assassin, Clock, Keyboard, Mouse, SerialStream, Ticker, and Watch.


                        The documentation for this class was generated from the following file:
                        • interrupt/gate.h
                        Friedrich-Alexander-Universität
                        Erlangen-Nürnberg

                        Schlossplatz 4
                        91054 Erlangen
                        • Impressum
                        • Datenschutz
                        • Barrierefreiheit
                        • Facebook
                        • RSS Feed
                        • Xing
                        Nach oben