On 11 October 2013 18:38, Alvise Rigo a.r...@virtualopensystems.com wrote:
Both KVM and TCG populate the cpreg_list with 64 bit registers IDs, but in
the TCG side the cpreg_list is sorted using the 32 bit id version while in
the kvm side the 64 bit id version is used.
This patch makes the
Sorry, I should have mentioned that an improper sorting of the cpreg_list
could lead to a migration failure when cpu_post_load considers an incoming
register as missing in the cpreg_indexes array.
However, as long as the two lists are exactly the same, the problem does
not occur.
On Fri, Oct 11,
On 14 October 2013 11:45, alvise rigo a.r...@virtualopensystems.com wrote:
Sorry, I should have mentioned that an improper sorting of the cpreg_list
could lead to a migration failure when cpu_post_load considers an incoming
register as missing in the cpreg_indexes array.
However, as long as
Both KVM and TCG populate the cpreg_list with 64 bit registers IDs, but in the
TCG side the cpreg_list is sorted using the 32 bit id version while in the kvm
side the 64 bit id version is used.
This patch makes the sorting of the cpreg_list consistent between KVM and TCG.
Signed-off-by: Alvise
On 12 October 2013 02:38, Alvise Rigo a.r...@virtualopensystems.com wrote:
Both KVM and TCG populate the cpreg_list with 64 bit registers IDs, but in
the TCG side the cpreg_list is sorted using the 32 bit id version while in
the kvm side the 64 bit id version is used.
This patch makes the