On 10/15/2009 06:22 PM, Jan Kiszka wrote:
Needs a KVM_CAP as well.
KVM_CAP_VCPU_STATE will imply KVM_CAP_NMI_STATE, so I skipped the latter
(user space code would use the former anyway to avoid yet another #ifdef
layer).
OK. New bits will need the KVM_CAP, though.
Perhaps it makes sense to query about individual states, including
existing ones? That will allow us to deprecate and then phase out
broken states. It's probably not worth it.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
