News for hackers. Stuff that matters.
Re:Bringing Call Gates Back by dfox on Wednesday August 09, 2017 @01:15PM (#14971384)
The fact that call gates does not disable interrupts is usually the desired behavior. Linux (and NT for 32 bit code) does not use call gates because they are not that useful for OSes that target the Unix/C flat memory model. You can probably use call gates to implement particularly fast IPC mechanism with semantics similar to QNX's message passing. But probably only real users of call gates are DOS extenders and 32 bit windows for 32/16b thunking (which is to large extent the same use case of mixing 32/16b code in single process).
Re:Bringing Call Gates Back by yuhong on Saturday August 19, 2017 @12:56AM (#15051758)
And yes, older Unixes also often used call gates too, for example Solaris.
Re:Bringing Call Gates Back by yuhong on Wednesday August 09, 2017 @04:09PM (#14973098)
When SYSCALL added EFLAGS masking, SWAPGS was also created with the assumption that it would be always done when going between kernel and user mode and before enabling interrupts.