Messages in this thread | | | Date | Wed, 23 Oct 2013 17:27:22 +0800 | From | "“tiejun.chen”" <> | Subject | Re: [v5][PATCH 3/6] book3e/kgdb: update thread's dbcr0 |
| |
On 10/19/2013 06:57 AM, Scott Wood wrote: > On Thu, 2013-06-20 at 18:28 +0800, Tiejun Chen wrote: >> gdb always need to generate a single step properly to invoke >> a kgdb state. But with lazy interrupt, book3e can't always >> trigger a debug exception with a single step since the current >> is blocked for handling those pending exception, then we miss >> that expected dbcr configuration at last to generate a debug >> exception. > > What do you mean by "the current is blocked"? Could you explain more > clearly what lazy EE has to do with MSR_DE and DBCR0? >
I will go another path to make sure the lazy EE doesn't affect KGDB, so please see next version.
Thanks,
Tiejun
| |