On 06/15/2011 02:32 PM, Jan Kiszka wrote:
>
> If it isn't zero, there's still a good chance fopcode will be zero
> (64-bit userspace, thread that hasn't used the fpu since the last
> context switch, last opcode happened to be zero).
I do not yet find "if fopcode is invalid, it is zero, just as IP and DP"
in the spec. What clears them reliably?
FNINIT
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
