On 9 August 2013 20:03, Mian M. Hamayun
m.hama...@virtualopensystems.com wrote:
On 09/08/2013 15:24, Peter Maydell wrote:
This set of #ifdefs is pretty messy. I suggest splitting kvm.c
into three:
target-arm/kvm.c -- anything common to both 32 and 64 bit
target-arm/kvm32.c --
On 23 July 2013 10:33, Mian M. Hamayun m.hama...@virtualopensystems.com wrote:
From: Mian M. Hamayun m.hama...@virtualopensystems.com
The cpu init function tries to initialize with all possible cpu types, as
KVM does not provide a means to detect the real cpu type and simply refuses
to
On 09/08/2013 15:24, Peter Maydell wrote:
On 23 July 2013 10:33, Mian M. Hamayun m.hama...@virtualopensystems.com wrote:
From: Mian M. Hamayun m.hama...@virtualopensystems.com
The cpu init function tries to initialize with all possible cpu types, as
KVM does not provide a means to detect the
From: Mian M. Hamayun m.hama...@virtualopensystems.com
The cpu init function tries to initialize with all possible cpu types, as
KVM does not provide a means to detect the real cpu type and simply refuses
to initialize on cpu type mis-match. By using the loop based init function,
we avoid the
