All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: tim@xen.org, jintack@cs.columbia.edu, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH] xen: arm64: more useful logging on bad trap.
Date: Wed, 18 Feb 2015 15:36:49 +0000	[thread overview]
Message-ID: <54E4B191.3040308@linaro.org> (raw)
In-Reply-To: <1424272771-25072-1-git-send-email-ian.campbell@citrix.com>

Hi Ian,

On 18/02/2015 15:19, Ian Campbell wrote:
> diff --git a/xen/arch/arm/arm64/traps.c b/xen/arch/arm/arm64/traps.c
> index 1693b5d..89b8eb3 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,13 @@ 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);

While you are modifying this function. Can you add a newline after the 
declarations?

Other than that:

Reviewed-by: Julien Grall <julien.grall@linaro.org>

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-02-18 15:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 15:19 [PATCH] xen: arm64: more useful logging on bad trap Ian Campbell
2015-02-18 15:36 ` Julien Grall [this message]
2015-02-18 15:47   ` Jintack Lim
2015-02-18 16:00     ` Julien Grall
2015-02-18 16:04       ` Ian Campbell
2015-02-18 16:29       ` Jintack Lim
2015-02-18 16:01     ` Ian Campbell
2015-02-18 16:30       ` Jintack Lim

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=54E4B191.3040308@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=jintack@cs.columbia.edu \
    --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.