On 12/17/21 02:35, Jing Qi wrote:
Hi Michal,
Seems there is a typo of 'restrictive' instead of 'strict' in the last
line of updated content. Right?
Actually, no. What this patch does is document the current state of
things. With current master, 'restrictive' is not allowed and only
'strict' is (the fact it doesn't work really is addressed in later
patches in this series). Therefore, I think this patch is correct as is.
But I see where you're coming from. In the end there will be only
'restrictive' allowed.
The reason I chose to do things separately is for easier cherry pick /
revert. Imagine at some point in future we will be able to tell QEMU to
migrate its own memory. Then we might want to revert patch 4/6 which
will leave us with:
For a running domain, the mode can't be changed, and the nodeset can be
changed only if the domain was started with mode of either \`strict' or
\`restrictive'.
Hopefully, my explanation makes sense.
Michal