On Tue, May 04, 2010 at 02:35:28PM -0400, Glauber Costa wrote:
Currently, in the linux kernel, we reset kvmclock if we are rebooting
into a crash kernel through kexec. The rationale, is that a new kernel
won't follow the same memory addresses, and the memory where kvmclock is
located in the
On 05/04/2010 09:35 PM, Glauber Costa wrote:
Currently, in the linux kernel, we reset kvmclock if we are rebooting
into a crash kernel through kexec. The rationale, is that a new kernel
won't follow the same memory addresses, and the memory where kvmclock is
located in the first kernel, will be
On Wed, May 05, 2010 at 10:26:43AM +0300, Avi Kivity wrote:
+msr_data.info.nmsrs = n;
+
+return kvm_vcpu_ioctl(env, KVM_SET_MSRS,msr_data);
+}
+
+
How about a different approach? Query the supported MSRs
(KVM_GET_MSR_LIST or thereabout) and reset them (with special cases
for
On 05/05/2010 06:24 PM, Glauber Costa wrote:
On Wed, May 05, 2010 at 10:26:43AM +0300, Avi Kivity wrote:
+msr_data.info.nmsrs = n;
+
+return kvm_vcpu_ioctl(env, KVM_SET_MSRS,msr_data);
+}
+
+
How about a different approach? Query the supported MSRs
(KVM_GET_MSR_LIST or
On Wed, May 05, 2010 at 06:34:22PM +0300, Avi Kivity wrote:
On 05/05/2010 06:24 PM, Glauber Costa wrote:
On Wed, May 05, 2010 at 10:26:43AM +0300, Avi Kivity wrote:
+msr_data.info.nmsrs = n;
+
+return kvm_vcpu_ioctl(env, KVM_SET_MSRS,msr_data);
+}
+
+
How about a different
Currently, in the linux kernel, we reset kvmclock if we are rebooting
into a crash kernel through kexec. The rationale, is that a new kernel
won't follow the same memory addresses, and the memory where kvmclock is
located in the first kernel, will be something else in the second one.
We don't do
