On Fri, 2012-07-06 at 15:00 -0600, Toshi Kani wrote: > Yes, offlining and eject are similar operations to a core as it alone > cannot be removed physically. Ejecting a core is a logical eject > operation, which updates the status (_STA) of the object in ACPI after > offlining. The difference from the offlining is that the ejected core > is no longer assigned to the partition. Here is one example. Say, a > core is assigned to a guest partition as a dedicated resource (ex. 100% > of its CPU time is bound to the partition). Offlining this core saves > the power-consumption, but this core is still bound to the partition. > Ejecting the core removes it from the partition (logically), and allows > it to be assigned to other partition as a dedicated resource with > hot-add. > Ejecting a core is reasonable when eject happens from a guest. I still wonder what firmware would do if kernel calls eject method on a core when running on the native host platform. If firmware behavior is not well defined in this case, there might be some risk associated with calling eject method on core. Makes sense? -- Khalid Aziz <khalid.aziz@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
