> But the BSP doesn't need to save anything. We'll always have N-1 SAL >states saved and N-1 CPUs that can be taken offline. As long as we >don't hard link a state to a specific CPU, we're in good shape. I've >been testing on my boxes with an order that intentionally gives CPUs the >state saved off of another CPU on OS entry. I appear to be able to make >the BSP return to SAL as well, but I don't think the rest of the hotplug >code is ready for this (the other CPU doesn't seem to be getting >scheduled). That sounds worrying ... it assumes that the SAL thinks that cpus are fungible, which might not be true on ccNUMA systems. -Tony - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Wed Feb 9 14:51:41 2005
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:35 EST