From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [ARM:PATCH v1 1/1] Add Odroid-XU (Exynos5410) support Date: Sat, 26 Jul 2014 22:26:25 +0100 Message-ID: <53D41D01.7060103@linaro.org> References: <1406242066-7001-1-git-send-email-suriyan.r@gmail.com> <53D24B4B.7020908@linaro.org> <1406291967.24842.1.camel@kazak.uk.xensource.com> <1406318711.4100.38.camel@hastur.hellion.org.uk> <53D390C3.4000506@linaro.org> <53D3EC54.6060105@linaro.org> <53D41C84.5060706@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <53D41C84.5060706@linaro.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Suriyan Ramasami Cc: keir@xen.org, Ian Campbell , ian.jackson@eu.citrix.com, Tim Deegan , "xen-devel@lists.xen.org" , Jan Beulich List-Id: xen-devel@lists.xenproject.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 >> wrote: >>> >>> >>> On 26/07/14 17:02, Suriyan Ramasami wrote: >>>> >>>> Hi Julien, >>>> >>>> On Sat, Jul 26, 2014 at 4:28 AM, Julien Grall >>>> 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