From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Josh Zhao <joshsystem@gmail.com>,
stefano.stabellini@eu.citrix.com, tim@xen.org,
xen-devel@lists.xen.org
Subject: Re: [PATCH RFC 8/8] xen/arm: Some early trap logging
Date: Fri, 13 Sep 2013 14:26:47 +0100 [thread overview]
Message-ID: <52331297.8010800@linaro.org> (raw)
In-Reply-To: <1378822705-19310-8-git-send-email-ian.campbell@citrix.com>
On 09/10/2013 03:18 PM, Ian Campbell wrote:
> Not for really for application, might be useful to someone?
I think it could be useful for early debugging on new platform or until
init_traps initialized the correct handlers.
Can you update this patch with more information about the trap (reset,
undefined, ...)?
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> ---
> xen/arch/arm/arm32/head.S | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/xen/arch/arm/arm32/head.S b/xen/arch/arm/arm32/head.S
> index 79e95b6..06d53ad 100644
> --- a/xen/arch/arm/arm32/head.S
> +++ b/xen/arch/arm/arm32/head.S
> @@ -366,6 +366,9 @@ paging:
> bne 1b
>
> launch:
> + adr r0, early_trap_vector
> + mcr CP32(r0, VBAR_EL2)
> +
> ldr r0, =init_stack /* Find the boot-time stack */
> ldr sp, [r0]
> add sp, #STACK_SIZE /* (which grows down from the top). */
> @@ -376,12 +379,24 @@ launch:
> beq start_xen /* and disappear into the land of C */
> b start_secondary /* (to the appropriate entry point) */
>
> +trap_early:
> + PRINT("\r\nEARLY TRAP\r\n")
> /* Fail-stop
> * r0: string explaining why */
> fail: PRINT("- Boot failed -\r\n")
> 1: wfe
> b 1b
>
> + .align 5
> +early_trap_vector:
> + .word 0 /* 0x00 - Reset */
> + b trap_early /* 0x04 - Undefined Instruction */
> + b trap_early /* 0x08 - Supervisor Call */
> + b trap_early /* 0x0c - Prefetch Abort */
> + b trap_early /* 0x10 - Data Abort */
> + b trap_early /* 0x14 - Hypervisor */
> + b trap_early /* 0x18 - IRQ */
> + b trap_early /* 0x1c - FIQ */
>
> #ifdef EARLY_PRINTK
> /* Bring up the UART.
>
--
Julien Grall
next prev parent reply other threads:[~2013-09-13 13:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 14:18 [PATCH RFC 0/8] xen/arm: very initial cubieboard2 support Ian Campbell
2013-09-10 14:18 ` [PATCH RFC 1/8] xen/arm: Implement ioremap Ian Campbell
2013-09-10 15:03 ` Julien Grall
2013-09-10 15:14 ` Ian Campbell
2013-09-10 15:20 ` Julien Grall
2013-09-10 14:18 ` [PATCH RFC 2/8] xen/arm: implement read[bl] and write[bl] Ian Campbell
2013-09-10 15:00 ` Julien Grall
2013-09-10 15:09 ` Ian Campbell
2013-09-10 15:12 ` Julien Grall
2013-09-10 15:15 ` Ian Campbell
2013-09-10 14:18 ` [PATCH RFC 3/8] ns16550: make usable on ARM Ian Campbell
2013-09-10 14:36 ` Keir Fraser
2013-09-10 14:45 ` Ian Campbell
2013-09-10 15:00 ` Jan Beulich
2013-09-10 15:11 ` Ian Campbell
2013-09-10 15:18 ` Jan Beulich
2013-09-10 15:21 ` Ian Campbell
2013-09-10 14:18 ` [PATCH RFC 4/8] ns16550: support DesignWare 8250 Ian Campbell
2013-09-10 14:36 ` Keir Fraser
2013-09-10 15:02 ` Jan Beulich
2013-09-10 15:12 ` Ian Campbell
2013-09-10 15:19 ` Jan Beulich
2013-09-10 15:21 ` Ian Campbell
2013-09-10 15:28 ` Jan Beulich
2013-09-10 15:30 ` Ian Campbell
2013-09-10 14:18 ` [PATCH RFC 5/8] xen/arm: Support Cortex-A7 GIC Ian Campbell
2013-09-10 14:18 ` [PATCH RFC 6/8] xen/arm: Basic support for sunxi/sun7i platform Ian Campbell
2013-09-10 14:18 ` [PATCH RFC 7/8] xen/arm: Blacklist some sun7i UARTs Ian Campbell
2013-09-10 14:18 ` [PATCH RFC 8/8] xen/arm: Some early trap logging Ian Campbell
2013-09-13 13:26 ` Julien Grall [this message]
2013-09-13 13:35 ` Ian Campbell
2013-09-13 13:44 ` Julien Grall
2013-09-11 2:05 ` [PATCH RFC 0/8] xen/arm: very initial cubieboard2 support Josh Zhao
2013-09-11 10:15 ` 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=52331297.8010800@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=joshsystem@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).