Bug#723180: [PATCH] Revert "x86: Disable IST stacks for debug/int 3/stack fault for PREEMPT_RT"

2014-01-06 Thread Sebastian Andrzej Siewior
* Andi Kleen | 2014-01-04 19:18:07 [+0100]: >On Fri, Jan 03, 2014 at 02:55:48PM +0100, Sebastian Andrzej Siewior wrote: >> where do I start. Let me explain what is going on here. The code >> sequence > >Yes the IST stacks are needed for correctness, even in more cases than >the example below. You

Bug#723180: [PATCH] Revert "x86: Disable IST stacks for debug/int 3/stack fault for PREEMPT_RT"

2014-01-05 Thread Andi Kleen
On Sun, Jan 05, 2014 at 05:45:47AM +0100, Mike Galbraith wrote: > On Sat, 2014-01-04 at 19:18 +0100, Andi Kleen wrote: > > On Fri, Jan 03, 2014 at 02:55:48PM +0100, Sebastian Andrzej Siewior wrote: > > > where do I start. Let me explain what is going on here. The code > > > sequence > > > > Yes t

Bug#723180: [PATCH] Revert "x86: Disable IST stacks for debug/int 3/stack fault for PREEMPT_RT"

2014-01-04 Thread Mike Galbraith
On Sat, 2014-01-04 at 19:18 +0100, Andi Kleen wrote: > On Fri, Jan 03, 2014 at 02:55:48PM +0100, Sebastian Andrzej Siewior wrote: > > where do I start. Let me explain what is going on here. The code > > sequence > > Yes the IST stacks are needed for correctness, even in more cases than > the exam

Bug#723180: [PATCH] Revert "x86: Disable IST stacks for debug/int 3/stack fault for PREEMPT_RT"

2014-01-04 Thread Andi Kleen
On Fri, Jan 03, 2014 at 02:55:48PM +0100, Sebastian Andrzej Siewior wrote: > where do I start. Let me explain what is going on here. The code > sequence Yes the IST stacks are needed for correctness, even in more cases than the example below. You cannot just disable them, just because you don't li

Bug#723180: [PATCH] Revert "x86: Disable IST stacks for debug/int 3/stack fault for PREEMPT_RT"

2014-01-03 Thread Sebastian Andrzej Siewior
where do I start. Let me explain what is going on here. The code sequence | pushf | pop%edx | or $0x1,%dh | push %edx | mov$0xe0,%eax | popf | sysenter triggers the bug. On 64bit kernel we see the double fault (with 32bit and 64bit userland) and on 32bit kernel there is no problem. T