Re: [v5][PATCH 6/6] book3e/kgdb: Fix a single stgep case of lazyIRQ

["âtiejun.chenâ"]

On 10/19/2013 07:32 AM, Scott Wood wrote:
> On Thu, 2013-06-20 at 18:28 +0800, Tiejun Chen wrote:
> > When we're in kgdb_singlestep(), we have to work around to get
> > thread_info by copying from the kernel stack before calling
> > kgdb_handle_exception(), then copying it back afterwards.
> >
> > But for PPC64, we have a lazy interrupt implementation. So after
> > copying thread info frome kernle stack, if we need to replay an
> > interrupt, we shouldn't restore that previous backup thread info
> > to make sure we can replay an interrupt lately with a proper
> > thread info.
>
> Explain why copying it would be a problem.

This would be gone away in next version as well :)

Thanks,

Tiejun

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/