Re: [PATCH 8/9] KVM: Rework of guest debug state writing

Avi Kivity
2010-02-21T09:27:14Z

On 02/19/2010 08:22 PM, Jan Kiszka wrote:
> So far we synchronized any dirty VCPU state back into the kernel before
> updating the guest debug state. This was a tribute to a deficite in x86
> kernels before 2.6.33. But as this is an arch-dependent issue, it is
> better handle in the x86 part of KVM and remove the writeback point for
> generic code. This also avoids overwriting the flushed state later on if
> user space decides to change some more registers before resuming the
> guest.
>

Inferring one property of kvm.ko from another is not good, since it
creates problems with backports. Better to create a separate KVM_CAP_
for the issue you're testing (and we can retroactively apply it to 2.6.33).

--
error compiling committee.c: too many arguments to function