From: Andrii Anisov <andrii_anisov@epam.com>
To: George John <georgeeldhojohn@gmail.com>,
Oleksandr Tyshchenko <olekstysh@gmail.com>
Cc: xen-devel@lists.xenproject.org,
Julien Grall <julien.grall@arm.com>,
nd@arm.com
Subject: Re: Error in Xen while booting for salvator-X (M3 Board)
Date: Mon, 27 Feb 2017 12:52:33 +0200 [thread overview]
Message-ID: <8c422d50-a2be-82cc-4a75-a749bae475d0@epam.com> (raw)
In-Reply-To: <CANou6Sr1kdo9U-ZF7kRkt9a00e74ZN2-AnJkuM1t7b_CttKeTg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1510 bytes --]
Dear George,
Actually r8a7796 and r8a7795 are different chips with different
peripherals, so you should adjust your r8a7796-xxx.dtb.
I'm not really sure what the problem is with XEN 4.6, but the crash
point you are stepped in with 4.8 is commented as following
/*
* Currently, to ensure hypervisor safety, when we received a
* guest-generated vSerror/vAbort, we just crash the guest to protect
* the hypervisor. In future we can better handle this by injecting
* a vSerror/vAbort to the guest.
*/
So I guess you see the abort on access to a peripheral missing on
r8a7796 but described in a device tree for r8a7795.
--
*Andrii Anisov*
*Lead Systems Engineer*
*Office: *+380 44 390 5457 <tel:+380%2044%20390%205457> *x* 66766
<tel:66766>*Cell: *+380 50 5738852 <tel:+380%2050%205738852>*Email:
*andrii_anisov@epam.com <mailto:andrii_anisov@epam.com>
*Kyiv**,* *Ukraine *(GMT+3)*epam.com <http://www.epam.com>*
CONFIDENTIALITY CAUTION AND DISCLAIMER
This message is intended only for the use of the individual(s) or
entity(ies) to which it is addressed and contains information that is
legally privileged and confidential. If you are not the intended
recipient, or the person responsible for delivering the message to the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited.
All unintended recipients are obliged to delete this message and destroy
any printed copies.
[-- Attachment #1.2: Type: text/html, Size: 5359 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-02-27 10:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 12:03 Error in Xen while booting for salvator-X (M3 Board) George John
2017-02-24 14:53 ` Julien Grall
2017-02-24 15:13 ` Oleksandr Tyshchenko
2017-02-27 10:29 ` George John
2017-02-27 10:48 ` Oleksandr Tyshchenko
2017-02-27 10:55 ` Oleksandr Andrushchenko
2017-02-28 15:01 ` George John
2017-02-27 10:52 ` Andrii Anisov [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=8c422d50-a2be-82cc-4a75-a749bae475d0@epam.com \
--to=andrii_anisov@epam.com \
--cc=georgeeldhojohn@gmail.com \
--cc=julien.grall@arm.com \
--cc=nd@arm.com \
--cc=olekstysh@gmail.com \
--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).