A process in ready state is ready to receive interrupts

A process in ready state is ready to be scheduled

It is not maintained in the data structures by kernel, it is only for conceptual understanding of programmers

A process can self-terminate only when it's running

Processes in the ready queue are in the ready state

A process waiting for I/O completion is typically woken up by the particular interrupt handler code

A process that is running is not on the ready queue

A process changes from running to ready state on a timer interrupt or any I/O wait

A process waiting for any condition is woken up by another process only

A process changes from running to ready state on a timer interrupt

A running process may terminate, or go to wait or become ready again

A waiting process starts running after the wait is over

Changing from running state to waiting state results in "giving up the CPU"

Typically, it's represented as a number in the PCB

User process can update it's own page table entries

Page table is accessed by the MMU as part of execution of an instruction

An invalid entry on a page means, it was an illegal memory reference

User process can update it's own PTBR

The PTBR is loaded by the OS

An invalid entry on a page means, either it was illegal memory reference or the page was not present in memory.

OS creates the page table for every process

Page table is accessed by the OS as part of execuation of an instruction

expressions

#directives

global variables

typedefs

local variable declaration

pointer dereference

function calls