From: Meng Xu <xumengpanda@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: sstabellini@kernel.org, Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Dushyant K Behl <dushyantbehl@in.ibm.com>,
Xen Devel <xen-devel@lists.xen.org>,
ijc@hellion.org.uk, Dushyant Behl <myselfdushyantbehl@gmail.com>
Subject: Re: Running Xen on Nvidia Jetson-TK1
Date: Fri, 13 May 2016 22:09:47 -0400 [thread overview]
Message-ID: <CAENZ-+n_YoCo6G67=aQ0Hx-ahfCtjrUBeBBio-RrkNxSBN69=Q@mail.gmail.com> (raw)
In-Reply-To: <57078396.5090400@arm.com>
Hi Julien and Dushyant,
>>>
>>>> (XEN) DOM0: [ 0.000000] irq: no irq domain found for
>>>> /interrupt-controller !
>>>> (XEN) DOM0: [ 0.000000] irq: no irq domain found for
>>>> /interrupt-controller !
>>>> (XEN) DOM0: [ 0.000000] irq: no irq domain found for
>>>> /interrupt-controller !
>>>> (XEN) DOM0: [ 0.000000] arch_timer: No interrupt available, giving up
>>>
>>>
>>>
>>> It looks like to me that Xen is not recreating the device-tree correctly.
>>> I
>>> would look into the kernel to find what is expected.
>>
>>
>> This looks like a possible bug (or some missing feature) in Xen's
>> device tree creation which could
>> take some time to handle, so if I could be of any more help to you
>> with this issue please let me know.
>
>
> There was a conversation on #xen-arm few days ago about this problem.
Is there a way that we can see the conversation on #xen-arm?
I hope to better understand the problem.
> Xen doesn't correctly recreate the GIC node which result in a loop between
> the interrupt controller. Can you try the below patch?
>
> http://dev.ktemkin.com/misc/xenarm-gic-parents.patch
It seems this link is invalid now...
Has this patch been upstreamed?
Hi Dushyant,
Could you help repost this patch in this email if it's not that large?
(Since we used the same repo, which is IanC's, it may be even better
if you could kindly share the patch based on the tegra-tk1-jetson-v1
branch of Ian's repo.?)
Hi Julien,
Do you have some suggestions on how we can debug and fix the issue
related to the device tree?
I saw that there may still be some issues with the NVIDIA devices as
Dushyant described after he applied the patch.
Right now, I have the exact same board as Dushyant has. I think I may
encounter the exact same issue as he did. So I'm wondering if there is
some documentation/tutorial/notes that we can learn about how to debug
the issues.
Thank you both very much for your help and time!
Best Regards,
Meng
-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-14 2:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 8:23 Running Xen on Nvidia Jetson-TK1 Dushyant K Behl
2016-03-09 13:37 ` Wei Liu
2016-03-10 5:08 ` Julien Grall
2016-03-12 14:20 ` Dushyant Behl
2016-03-12 15:27 ` Meng Xu
2016-03-12 20:23 ` Dushyant Behl
2016-03-13 2:10 ` Meng Xu
2016-03-14 9:31 ` Dushyant Behl
2016-03-14 14:12 ` Konrad Rzeszutek Wilk
2016-03-14 14:19 ` Dushyant Behl
2016-03-17 14:52 ` Julien Grall
2016-03-18 15:01 ` Dushyant Behl
2016-03-18 17:23 ` Julien Grall
2016-03-21 10:12 ` Dushyant Behl
2016-03-24 11:05 ` Dushyant Behl
2016-03-29 19:01 ` Julien Grall
2016-03-29 20:56 ` Dushyant Behl
2016-04-01 10:04 ` Julien Grall
2016-04-07 7:48 ` Dushyant Behl
2016-04-08 10:10 ` Julien Grall
2016-04-08 12:27 ` Ian Campbell
2016-04-14 15:54 ` Dushyant Behl
2016-05-14 18:43 ` Meng Xu
2016-05-14 19:03 ` Dushyant Behl
2016-05-14 2:09 ` Meng Xu [this message]
2016-05-14 17:36 ` Dushyant Behl
2016-05-14 18:34 ` Meng Xu
2016-05-14 18:37 ` Meng Xu
2016-05-14 18:58 ` Dushyant Behl
2016-05-12 1:00 ` Meng Xu
2016-05-12 9:19 ` Dushyant Behl
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='CAENZ-+n_YoCo6G67=aQ0Hx-ahfCtjrUBeBBio-RrkNxSBN69=Q@mail.gmail.com' \
--to=xumengpanda@gmail.com \
--cc=dushyantbehl@in.ibm.com \
--cc=ijc@hellion.org.uk \
--cc=julien.grall@arm.com \
--cc=myselfdushyantbehl@gmail.com \
--cc=sstabellini@kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--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).