[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2 1/1] XEN/ARM: Add Odroid-XU3/XU4 support

On Tue, 2016-02-09 at 10:20 -0800, Suriyan Ramasami wrote:
> ÂI agree on the first two paragraphs.
> > > For the third paragraph, the rebuttal is that the exynos5800 and
> > > exynos5422 based SoCs can have both clusters on at the same time. Hence,
> > > the third paragrapah comment will have to be tweaked further. Possibly
> > > reading:
> > > The exynos5800 and exynos5422 can have both clusters on at the same time.
> > > The exynos5800 boots up with cpu0 on cluster0 (A15). The exynos5422 can
> > > boot up on either clusters as its pin controlled. In this case the DTS
> > > should properly reflect the cpu order.
> > 
> > Does the OS need to be aware of all these combinations though? Is it not
> > sufficient to know how to bring up an A15 core and how to bring up an A7
> > core and then just do so based on the information in the DTS, without
> > needing to worry about which sort of core we happened to have booted on?
> > 
> > 
> Unfortunately, at least looking at the boot up code for the Exynos5422,
> the OS needs to be aware of it. This is what I see in the linux source
> code. If it boots up on an A7, then a special reset is needed which is
> not needed when booted up otherwise. I do not have much more details on
> that other than the Linux code.
> Without that reset sequence, I have also verified that the powered on CPU
> does not come up.

Are we able to say that if we are booted on cluster 1 (always the A7s) then
we always need this magic reset? i.e. is true for all SoCs which have an A7
cluster and can boot from it? (it's tautologically true for SocS which
either have no A7's or cannot boot from them).

Maybe I'm looking for similarities between different exynos variants which
doesn't exist though. If we are going to talk about specific SoCs in the
comments then I would rather that the code was also explicit rather than
assuming cluster 1 will only be found on the 5800, that might be as simple
as mapping the compatible string to a max_cluster (default 0 for unknown
SoC) and warning if pcluster > max_cluster.

> > Â>Â The exynos5410 can have only one cluster on at a time, and it boots
> > up
> > > with pcluster == 0.
> > > Any tweaks and comments on the above is appreciated.
> > 
> > How much of this is down to physical h/w limitations and how much of it
> > is
> > down to firmware or software limitations? Can you flip the to the other
> > cluster somehow?
> > ÂÂ
> The 5410 boots up on an A15, and only those 4 A15 CPUs in cluster 0 are
> brought up. Hence, no flipping is required.

What I meant was, given that the 5410 has a cluster of A15 and a cluster of
A7s (right?) and you can only have one on at a time, how does an OS make
use of the A7s if it wants to? As you say it boots from the A15, so how can
the A7s be used?


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.