From: Julien Grall <julien.grall@arm.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
xen-devel@lists.xensource.com, sstabellini@kernel.org
Subject: Re: [TESTDAY] Test report of ARM CubieTruck with Xen 4.7 (staging)
Date: Fri, 1 Apr 2016 17:07:27 +0100 [thread overview]
Message-ID: <56FE9CBF.4060407@arm.com> (raw)
In-Reply-To: <20160330153043.GA30491@char.us.oracle.com>
Hi Konrad,
Thank you for testing Xen ARM on the cubietruck!
On 30/03/16 16:30, Konrad Rzeszutek Wilk wrote:
> *Hardware: ARM CubieTruck A20 (2GB).
>
> *Software: Linaro 14.04 with
> - Xen 4.7 (829e03c acpi: drop CONFIG_ACPI_BOOT and use CONFIG_ACPI instead + xsplice.v5)
> - Linux v4.5 (with revert of 88f8b1bb41c6208f81b6a480244533ded7b59493 "
> stmmac: Fix 'eth0: No PHY found' regression")
> - Linux v4.4
> - Linux v4.3
> - Linux v4.2
>
> *Guest operating systems: Ubuntu 14.04
>
> *Functionality tested: ARM Manual Smoke Test
>
> *Comments:
>
> I get these:
>
> (XEN) Freed 260kB init memory.
> (XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER4
> (XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER8
> (XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER12
> (XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER16
> (XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER0
> (XEN) d0v1: vGICD: unhandled word write 0xffffffff to ICACTIVER0
> (XEN) d1v0: vGICD: unhandled word write 0xffffffff to ICACTIVER0
Xen doesn't currently emulate the registers I*ACTIVERn. For now, it's
not a big problem as the usage of I*ACTIVER0 is very limited. This will
need to be supported properly when migration will be added for ARM.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-04-01 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 15:30 [TESTDAY] Test report of ARM CubieTruck with Xen 4.7 (staging) Konrad Rzeszutek Wilk
2016-04-01 16:07 ` 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=56FE9CBF.4060407@arm.com \
--to=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.