Re: [v3] booke/kprobe: Fix stack corrupt issue when kprobe 'stwu'

[v3 PATCH 1/1] booke/kprobe: make program exception to use one dedicated exception stack · Tiejun Chen <hidden> · 2011-07-11
[v3] booke/kprobe: Fix stack corrupt issue when kprobe 'stwu' · Tiejun Chen <hidden> · 2011-07-11
Re: [v3] booke/kprobe: Fix stack corrupt issue when kprobe 'stwu' · tiejun.chen <hidden> · 2011-07-14
Re: [v3 PATCH 1/1] booke/kprobe: make program exception to use one dedicated exception stack · tiejun.chen <hidden> · 2011-07-12
Re: [v3 PATCH 1/1] booke/kprobe: make program exception to use one dedicated exception stack · Kumar Gala <hidden> · 2011-07-14
Re: [v3 PATCH 1/1] booke/kprobe: make program exception to use one dedicated exception stack · Scott Wood <hidden> · 2011-07-14
Re: [v3 PATCH 1/1] booke/kprobe: make program exception to use one dedicated exception stack · tiejun.chen <hidden> · 2011-07-15
Re: [v3 PATCH 1/1] booke/kprobe: make program exception to use one dedicated exception stack · Scott Wood <hidden> · 2011-07-15
RE: [v3 PATCH 1/1] booke/kprobe: make program exception to use one dedicated exception stack · Chen, Tiejun <hidden> · 2011-07-16
Re: [v3 PATCH 1/1] booke/kprobe: make program exception to use one dedicated exception stack · Scott Wood <hidden> · 2011-07-18
Re: [v3 PATCH 1/1] booke/kprobe: make program exception to use one dedicated exception stack · tiejun.chen <hidden> · 2011-07-19
Re: [v3 PATCH 1/1] booke/kprobe: make program exception to use one dedicated exception stack · Benjamin Herrenschmidt <benh@kernel.crashing.org> · 2011-08-30
Re: [v3 PATCH 1/1] booke/kprobe: make program exception to use one dedicated exception stack · tiejun.chen <hidden> · 2011-08-31
Re: [v3 PATCH 1/1] booke/kprobe: make program exception to use one dedicated exception stack · Benjamin Herrenschmidt <benh@kernel.crashing.org> · 2011-08-31
Re: [v3 PATCH 1/1] booke/kprobe: make program exception to use one dedicated exception stack · tiejun.chen <hidden> · 2011-07-21

From: tiejun.chen <hidden>
Date: 2011-07-14 11:57:28

Tiejun Chen wrote:

v1 -> v2: when allocate pgirq_ctx, use 'hw_cpu' to identify cpu ID in exc_lvl_early_init().
v2 -> v3: add that specific return-from-program-exc to restore necessary thread info then
we can withdraw the original patch #2.

Any feedback?

Thanks
Tiejun

Tiejun
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help