Displaying 2 results from an estimated 2 matches for "iret16".
2007 Apr 18
1
[PATCH 1/2] Transparent entry.S IRQ holdoff handling
...very tricky code changes that would otherwise be required. CLI/STI/IRET
may all assume a 32 bit flat stack for writing to data areas.
STI_SYSEXIT is macroized together because it implicitly relies on the interrupt
holdoff property of STI.
The IRET from a 16-bit stack must be marked explicitly as IRET16, because at
this point there are no flat data segments loaded. It is expected that the
IRET translation for a hypervisor will need to access a virtual interrupt flag
in memory, requiring either a flat stack segment or knowledge of non-flatness
so it can load a temporary selector to use.
Signed-of...
2007 Apr 18
1
[PATCH 1/2] Transparent entry.S IRQ holdoff handling
...very tricky code changes that would otherwise be required. CLI/STI/IRET
may all assume a 32 bit flat stack for writing to data areas.
STI_SYSEXIT is macroized together because it implicitly relies on the interrupt
holdoff property of STI.
The IRET from a 16-bit stack must be marked explicitly as IRET16, because at
this point there are no flat data segments loaded. It is expected that the
IRET translation for a hypervisor will need to access a virtual interrupt flag
in memory, requiring either a flat stack segment or knowledge of non-flatness
so it can load a temporary selector to use.
Signed-of...