From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: [TESTDAY] Test report
Date: Fri, 13 May 2016 22:34:44 +0200 [thread overview]
Message-ID: <20160513203444.GJ16305@toto> (raw)
* Hardware: ZCU102 ZynqMP board
* Software: Rolled my own dom0 linux
* Tested: Start dom0
The test fails with the following error:
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 0000000000080000
(XEN) Allocating 1:1 mappings totalling 512MB for dom0:
(XEN) BANK[0] 0x00000020000000-0x00000040000000 (512MB)
(XEN) Grant table range: 0x0000007fe00000-0x0000007fe5f000
(XEN) smmu: /amba/smmu@fd800000: d0: p2maddr 0x000000007ff64000
(XEN) Device tree generation failed (-22).
It's the PCIe node that is causing trouble, the bindings are here:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/pci/xilinx-nwl-pcie.txt
It's that inner interrupt-controller node that is causing problems as
Xen/ARM only supports one interrupt-controller node (IIUC).
Disabling the pcie node for zynqmp boards gets dom0 to boot (obviously
without PCIe support).
Does it make sense to try to fix this problem this late inte the
release cycle? (I can have a closer look and propose a possible fix
for discussion)
Or should we disable the PCIe for ZynqMP for now and try to fix this
properly for 4.8?
Any ideas/suggestions?
Best regards,
Edgar
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-05-13 20:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 20:34 Edgar E. Iglesias [this message]
2016-05-14 18:15 ` [TESTDAY] Test report Julien Grall
2016-05-14 19:04 ` Edgar E. Iglesias
2016-05-16 9:58 ` Wei Liu
2016-05-16 13:20 ` Julien Grall
2016-05-16 13:41 ` Edgar E. Iglesias
2016-05-16 13:43 ` Julien Grall
-- strict thread matches above, loose matches on Subject: below --
2017-05-23 17:03 Andrii Anisov
2017-05-23 20:14 ` Stefano Stabellini
2017-05-25 10:17 ` Julien Grall
2017-05-25 18:41 ` Stefano Stabellini
2016-05-13 15:14 Tamas K Lengyel
2015-10-01 16:59 Tamas K Lengyel
2015-10-01 17:04 ` Wei Liu
2014-10-30 10:54 Jan Vejvalka
2014-10-30 14:39 ` Ian Campbell
2014-10-31 6:35 ` Jan Vejvalka
2014-10-30 14:58 ` Roger Pau Monné
2014-01-20 22:49 Don Slutz
2014-01-20 23:35 ` Konrad Rzeszutek Wilk
2014-01-23 10:51 ` Ian Campbell
2014-01-23 22:03 ` Don Slutz
2014-01-24 14:58 ` Konrad Rzeszutek Wilk
2014-01-24 16:43 ` Don Slutz
2014-01-24 19:06 ` Don Slutz
2014-01-24 19:20 ` Konrad Rzeszutek Wilk
2014-01-27 1:15 ` herbert cland
2012-09-19 7:04 Dariusz Krempa
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=20160513203444.GJ16305@toto \
--to=edgar.iglesias@gmail.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xen.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).