Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I know all the general registers are pushed on the stack when the an interrupts happen, but I can’t see any code that flag register are save. The assembly instruction like setl which depends on the flag register, is easy to make a wrong result when restoring from an interrupt, if the flag register is corrupted.
Yes, the
(e/r)flagsregister needs to be saved across context switches like that.All interrupts (hardware and software, including exceptions) save it automatically on the stack and the
iretinstruction at the end of the ISR restores it.System calls use the same or similar mechanism and preserve the register.
Scheduling is triggered by interrupts or system calls. So, everything’s covered.