From: Julien Grall <firstname.lastname@example.org> To: Dushyant Behl <email@example.com> Cc: firstname.lastname@example.org, Wei Liu <email@example.com>, Stefano Stabellini <firstname.lastname@example.org>, Dushyant K Behl <email@example.com>, Xen Devel <firstname.lastname@example.org>, Meng Xu <email@example.com>, firstname.lastname@example.org Subject: Re: Running Xen on Nvidia Jetson-TK1 Date: Fri, 8 Apr 2016 11:10:30 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CAHF350+bddg+voPb33FDMyVRQCxmT_LZyfSzVmqZ-Jh=GGFc2w@mail.gmail.com> On 07/04/16 08:48, Dushyant Behl wrote: > Hello, Hi Dushyant, > On Fri, Apr 1, 2016 at 3:34 PM, Julien Grall <firstname.lastname@example.org> wrote: >> Hello Dushyant, >> >> On 29/03/16 21:56, Dushyant Behl wrote: >>> >>> On Wed, Mar 30, 2016 at 12:31 AM, Julien Grall <email@example.com> >>> wrote: >>>> >>>> On 24/03/16 11:05, Dushyant Behl wrote: >> >> >>> (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. 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 > > [I've cc'ed Ian Campbell in this mail (Sorry for cc'ing you explicitly)] Ian's citrix e-mail is not valid anymore. I have CC'ed the new one. > Ian, > > Actually, I want to run Xen on the Tegra Jetson board for some project > of mine but currently Linux-4.1 is > failing as dom0 because its not able to receive interrupts from the arch_timer. > This link contains the dom0 failure boot log - > http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg03715.html > > In your patch for *Hacky* support for Jetsok-TK1 you said that you > were able to run guests on > Jetson-tk1 board with Xen. Can I know which kernel version you used as > dom0 (and possibly domU guests)? Regards, -- Julien Grall _______________________________________________ Xen-devel mailing list Xenfirstname.lastname@example.org http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-08 10:10 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-03-08 8:23 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 [this message] 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 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Running Xen on Nvidia Jetson-TK1' \ /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
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).