xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Bamvor Jian Zhang <bjzhang@suse.com>
Cc: julien.grall@citrix.com, andre.przywara@calxeda.com,
	xen-devel@lists.xen.org, Stefano.Stabellini@eu.citrix.com
Subject: Re: two questions about xen on arm
Date: Fri, 1 Nov 2013 09:29:34 +0000	[thread overview]
Message-ID: <1383298174.672.10.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <5273CEA10200003000070924@soto.provo.novell.com>

On Fri, 2013-11-01 at 01:54 -0600, Bamvor Jian Zhang wrote:
> fix destination. 
> sorry, i sent it to the wrong address. 
> 
>  >>>Bamvor Jian Zhang wrote: 
> > hi, 
> >   
> > recently, i got xen running on allwinner A20 successful[1], and i 
> > have two questions: 
> >  
> > 1, how to get guest stack trace? 
> > i could get the guest stack trace with the following patch, is it 
> > make sense?

The only issue would be that it prints 8-byte words for a 32-on-64
guest. That as it is much better than nothing, we can live with it for
sure.

>  and i could only get the dom0 kernel trace, how could 
> > i get the domU kernel trace?  

This code should work equally well for any guest AFAICT, what issue are
you seeing?

> >   
> >  #ifdef CONFIG_ARM_64 
> >      case PSR_MODE_EL1t: 
> >  
> > 2, xen kernel config 
> > i am confuse about what does "CONFIG XEN" mean. it  will check the kernel  
> > features for dom0 and domU kernel(mix XEN_BANDEND and XXX_FRONTEND) 
> > should we define XEN_DOM0 and XEN_DOMU configs respectively?  

I'm not sure what you mean, but yes, if you want to run Xen you should
enable the relevant CONFIG options, including CONFIG_XEN and I think
CONFIG_XEN_DOM0.

Ian.

  reply	other threads:[~2013-11-01  9:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01  7:54 two questions about xen on arm Bamvor Jian Zhang
2013-11-01  9:29 ` Ian Campbell [this message]
2013-11-01 10:34   ` Bamvor Jian Zhang
2013-11-01 10:41     ` Ian Campbell
2013-11-01 11:38       ` Bamvor Jian Zhang
2013-11-01 11:46         ` Ian Campbell
2013-11-06 18:52           ` Stefano Stabellini
2013-11-07  8:29             ` Ian Campbell
2013-11-07 10:48               ` Stefano Stabellini
2013-11-07 11:51                 ` 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=1383298174.672.10.camel@kazak.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=andre.przywara@calxeda.com \
    --cc=bjzhang@suse.com \
    --cc=julien.grall@citrix.com \
    --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).