On Thu, 2013-06-20 at 18:28 +0800, Tiejun Chen wrote:
> Currently we need to skip this for supporting KGDB.

Does it need to depend on CONFIG_KGDB?  Either you've fixed the "can't
quite save properly" part, or you haven't.

-Scott

> 
> Signed-off-by: Tiejun Chen <tiejun.c...@windriver.com>
> ---
>  arch/powerpc/kernel/exceptions-64e.S |    4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/powerpc/kernel/exceptions-64e.S 
> b/arch/powerpc/kernel/exceptions-64e.S
> index 07cf657..a286b51 100644
> --- a/arch/powerpc/kernel/exceptions-64e.S
> +++ b/arch/powerpc/kernel/exceptions-64e.S
> @@ -639,11 +639,13 @@ kernel_dbg_exc:
>       rfdi
>  
>       /* Normal debug exception */
> +1:   andi.   r14,r11,MSR_PR;         /* check for userspace again */
> +#ifndef CONFIG_KGDB
>       /* XXX We only handle coming from userspace for now since we can't
>        *     quite save properly an interrupted kernel state yet
>        */
> -1:   andi.   r14,r11,MSR_PR;         /* check for userspace again */
>       beq     kernel_dbg_exc;         /* if from kernel mode */
> +#endif
>  
>       /* Now we mash up things to make it look like we are coming on a
>        * normal exception



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

Reply via email to