Re: [Qemu-devel] [PATCH 1/4] [PATCH] introduce QEMUAccel and fill it with interrupt specific driver

[Glauber Costa <gcosta@redhat.com>]

Paul Brook wrote:
>>> Maybe 'VCPU' would be a clearer name?  QEMU provides its own VCPU, and
>>> KQEMU+QEMU also provide one toegether.  While KVM provides essentially
>>> one or more whole VCPUs by itself and uses QEMU's drivers only doesn't
>>> it?
>>>
>>> -- Jamie
>> VCPU is rather confusing with the vcpus themselves. KVM, for instance,
>> has its own structures called "vcpu".
>>
>> If it is preferred, however, we can name the structure VCPUOperations,
>> and change the function names that involves accel_yyy to vcpu_op_yyy()
> 
> kvm wants to hook into more than just the CPU doesn't it?
But so far, the structure I proposed only touches cpu-related things.
We can have two structures for clarity. Like MEMOperations, and so far.
We do it this way for paravirt_ops in linux, with good results in code 
clarity.