On Thu, Jul 23, 2015 at 3:37 PM, Andy Lutomirski wrote:
> int3 uses IST and the paranoid gsbase path. Neither is necessary,
> although the IST stack may currently be necessary to avoid stack
> overruns.
>
> Clean up IRQ stacks, make them NMI safe, teach idtentry to use
> irqstacks if requested,
int3 uses IST and the paranoid gsbase path. Neither is necessary,
although the IST stack may currently be necessary to avoid stack
overruns.
Clean up IRQ stacks, make them NMI safe, teach idtentry to use
irqstacks if requested, and move int3 to the IRQ stack.
This prepares us to return from
On Thu, Jul 23, 2015 at 3:37 PM, Andy Lutomirski l...@kernel.org wrote:
int3 uses IST and the paranoid gsbase path. Neither is necessary,
although the IST stack may currently be necessary to avoid stack
overruns.
Clean up IRQ stacks, make them NMI safe, teach idtentry to use
irqstacks if
int3 uses IST and the paranoid gsbase path. Neither is necessary,
although the IST stack may currently be necessary to avoid stack
overruns.
Clean up IRQ stacks, make them NMI safe, teach idtentry to use
irqstacks if requested, and move int3 to the IRQ stack.
This prepares us to return from
4 matches
Mail list logo