Re: [Kgdb-bugreport] [PATCH] Fix singlestep exception kernel-user x86_64 and ia32

2007-05-16 Thread Amit S. Kale
Jason, This check atomic_read(cpu_doing_single_step) != -1 may result in a loss of debug events on other cpus Changing it to atomic_read(cpu_doing_single_step) == raw_smp_processor_id() corrects that problem I see that you've checked in this change. Would you mind waiting for 24 hours after

Re: [Kgdb-bugreport] [PATCH] Fix singlestep exception kernel-user x86_64 and ia32

2007-05-16 Thread Wessel, Jason
-Original Message- From: Amit S. Kale [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 16, 2007 4:19 AM To: Wessel, Jason Cc: kgdb-bugreport@lists.sourceforge.net; Sergei Shtylyov; Tom Rini Subject: Re: [PATCH] Fix singlestep exception kernel-user x86_64 and ia32 Jason,

[Kgdb-bugreport] [PATCH] Further fix to single step user-kernel

2007-05-16 Thread Jason Wessel
I solved the GPF problem I mentioned in an earlier e-mail (see the information below the first patch). The patch below is needed so the single step exception bits are cleared. It was easiest to use the predefined handler exception routine to do the work of executing the continue if the KGDB