Professor, let me ask you one more question.
Thank you for teaching me that the CPU scheduler was a process, not a program source code in the kernel.
I've learned that CPU scheduler is not a separate process at school.
Until now, I learned that CPU scheduler is a passive program source code in the kernel.
And I learned that each process is frequently caught in an interrupt, enters kernel mode, and executes CPU scheduler code in the kernel on its own at school.
I have a question here.
Even if user processes are frequently interrupted and enter kernel mode due to hardware signals,
I didn't write the source code for the user process to execute the CPU scheduler source code in the kernel.
By the way, how do processes execute the source code of the CPU scheduler in the kernel?
That's why I asked this question.
I knew the CPU scheduler was built into the kernel, but it wasn't a passive source code, it was a separate process.
At school, I learned that CPU scheduler is not a separate process, but a source code built into the kernel.
Thank you for teaching me that the CPU scheduler was a process, not a program source code in the kernel.
Then, When entering PS-ef instructions into the shell,
what are the PID and CMD of the CPU scheduler process?
