From: Julien Grall <julien.grall@linaro.org>
To: Suriyan Ramasami <suriyan.r@gmail.com>
Cc: keir@xen.org, Ian Campbell <ian.campbell@citrix.com>,
ian.jackson@eu.citrix.com, Tim Deegan <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [ARM:PATCH v1 1/1] Add Odroid-XU (Exynos5410) support
Date: Sat, 26 Jul 2014 22:26:25 +0100 [thread overview]
Message-ID: <53D41D01.7060103@linaro.org> (raw)
In-Reply-To: <53D41C84.5060706@linaro.org>
On 26/07/14 22:24, Julien Grall wrote:
>
>
> On 26/07/14 21:26, Suriyan Ramasami wrote:
>> On Sat, Jul 26, 2014 at 10:58 AM, Julien Grall
>> <julien.grall@linaro.org> wrote:
>>>
>>>
>>> On 26/07/14 17:02, Suriyan Ramasami wrote:
>>>>
>>>> Hi Julien,
>>>>
>>>> On Sat, Jul 26, 2014 at 4:28 AM, Julien Grall <julien.grall@linaro.org>
>>>> wrote:
>>>>>
>>>>> Hi Suriyan,
>>>>>
>>>>>
>>>>> On 26/07/14 08:26, Suriyan Ramasami wrote:
>>>>>>
>>>>>>
>>>>>> I also noticed that in some instances of "xl create" it does bring up
>>>>>> domU with 4 cpus as mentioned in the domU.cfg file, and in those
>>>>>> instances the domU boots up.
>>>>>>
>>>>>> Is this some kind of bug?
>>>>>
>>>>>
>>>>>
>>>>> We use PSCI to boot secondary CPUs. You may want to check the the PSCI
>>>>> call
>>>>> has effectively been issued for those VCPUs.
>>>>>
>>>> I shall check on this!
>>>>>
>>>>> Which Xen and Linux version are you using?
>>>>
>>>> Xen is 4.5 dev (git clone git://xenbits.xen.org/xen.git)
>>>> Linux is 3.14 from hardkernel linux repository, branch:
>>>> odroid-3.14.y-linaro
>>>
>>>
>>> Can you try a Linux upstream? The error may come from the hardkernel
>>> linux.
>>
>> Is this for domU?
>> For dom0, I do not have a working kernel for upstream for the XU. I
>> did try 3.16 samsung-next as well as mainline linux and the dts needs
>> to be worked upon (or so I think)
>
> I was talking about domU.
>
>> Using upstream for domU exhibits the same behavior.
>>
>> One out of roughly 10 creates succeeds (I can get console output).
>> In the cases that succeed, I do see that do_psci_cpu_on() gets called.
>> In the cases that domU does not boot up, the call to do_psci_cpu_on()
>> does not happen.
>
> Reading back one of your previous mail:
>
> "I have noticed that there is no ARM port of XEN having more than 2
> CPUs. Is that correct? I am mentioning this, cause with the XU, though
> I can bring up all 4 processors in XEN and in dom0, domU fails to make
> much boot progress when it is xl created. I am able to boot domU, if I
> restrict the dtb for dom0 to 2 CPUs."
>
> By "I restrict the dtb for dom0 to 2 CPUs", did you mean removing some
> CPUs in the device tree or using dom0_max_vcpus=2 on Xen command line?
I forgot a question. Does a guest with 1 VCPU is working fine? I can't
fine any clue on your mails.
> I was wondering if dom0 is touching the physical CPUs by mistake (mainly
> because we map some regions used to control them).
> It might be worse to check that no cpufreq or power management is called
> on DOM0 at any time.
--
Julien Grall
next prev parent reply other threads:[~2014-07-26 21:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 22:47 [ARM:PATCH v1 1/1] Add Odroid-XU (Exynos5410) support Suriyan Ramasami
2014-07-25 8:18 ` Ian Campbell
2014-07-25 12:19 ` Julien Grall
2014-07-25 12:39 ` Ian Campbell
2014-07-25 17:45 ` Suriyan Ramasami
2014-07-25 20:05 ` Ian Campbell
2014-07-26 0:06 ` Suriyan Ramasami
2014-07-26 7:26 ` Suriyan Ramasami
2014-07-26 11:28 ` Julien Grall
2014-07-26 16:02 ` Suriyan Ramasami
2014-07-26 17:58 ` Julien Grall
2014-07-26 20:26 ` Suriyan Ramasami
2014-07-26 21:24 ` Julien Grall
2014-07-26 21:26 ` Julien Grall [this message]
2014-07-27 18:12 ` Suriyan Ramasami
2014-07-28 12:53 ` Julien Grall
2014-07-28 18:06 ` Suriyan Ramasami
2014-07-28 20:19 ` Suriyan Ramasami
2014-07-28 22:25 ` Suriyan Ramasami
2014-07-29 7:30 ` Ian Campbell
2014-07-29 15:49 ` Suriyan Ramasami
2014-07-29 17:36 ` Ian Campbell
2014-08-12 19:05 ` Suriyan Ramasami
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=53D41D01.7060103@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=suriyan.r@gmail.com \
--cc=tim@xen.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).