On Sun, 2011-02-27 at 14:16 +0200, Avi Kivity wrote:
On 02/23/2011 07:44 PM, Glauber Costa wrote:
We've been supporting kvmclock MSRs in the 0x4b564d00-0x4b564dff range
for a while now, but we're not exposing it yet, meaning nobody is using it.
This simple patch takes care of that.
We're
On 02/28/2011 03:24 PM, Glauber Costa wrote:
On Sun, 2011-02-27 at 14:16 +0200, Avi Kivity wrote:
On 02/23/2011 07:44 PM, Glauber Costa wrote:
We've been supporting kvmclock MSRs in the 0x4b564d00-0x4b564dff range
for a while now, but we're not exposing it yet, meaning nobody is using
On 02/28/2011 03:30 PM, Avi Kivity wrote:
On 02/28/2011 03:24 PM, Glauber Costa wrote:
On Sun, 2011-02-27 at 14:16 +0200, Avi Kivity wrote:
On 02/23/2011 07:44 PM, Glauber Costa wrote:
We've been supporting kvmclock MSRs in the 0x4b564d00-0x4b564dff
range
for a while now, but we're not
On 02/25/2011 03:11 PM, Glauber Costa wrote:
On Thu, 2011-02-24 at 18:54 -0500, Steven Rostedt wrote:
On Thu, 2011-02-24 at 20:48 -0300, Glauber Costa wrote:
On Thu, 2011-02-24 at 18:24 -0500, Steven Rostedt wrote:
On Wed, Feb 23, 2011 at 12:44:14PM -0500, Glauber Costa wrote:
On 02/23/2011 07:44 PM, Glauber Costa wrote:
We've been supporting kvmclock MSRs in the 0x4b564d00-0x4b564dff range
for a while now, but we're not exposing it yet, meaning nobody is using it.
This simple patch takes care of that.
We're exposing them via KVM_GET_SUPPORTED_CPUID, leaf
On Thu, 2011-02-24 at 18:54 -0500, Steven Rostedt wrote:
On Thu, 2011-02-24 at 20:48 -0300, Glauber Costa wrote:
On Thu, 2011-02-24 at 18:24 -0500, Steven Rostedt wrote:
On Wed, Feb 23, 2011 at 12:44:14PM -0500, Glauber Costa wrote:
We've been supporting kvmclock MSRs in the
On Thu, 2011-02-24 at 18:24 -0500, Steven Rostedt wrote:
On Wed, Feb 23, 2011 at 12:44:14PM -0500, Glauber Costa wrote:
We've been supporting kvmclock MSRs in the 0x4b564d00-0x4b564dff range
for a while now, but we're not exposing it yet, meaning nobody is using it.
This simple patch takes
On Thu, 2011-02-24 at 20:48 -0300, Glauber Costa wrote:
On Thu, 2011-02-24 at 18:24 -0500, Steven Rostedt wrote:
On Wed, Feb 23, 2011 at 12:44:14PM -0500, Glauber Costa wrote:
We've been supporting kvmclock MSRs in the 0x4b564d00-0x4b564dff range
for a while now, but we're not exposing it
We've been supporting kvmclock MSRs in the 0x4b564d00-0x4b564dff range
for a while now, but we're not exposing it yet, meaning nobody is using it.
This simple patch takes care of that.
Signed-off-by: Glauber Costa glom...@redhat.com
---
arch/x86/kvm/x86.c |1 +
include/linux/kvm.h |1 +
