Methods of Device Interaction (OS ↔ I/O Devices)

🔷 Core Problem

👉 How does the operating system communicate with hardware devices?

• How does OS send commands?

• How does it read device status or data?

---

1. Two Primary Methods

There are two fundamental approaches used in modern systems:

---

1. Explicit I/O Instructions

🔷 Concept

• Special machine instructions are used to communicate with devices

• These instructions directly access device registers

---

🔷 How It Works

• CPU executes specific I/O instructions:

  • Read from device → input instruction

  • Write to device → output instruction

📌 Example (x86 architecture):

• in → read from device

• out → write to device

---

🔷 Mechanism

1. OS places:

   • Data in CPU register

   • Device identifier (port number)

2. Executes instruction (e.g., out)

3. Hardware routes operation to:

   • Device register instead of memory

---

🔷 Key Characteristics

• Uses separate address space (I/O ports)

• Requires special instructions

• Device identified via port numbers

---

🔒 Privilege Requirement

👉 These instructions are privileged

• Only OS (kernel mode) can execute them

• Prevents user programs from:

  • Direct disk access

  • Corrupting system

---

⚠️ Why Privileged?

If not restricted:

• Any program could overwrite disk

• System security and stability collapse

---

2. Memory-Mapped I/O (MMIO)

🔷 Concept

• Device registers are treated as normal memory addresses

👉 No special instructions needed!

---

🔷 How It Works

• OS uses regular memory operations:

  • load → read device register

  • store → write device register

---

🔷 Mechanism

1. Device registers mapped into physical memory space

2. OS accesses them like normal memory:

   *device_register = value;   // write
   value = *device_register;   // read
   

3. Hardware detects:

   • Address belongs to device

   • Redirects request to device instead of RAM

---

🔷 Key Characteristics

• Uses same address space as memory

• No special instructions required

• Simpler programming model

---

3. Comparison of the Two Methods

Feature	Explicit I/O Instructions	Memory-Mapped I/O
Instructions	Special (in, out)	Normal load/store
Address space	Separate (I/O ports)	Shared with memory
Complexity	Slightly higher	Simpler
Flexibility	Less flexible	More flexible
Usage	Traditional systems	Widely used today

---

4. Key Insight

👉 Both methods achieve the same goal:

• Read/write device registers

Difference is only how access is performed:

• Special instructions vs normal memory operations

---

5. Important Observations

🔹 No Clear Winner

• Both approaches are still used

• Choice depends on:

  • Architecture design

  • Hardware simplicity

  • Performance considerations

---

🔹 OS Control is Critical

• OS acts as mediator

• Prevents unsafe direct hardware access

---

6. Conceptual Flow of Interaction

Regardless of method:

1. OS writes to command register

2. OS writes/reads data register

3. OS checks status register

4. Device performs operation

7. Summary

• Two methods to interact with I/O devices:

  1. Explicit I/O instructions

  2. Memory-mapped I/O

• Both allow OS to access device registers

• Explicit method uses special instructions

• MMIO uses normal memory operations

• Access is privileged to ensure system protection