[Xen-devel] [PATCH v6 1/4] arm: introduce psci_smp_ops
Nicolas Pitre
nicolas.pitre at linaro.org
Fri Apr 19 12:33:22 EDT 2013
On Fri, 19 Apr 2013, Ian Campbell wrote:
> On Fri, 2013-04-19 at 16:47 +0100, Nicolas Pitre wrote:
> > No one should be probing registers without making sure it is safe to do
> > so. Even on non virtualized hardware this can be a dangerous thing to
> > do.
>
> Won't people writing per machine code consider, not unreasonably, that
> having been called through a mdesc machine specific hook constitutes
> enough "making sure" that they think it is safe to touch registers which
> are specific to that machine?
Remember that this hook was introduced to decide at run time between
different possibilities for SMP ops on the _same_ machine configuration.
That machine shouldn't do things which is not permitted on either
possible alternatives already. So far the actual usage of that hook
only looks in the DT to make a decision. But even if it were to touch
the hardware, that means it has to be safe to do so on all the possible
hardware variations this mdesc is associated to.
And if Xen wants to emulate one of those hardware alternatives, then it
better be ready to emulate it properly, or manage for _another_ mdesc to
be selected instead. That's why mach-virt was introduced.
So in my opinion there is just no issue here.
Nicolas
More information about the linux-arm-kernel
mailing list