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

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 06.08.14 at 17:03, <vkuznets@xxxxxxxxxx> wrote:
> "Jan Beulich" <JBeulich@xxxxxxxx> writes:
>> And why not for CPU 0?
>>
> 
> Because the suggested op will fail for already running CPU0..

Sure, but how do you deal with that?

>> Furthermore, what is the state of vCPU-s beyond 31 going to be after
>> they got their vCPU info reset? They won't have any other area as
>> fallback.
> 
> 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?

> I tested kexec with 64 vcpus case, no issues noticed.

That's purely observation based then, in an environment where
(for the specific operation here) not much can go wrong. But I
guess we'll see how things are once you properly document all
limitations.

Jan


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