|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v2 2/6] arm: move GIC SGI kicking into separate function
On 12/02/2013 04:01 PM, Ian Campbell wrote: On Mon, 2013-12-02 at 12:08 +0100, Andre Przywara wrote:Currently we unconditionally send SGIs to all cores on SMP bringup. PSCI will not need this, so we move this into a function and call it explicitly from the platforms that need it. This gets us get rid of the empty cpu_up() platform functions in ARM32 and the comment in there.I don't think this is quite true -- even on a PSCI system the kick is required to get past the gate in head.S. Right, but this is the responsibility of the PSCI handler in the firmware, right? I was under the assumption that the semantics of cpu_on is to start executing code at the given address, whatever this takes internally. Calxeda firmware for instance does the SGI kick. I wonder how this interacts with PSCI implementations which use an SGI themselves internally... Please note that we do not get rid of this, but just move it. ARM64 calls it in arm64/smpboot.c, ARM32 non-PSCI platforms call this now explicitly by pointing to that function in their platforms/foo.c file. But I suppose it is the intention that the platform code always has both its own logic and this SGI kick (possibly coalesced) in such circumstances? Which is probably ok? That was my thinking, yes. Regards, Andre.
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |