Alexander Graf [off-list ref] writes:
On 01/28/2014 05:44 PM, Aneesh Kumar K.V wrote:
quoted
We definitely don't need to emulate mtspr, because both the registers
are hypervisor resource.
This patch description doesn't cover what the patch actually does. It
changes the implementation from "always tell the guest it uses 100%" to
"give the guest an accurate amount of cpu time spent inside guest
context".
Will fix that
Also, I think we either go with full hyp semantics which means we also
emulate the offset or we go with no hyp awareness in the guest at all
which means we also don't emulate SPURR which is a hyp privileged
register.
Can you clarify this ?
Otherwise I like the patch :).
-aneesh