From: Julien Grall <julien.grall@arm.com>
To: Ivan Pavic <ivan.pavic2@fer.hr>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Jonathan Daugherty <jtd@galois.com>, Adam Wick <awick@galois.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: Basic bare metal ARM domain interface
Date: Thu, 2 Jun 2016 12:41:02 +0100 [thread overview]
Message-ID: <57501B4E.6040203@arm.com> (raw)
In-Reply-To: <20160601200648.GA4108@dumpram-Inspiron-3537>
On 01/06/16 21:06, Ivan Pavic wrote:
> On Tue, May 31, 2016 at 10:53:06AM +0100, Julien Grall wrote:
> Hello Julien,
Hello Ivan,
> thank you very much, I succeded with debug console and pin toggle (iomem).
> It's actually good that you answered late, because it made me look through xen
> traps.c and console.c code, so I recompiled xen few times. The main problem with
> was compiler, I think. I've always got data abort with hypervisor calls and
> similiar. Now I'm using gcc-linaro-arm-none-eabi-4.9 for both xen and
> application.
Your guest (i.e the application) and Xen should not need to be built
with the same compiler.
Which compiler led to use a data abort? And where was the data abort? In
Xen or the guest?
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-02 11:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 19:42 Basic bare metal ARM domain interface Ivan Pavić2
2016-05-27 10:04 ` Julien Grall
2016-05-27 13:19 ` Ivan Pavić2
[not found] ` <20160527211650.GA43457@galois.com>
2016-05-28 11:21 ` Ivan Pavić2
2016-05-30 20:21 ` Odgovor: " Ivan Pavić2
2016-05-31 9:53 ` Julien Grall
2016-06-01 20:06 ` Ivan Pavic
2016-06-02 11:41 ` Julien Grall [this message]
2016-06-02 19:09 ` Ivan Pavic
2016-06-03 10:23 ` Julien Grall
2016-06-06 23:31 ` Ivan Pavic
2016-06-07 14:18 ` Julien Grall
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=57501B4E.6040203@arm.com \
--to=julien.grall@arm.com \
--cc=awick@galois.com \
--cc=ivan.pavic2@fer.hr \
--cc=jtd@galois.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).