Re: [PATCH RFC 0/1] Introduce VCPUOP_reset_vcpu_info

[Vitaly Kuznetsov <vkuznets@redhat.com>]

"Jan Beulich" <JBeulich@suse.com> writes:

>>>> On 07.08.14 at 13:41, <vkuznets@redhat.com> wrote:
>> "Jan Beulich" <JBeulich@suse.com> writes:
>>>>>> On 06.08.14 at 17:03, <vkuznets@redhat.com> wrote:
>>>> In xen their vcpu_info will point to dummy_vcpu_info (that's what we
>>>> have there before VCPUOP_register_vcpu_info I guess).
>>>
>>> Right, but such a vCPU can't be brought up. Did you verify that
>>> this holds with your additions?
>> 
>> That's fine as new kernel will call VCPUOP_register_vcpu_info on
>> bootup. 
>
> But my question was targeting the hypervisor side, i.e. I was
> asking that you get away from your "works fine in my limited use
> case" way of thinking, and rather check that you don't subtly
> break anything else.

Thanks, that's fine, that's what the RFC is about. I'll definitely try
looking deeper and I'll be grateful for some examples of what can
actually go wrong.

-- 
  Vitaly