Re: [PATCH] Sometimes, there is OOPS happened when we use oprofile.

2012-10-31 Thread Robert Richter
On 31.10.12 14:33:17, H. Peter Anvin wrote: > I'm vaguely concerned about the following: > > + * To always return a non-null > + * stack pointer we fall back to regs as stack if no previous stack > + * exists. > > The logic being that if there is no stack pointer and the stack is > too empty, to

Re: [PATCH] Sometimes, there is OOPS happened when we use oprofile.

2012-10-31 Thread H. Peter Anvin
On 10/31/2012 02:05 PM, Robert Richter wrote: Jun, On 29.10.12 02:33:54, Zhang, Jun wrote: Sometimes, there is OOPS happened when we use oprofile. next is the call stack. From call stack, we find in call_on_stack if there is a nmi interrupt between "xchgl %%ebx,%%esp" and "call *%%edi", system

Re: [PATCH] Sometimes, there is OOPS happened when we use oprofile.

2012-10-31 Thread H. Peter Anvin
On 10/31/2012 02:05 PM, Robert Richter wrote: Jun, On 29.10.12 02:33:54, Zhang, Jun wrote: Sometimes, there is OOPS happened when we use oprofile. next is the call stack. From call stack, we find in call_on_stack if there is a nmi interrupt between "xchgl %%ebx,%%esp" and "call *%%edi", system

Re: [PATCH] Sometimes, there is OOPS happened when we use oprofile.

2012-10-31 Thread Robert Richter
Jun, On 29.10.12 02:33:54, Zhang, Jun wrote: > Sometimes, there is OOPS happened when we use oprofile. next > is the call stack. From call stack, we find in > call_on_stack if there is a nmi interrupt between "xchgl > %%ebx,%%esp" and "call *%%edi", system will OOPS. this should be related and fi