From: Suriyan Ramasami <suriyan.r@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Ivan Pavić2" <Ivan.Pavic2@fer.hr>
Subject: Re: Odroid XU3 support
Date: Wed, 27 Apr 2016 15:53:53 -0700 [thread overview]
Message-ID: <CANoR_ODOjJyHsxsXhpnzMM9A4MqLsoWzSu+LGJz=CLdsxoAYLQ@mail.gmail.com> (raw)
In-Reply-To: <571F439B.3070707@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 1815 bytes --]
On Tue, Apr 26, 2016 at 3:31 AM, Julien Grall <julien.grall@arm.com> wrote:
> (CC the author of the Odroid support in Xen)
>
> On 25/04/2016 11:01, Ivan Pavić2 wrote:
>
>> Hello,
>>
>
> Hello,
>
> I have CCed Suriyan who added the support of Odroid in Xen. He might be
> able to help you here.
>
>
>> i'm trying to boot dom0 linux on exynos5422 platform on A15 (big cpu
>> cluster).
>> From the past mailing lists on this link:
>> http://lists.xen.org/archives/html/xen-devel/2016-02/msg02275.html)
>> I'm not sure that is well defined how to change A7's for A15's.
>> Should change be in DTS or should one change cpu power up routines in
>> linux?
>> So far every time it boots from A7's.
>>
>
The Odroid XU3/XU4 afaict has a hardware pin which dictates if a A7 or an
A15 core should boot up. It is currently set to boot up from the A7s.
> Additionally, I found this in xen boot.ini file:
>>
>> # use the A7s for dom0 and pin them to it
>> setenv xen_bootargs sync_console console=dtuart dtuart=/serial@12C20000 \
>> dom0_mem=800M dom0_max_vcpus=4 dom0_vcpus_pin
>>
>> How this defines A7s for dom0?
>>
>> As mentioned above, the hardware by design boots up from the A7 cluster.
Hence, the first 4 cpus are A7s and the next 4 are the A15s.
> How can I check which core is currently active?
>> Judging by this link on big.LITTLE architecture:
>> http://forum.odroid.com/viewtopic.php?f=65&t=2580
>>
>> result of: cat /proc/cpuinfo | grep "CPU part" is
>> CPU part : 0xc07
>>
>> which stands for A7.
>>
>> If you do this in dom0, it will show all of them to be 0xc07. They are
vCPUs after all.
I am not sure if I answered your question. Please feel free to probe more.
Thanks!
-Suriyan
> Regards,
>>
>
> Regards,
>
> --
> Julien Grall
>
[-- Attachment #1.2: Type: text/html, Size: 3594 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-27 22:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 10:01 Odroid XU3 support Ivan Pavić2
2016-04-26 10:31 ` Julien Grall
2016-04-27 22:53 ` Suriyan Ramasami [this message]
2016-04-28 9:50 ` Julien Grall
2016-04-28 13:19 ` Ivan Pavić2
2016-04-28 13:26 ` Suriyan Ramasami
2016-05-05 11:39 ` Julien Grall
2016-05-05 11:39 ` Julien Grall
2016-05-08 11:59 ` Peng Fan
2016-05-09 9:49 ` Julien Grall
2016-05-10 7:53 ` Peng Fan
2016-05-10 9:33 ` Julien Grall
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='CANoR_ODOjJyHsxsXhpnzMM9A4MqLsoWzSu+LGJz=CLdsxoAYLQ@mail.gmail.com' \
--to=suriyan.r@gmail.com \
--cc=Ivan.Pavic2@fer.hr \
--cc=julien.grall@arm.com \
--cc=xen-devel@lists.xenproject.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).