Re: [patch V2 03/29] x86/irq/64: Remove a hardcoded irq_stack_union access

2019-04-05 Thread Thomas Gleixner
On Fri, 5 Apr 2019, Josh Poimboeuf wrote: > On Fri, Apr 05, 2019 at 09:37:27AM -0700, Sean Christopherson wrote: > > On Fri, Apr 05, 2019 at 05:07:01PM +0200, Thomas Gleixner wrote: > > > - irq_stack_top = (u64)this_cpu_ptr(irq_stack_union.irq_stack) + > > > - STACK_TOP_MARGIN; > >

Re: [patch V2 03/29] x86/irq/64: Remove a hardcoded irq_stack_union access

2019-04-05 Thread Josh Poimboeuf
On Fri, Apr 05, 2019 at 09:37:27AM -0700, Sean Christopherson wrote: > On Fri, Apr 05, 2019 at 05:07:01PM +0200, Thomas Gleixner wrote: > > From: Andy Lutomirski > > > > stack_overflow_check() is using both irq_stack_ptr and irq_stack_union to > > find the IRQ stack. That's going to break when vm

Re: [patch V2 03/29] x86/irq/64: Remove a hardcoded irq_stack_union access

2019-04-05 Thread Sean Christopherson
On Fri, Apr 05, 2019 at 09:37:27AM -0700, Sean Christopherson wrote: > On Fri, Apr 05, 2019 at 05:07:01PM +0200, Thomas Gleixner wrote: > > From: Andy Lutomirski > > > > stack_overflow_check() is using both irq_stack_ptr and irq_stack_union to > > find the IRQ stack. That's going to break when vm

Re: [patch V2 03/29] x86/irq/64: Remove a hardcoded irq_stack_union access

2019-04-05 Thread Sean Christopherson
On Fri, Apr 05, 2019 at 05:07:01PM +0200, Thomas Gleixner wrote: > From: Andy Lutomirski > > stack_overflow_check() is using both irq_stack_ptr and irq_stack_union to > find the IRQ stack. That's going to break when vmapped irq stacks are > introduced. > > Change it to just use irq_stack_ptr. >