From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrii Anisov Subject: Re: Error in Xen while booting for salvator-X (M3 Board) Date: Mon, 27 Feb 2017 12:52:33 +0200 Message-ID: <8c422d50-a2be-82cc-4a75-a749bae475d0@epam.com> References: <6b4a6e23-aacb-99ec-3445-ff860611b3fa@arm.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2974244328063794455==" Return-path: Received: from mail6.bemta6.messagelabs.com ([193.109.254.103]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ciIvA-0007kO-WD for xen-devel@lists.xenproject.org; Mon, 27 Feb 2017 10:52:49 +0000 In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: George John , Oleksandr Tyshchenko Cc: xen-devel@lists.xenproject.org, Julien Grall , nd@arm.com List-Id: xen-devel@lists.xenproject.org --===============2974244328063794455== Content-Type: multipart/alternative; boundary="------------22C576196BBDA92976B99983" --------------22C576196BBDA92976B99983 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit 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 *x* 66766 *Cell: *+380 50 5738852 *Email: *andrii_anisov@epam.com *Kyiv**,* *Ukraine *(GMT+3)*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. --------------22C576196BBDA92976B99983 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 8bit

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 x 66766   Cell: +380 50 5738852   Email: andrii_anisov@epam.com

Kyiv, Ukraine (GMT+3)   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.

 

--------------22C576196BBDA92976B99983-- --===============2974244328063794455== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============2974244328063794455==--