On Mon, 22 Apr 2013, Nicolas Pitre wrote: > > I think the key thing that non-Xen folks aren't aware of is that > > although Xen passes the majority of the underlying hardware to the dom0 > > kernel to manage one of the few things it does not expose to guests > > (where "guests" includes dom0) is the SMP topology of the underlying system. > > I suspect it is unlikely to pass on the DT information about the CCI > either. Which means that, in the case that started this thread, the > smp_init function needed by MCPM will simply return false and the next > priority in the list i.e. plain PSCI will be initialized instead. > > I don't forsee the need to poke at the hardware directly within > ->smp_init, not since everything is moving to DT now. > > Sure there are ways to screw up Xen support from within this hook, but > that can be achieved in many other places. Will Xen take over every > possible hooks in the kernel to prevent that from happening? > > So please let's not cry wolf needlessly.
OK, you convinced me :-) I'll drop the patch. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
