xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Andrii Anisov <andrii.anisov@globallogic.com>
Cc: Tim Deegan <tim@xen.org>, Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Hypervisor compilation for arm without debug=y
Date: Tue, 20 Aug 2013 18:07:36 +0100	[thread overview]
Message-ID: <5213A258.8080205@linaro.org> (raw)
In-Reply-To: <5213A069.3020400@linaro.org>

On 08/20/2013 05:59 PM, Julien Grall wrote:
> On 08/20/2013 05:03 PM, Andrii Anisov wrote:
>> BTW,
>>
>>     > Is it a known issue?
>>
>>     I suspect none of us has ever really used a non-debug build!
>>
>>
>> Wiki says: 
>>
>>     Once you have a suitable cross compiler you can compile Xen with:
>>        $ make dist-xen XEN_TARGET_ARCH=arm32
>>     CROSS_COMPILE=arm-unknown-linux-gnueabi-
>>     or:
>>        $ make dist-xen XEN_TARGET_ARCH=arm64
>>     CROSS_COMPILE=aarch64-linux-gnu-
>>
>>
>> Without debug=y flag.
> 
> On unstable branch by default debug=y. On release branches have debug=n
> by default.
> 
> I have tried to boot a non-debug Xen on the Versatile Express:
>    gcc 4.8.1: Xen boots
>    gcc 4.6.3: Xen hangs with no output log (even early printk)

I was wrong, when debug=n it's not possible to have early printk. So Xen
only hangs.

But, if I enable early printk (by hacking xen/arch/arm/Rules.mk) Xen is
able to boot...


-- 
Julien Grall

  reply	other threads:[~2013-08-20 17:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 11:44 Hypervisor compilation for arm without debug=y Andrii Anisov
2013-08-19 15:11 ` Ian Campbell
2013-08-19 15:49   ` Andrii Anisov
2013-08-20 16:03     ` Andrii Anisov
2013-08-20 16:59       ` Julien Grall
2013-08-20 17:07         ` Julien Grall [this message]
2013-08-21 10:38           ` Andrii Anisov

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=5213A258.8080205@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=andrii.anisov@globallogic.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).