> We have __set_cpuflag() to set a flag; do we also want
> __clear_cpuflag()? Would make the code nicer, I think. (There are more
> possible callers for that.)
Mind if we do that in a separate patch?
Thanks!
>
>> read_lock(&vcpu->kvm->arch.sca_lock);
>> if (vcpu->kvm->arch.use_esca) {
>> struct esca_block *sca = vcpu->kvm->arch.sca;
--
Thanks,
David / dhildenb
--
To unsubscribe from this list: send the line "unsubscribe linux-s390" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
