Re: [Xen-devel] [PATCH RFC 0/1] Introduce VCPUOP_reset_vcpu_info

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 07.08.14 at 13:41, <vkuznets@xxxxxxxxxx> wrote:
> "Jan Beulich" <JBeulich@xxxxxxxx> writes:
>>>>> On 06.08.14 at 17:03, <vkuznets@xxxxxxxxxx> 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.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel