From: Julien Grall <julien.grall@arm.com>
To: Peng Fan <van.freenix@gmail.com>
Cc: "Suriyan Ramasami" <suriyan.r@gmail.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Ivan Pavić2" <Ivan.Pavic2@fer.hr>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Odroid XU3 support
Date: Mon, 9 May 2016 10:49:58 +0100 [thread overview]
Message-ID: <57305D46.70305@arm.com> (raw)
In-Reply-To: <20160508115944.GB926@linux-7smt.suse>
On 08/05/2016 12:59, Peng Fan wrote:
> Hi Julien,
Hello Peng,
> On Thu, Apr 28, 2016 at 10:50:33AM +0100, Julien Grall wrote:
>> Hello,
>>
>> On 27/04/16 23:53, Suriyan Ramasami wrote:
>>
>>> 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.
>>
>> Which is not a good idea. This means that Linux is not able to detect
>> potential errata for the underlying cores (in this case the cortex-A15). Also
>> some userspace may do some runtime optimization based on the kind of CPUs
>> available in the guest.
>>
>> Xen is not ready for big.LITTLE, so I would highly recommend you to disable
>> either all the Cortex-A15 or Cortex-A7.
>
> For Cortex A53 + A72 or A53 + A57, xen also not ready?
Xen is not ready at all for big.LITTLE, no matter the combinations of
the CPUs.
Some of the cores you mentioned (especially A53 and A57) may contain
errata that requires workaround in the Linux kernel to avoid potential
data corruption or deadlock. As the vPIDR will always be equal to the
boot CPU vMIDR, Linux won't apply the necessary workaround to itself.
So using big and little cores at the same time with Xen is not safe at
all, even if you create CPU pool with current version of Xen.
>
> If need to let xen support A53 + A72 or A53 + A57, what work may need to be done?
I gave some insights later this thread. See:
http://lists.xen.org/archives/html/xen-devel/2016-05/msg00466.html
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-09 9:50 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
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 [this message]
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=57305D46.70305@arm.com \
--to=julien.grall@arm.com \
--cc=Ivan.Pavic2@fer.hr \
--cc=sstabellini@kernel.org \
--cc=suriyan.r@gmail.com \
--cc=van.freenix@gmail.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).