xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 7 Jun 2016 15:18:50 +0100	[thread overview]
Message-ID: <5756D7CA.3050301@arm.com> (raw)
In-Reply-To: <20160606233109.GA12077@dumpram-Inspiron-3537>



On 07/06/16 00:31, Ivan Pavic wrote:
> Hello Julien,

Hello Ivan,

> On Fri, Jun 03, 2016 at 11:23:33AM +0100, Julien Grall wrote:
>>
>>
>> On 02/06/16 20:09, Ivan Pavic wrote:
>>> Hello Julien,
>>
>> Hello Ivan,
>>
>>> On Thu, Jun 02, 2016 at 12:41:02PM +0100, Julien Grall wrote:
>>>>
>>>> Which compiler led to use a data abort? And where was the data
>>>> abort? In Xen or the guest?
>>>>
>>>
>>> When I compile app directly on ODROID I used:
>>> arm-linux-gnueabihf
>>> gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1)
>>>
>>> HVC instruction works form assembler, but when I call it from main, for
>>> example:
>>> HYPERVISOR_console_io (HYPERCALL_WRITE, SYSTEM_UP_LEN, SYSTEM_UP_MSG);
>>> then I get this in xl dmesg:
>>> traps.c:2450:d2v0 HSR=0x90000046 pc=0x40008250 gva=0 gpa=0000000000000000
>>
>> To be honest this looks like a latent issue in your app rather than
>> a bug in the compiler.
>>
>> I would try to find which instruction is causing the data abort.
>> Also is your app running with page table and cache enabled?
>>
>
> Page table and cache are related to MMU, right? I didn't initialize MMU
> so far.

All the memory buffer passed to the hypercall should be cacheable (see 
xen/include/public/asm-arm.h for more details). I.e the MMU should be 
enabled.

Otherwise, the behavior is unreliable because the memory attribute will 
be different in Xen and the guest. Xen is mapping the region cacheable.

Regards,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2016-06-07 14:18 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
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 [this message]

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=5756D7CA.3050301@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).