All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: julien.grall@linaro.org, tim@xen.org, jintack@cs.columbia.edu,
	stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v2] xen: arm64: more useful logging on bad trap.
Date: Wed, 18 Feb 2015 17:26:33 +0000	[thread overview]
Message-ID: <54E4CB49.1020209@citrix.com> (raw)
In-Reply-To: <1424278915-6468-1-git-send-email-ian.campbell@citrix.com>

On 18/02/15 17:01, Ian Campbell wrote:
> Dump the register state before panicing so we have some clue where the
> issue occurred. Also decode the ESR register a bit to save having to
> grab a pen and paper.
>
> ESR_EL2 is a 32-bit register, so use SYSREG_READ32 not ..._READ64, as
> we already do correctly in the main trap handler.
>
> While here notice that do_trap_serror is never called and remove it.
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> Reviewed-by: Julien Grall <julien.grall@linaro.org>
> Tested-by: Jintack Lim <jintack@cs.columbia.edu>
> Cc: jintack@cs.columbia.edu
> ---
> Jintack, since you have a system which is exhibiting SError issues I
> wonder if I could prevail on you to give this patch a try on your
> system and report on the output. I've only compile tested this myself.
>
> v2: Added blank line after variable declaration
>     Split log message into two lines.
>     s/code/ESR/ and reformat a little.
> ---
>  xen/arch/arm/arm64/traps.c |   14 ++++++--------
>  1 file changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/xen/arch/arm/arm64/traps.c b/xen/arch/arm/arm64/traps.c
> index 1693b5d..31a3ca5 100644
> --- a/xen/arch/arm/arm64/traps.c
> +++ b/xen/arch/arm/arm64/traps.c
> @@ -24,11 +24,6 @@
>  
>  #include <public/xen.h>
>  
> -asmlinkage void do_trap_serror(struct cpu_user_regs *regs)
> -{
> -    panic("Unhandled serror trap");
> -}
> -
>  static const char *handler[]= {
>          "Synchronous Abort",
>          "IRQ",
> @@ -38,11 +33,14 @@ static const char *handler[]= {
>  
>  asmlinkage void do_bad_mode(struct cpu_user_regs *regs, int reason)
>  {
> -    uint64_t esr = READ_SYSREG64(ESR_EL2);
> -    printk("Bad mode in %s handler detected, code 0x%08"PRIx64"\n",
> -           handler[reason], esr);
> +    union hsr hsr = { .bits = READ_SYSREG32(ESR_EL2) };
> +
> +    printk("Bad mode in %s handler detected", handler[reason]);
> +    printk("ESR=0x%08"PRIx32":  EC=%"PRIx32", IL=%"PRIx32", ISS=%"PRIx32"\n",
> +           hsr.bits, hsr.ec, hsr.len, hsr.iss);

This would be better as a single printk() call, otherwise a different
cpu issuing a printk() could interleave in the middle of the line.

Also, you appear to have dropped the space between "detected" and "ESR"

~Andrew

  reply	other threads:[~2015-02-18 17:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 17:01 [PATCH v2] xen: arm64: more useful logging on bad trap Ian Campbell
2015-02-18 17:26 ` Andrew Cooper [this message]
2015-02-19  8:45   ` Ian Campbell
2015-02-19 10:17     ` Andrew Cooper
2015-02-19 10:22       ` Ian Campbell
2015-02-19 17:20         ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54E4CB49.1020209@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=jintack@cs.columbia.edu \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.