O'rnatilgan operatsion tizimlardagi

uzilishlar
Interruptions are a fundamental part of modern operating systems, allowing
devices and software tUzilishlar zamonaviy operatsion tizimlarning asosiy
qismi bo'lib, qurilmalar va dasturiy ta'minot bilan samarali muloqot qilish va
hodisalarga javob berish imkonini beradi. Ular periferik qurilmalar uchun
protsessorni o'zgarishlar yoki so'rovlar to'g'risida xabardor qilish usulini
taqdim etadi, bu esa tizimga ularni tezda hal qilish imkonini beradi.o efficiently
communicate and respond to events. They provide a way for peripheral
devices to notify the CPU of changes or requests, enabling the system to
handle them promptly.
Uzilishlar turlari
Uskuna uzilishlari
Bular protsessorga bo’ladigan
biror hodisa yoki so’rov
haqida haqida xabar berish
uchun klaviatura, sichqoncha
yoki tarmoq kartalari kabi
qurilmalar tomonidan ishlab
chiqarilgan signallardir.
Software Interrupts
These are generated by
software, such as system calls
or exceptions, to request
services from the operating
system or handle errors.
Timed Interrupts
These are generated by a
system timer to provide a
regular clock signal for
scheduling and time-keeping
tasks.
Interrupt Handling Mechanism
Interrupt Request 1
Qurilma protsessorga event
kerakligini bildiruvchi uzilish
bildiroshnomasinii yaratadi. 2 Interrupt Acknowledgment
The CPU pauses the current task,
saves its state, and acknowledges the
Interrupt Service Routine 3 interrupt request.
The CPU executes the appropriate
Interrupt Service Routine (ISR) to
handle the interrupt and address the
device's needs.
Interrupt Prioritization
1 Priority Levels 2 Preemption 3 Interrupt Masking
Interrupts are assigned A higher-priority The system can
different priority levels, interrupt can preempt selectively enable or
with higher-priority the current task, forcing disable interrupts to
interrupts taking the CPU to temporarily manage their priorities
precedence over lower- suspend its execution to and prevent race
priority ones. service the more urgent conditions.
interrupt.
Interrupt Service Routines (ISRs)
Efficiency
ISRs must be designed to be as efficient as
possible, minimizing the time spent in the
interrupt handler to avoid delaying other
tasks.
Reentrant Code
ISRs should be reentrant, allowing them to be
interrupted and resumed without corrupting
their state.
Shared Resources
ISRs must carefully manage shared resources,
such as data structures, to prevent race
conditions and ensure data integrity.
Atomicity
Critical sections within ISRs should be made
atomic to ensure that they are executed as a
single, uninterruptible operation.
Interrupt Latency and Response Time

Interrupt Latency
The time between the occurrence of an interrupt and the start of its servicing by the
CPU.

Interrupt Response Time

The time between the occurrence of an interrupt and the completion of its servicing
by the CPU.

Determinism
Real-time systems require deterministic interrupt latency and response time to
ensure predictable performance.
Interrupt-driven vs. Polled I/O
Interrupt-driven I/O
Devices generate interrupts to
notify the CPU of events,
allowing the system to
respond quickly and
efficiently.
Polled I/O
The CPU regularly checks the
status of devices, polling
them for changes, which can
be less efficient but simpler
to implement.
Trade-offs
Interrupt-driven I/O offers
better responsiveness, but
can introduce complexity and
potential issues, while polled
I/O is simpler but less
efficient.
Challenges and Considerations

Priority Interrupt Latency Race Conditions Performance

Management Impact
Carefully managing
Ensuring that high- Minimizing the time shared resources to Ensuring that the
priority interrupts are between the prevent race overhead of interrupt
serviced in a timely occurrence of an conditions and handling does not
manner while interrupt and the start ensure data integrity degrade overall
avoiding starvation of of its servicing to during interrupt system performance.
lower-priority tasks. meet real-time handling.
requirements.