It makes no sense for the clock initialization to be
hanging around in setup_32.c when we have a generic kvm guest
initialization function available. So, we move kvmclock_init()
inside such a function, leading to a cleaner code.
Signed-off-by: Glauber Costa [EMAIL PROTECTED]
---
Glauber Costa wrote:
It makes no sense for the clock initialization to be
hanging around in setup_32.c when we have a generic kvm guest
initialization function available. So, we move kvmclock_init()
inside such a function, leading to a cleaner code.
Signed-off-by: Glauber Costa [EMAIL
From: Ryan Harper [EMAIL PROTECTED]
Rather than faking up some geometry, allow the backend to push the disk
geometry via virtio pci config option. Keep the old geo code around for
compatibility.
Signed-off-by: Ryan Harper [EMAIL PROTECTED]
Reviewed-by: Anthony Liguori [EMAIL PROTECTED]
diff
On Thursday 17 April 2008 04:56:37 Ryan Harper wrote:
From: Ryan Harper [EMAIL PROTECTED]
Rather than faking up some geometry, allow the backend to push the disk
geometry via virtio pci config option. Keep the old geo code around for
compatibility.
Hi Ryan,
Looks good! Some brief review