From: Bamvor Jian Zhang <bjzhang@suse.com>
To: xen-devel@lists.xen.org
Cc: tim@xen.org, stefano.stabellini@citrix.com,
ian.campbell@citrix.com, Bamvor Jian Zhang <bjzhang@suse.com>
Subject: [PATCH 1/2] xen: arm: enable 32bit kernel stack trace
Date: Mon, 4 Nov 2013 16:01:25 +0800 [thread overview]
Message-ID: <1383552086-19858-2-git-send-email-bjzhang@suse.com> (raw)
In-Reply-To: <1383552086-19858-1-git-send-email-bjzhang@suse.com>
Signed-off-by: Bamvor Jian Zhang <bjzhang@suse.com>
---
xen/arch/arm/traps.c | 22 +++++++++++++++-------
1 file changed, 15 insertions(+), 7 deletions(-)
diff --git a/xen/arch/arm/traps.c b/xen/arch/arm/traps.c
index 4c0fc32..70623ee 100644
--- a/xen/arch/arm/traps.c
+++ b/xen/arch/arm/traps.c
@@ -628,13 +628,21 @@ static void show_guest_stack(struct vcpu *v, struct cpu_user_regs *regs)
printk("No stack trace for guest user-mode\n");
return;
- case PSR_MODE_FIQ:
- case PSR_MODE_IRQ:
- case PSR_MODE_SVC:
- case PSR_MODE_ABT:
- case PSR_MODE_UND:
- printk("No stack trace for 32-bit guest kernel-mode\n");
- return;
+ case PSR_MODE_FIQ:
+ sp = regs->sp_fiq;
+ break;
+ case PSR_MODE_IRQ:
+ sp = regs->sp_irq;
+ break;
+ case PSR_MODE_SVC:
+ sp = regs->sp_svc;
+ break;
+ case PSR_MODE_ABT:
+ sp = regs->sp_abt;
+ break;
+ case PSR_MODE_UND:
+ sp = regs->sp_und;
+ break;
#ifdef CONFIG_ARM_64
case PSR_MODE_EL1t:
--
1.8.1.4
next prev parent reply other threads:[~2013-11-04 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 8:01 [PATCH 0/2] xen: arm: improve xen arm support Bamvor Jian Zhang
2013-11-04 8:01 ` Bamvor Jian Zhang [this message]
2013-11-04 17:50 ` [PATCH 1/2] xen: arm: enable 32bit kernel stack trace Ian Campbell
2013-11-05 2:21 ` Bamvor Jian Zhang
2013-11-04 8:01 ` [PATCH 2/2] xen: arm: add default kernel_start in xenctx Bamvor Jian Zhang
2013-11-04 17:50 ` 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=1383552086-19858-2-git-send-email-bjzhang@suse.com \
--to=bjzhang@suse.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@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).