On Fri, 5 Apr 2013, Stefano Stabellini wrote: > On Fri, 5 Apr 2013, Stefano Stabellini wrote: > > - we are running on Xen > > Xen is running on the platform, we are running as a guest on Xen and an > > hypervisor node is available on device tree. > > Let's also assume that there aren't any "arm,cci" compatible nodes on > > device tree because Xen wouldn't export this kind of information to any > > guests right now. Therefore PSCI should be used to boot secondary cpus. > > Just in case this isn't clear enough: we don't have big.LITTLE support > in Xen right now, not in the hypervisor and certainly not in guests. > I'm keen on having big.LITTLE support in the hypervisor (thus some > code similar to your MCPM patch series will probably end up in Xen at > some point) but I doubt we'll expose big.LITTLE to guests any time > soon. It's going to be years, so I am not particularly worried about > it right now.
I fully understand that it is unlikely that a Xen guest will "see" a big.LITTLE environment in the near future. My concern is about a kernel that is _configured_ to run either on a native VExpress machine that might or might not be b.L, or as a Xen guest, in the same zImage binary. Nicolas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/