Home
last modified time | relevance | path

Searched hist:"168 d918f2643d7d3f0240e768d40b4f8aba3540a" (Results 1 – 3 of 3) sorted by relevance

/openbmc/linux/arch/x86/kvm/
H A Dpmu.hdiff 168d918f2643d7d3f0240e768d40b4f8aba3540a Fri Feb 21 20:34:13 CST 2020 Eric Hankland <ehankland@google.com> KVM: x86: Adjust counter sample period after a wrmsr

The sample_period of a counter tracks when that counter will
overflow and set global status/trigger a PMI. However this currently
only gets set when the initial counter is created or when a counter is
resumed; this updates the sample period after a wrmsr so running
counters will accurately reflect their new value.

Signed-off-by: Eric Hankland <ehankland@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
H A Dpmu.cdiff 168d918f2643d7d3f0240e768d40b4f8aba3540a Fri Feb 21 20:34:13 CST 2020 Eric Hankland <ehankland@google.com> KVM: x86: Adjust counter sample period after a wrmsr

The sample_period of a counter tracks when that counter will
overflow and set global status/trigger a PMI. However this currently
only gets set when the initial counter is created or when a counter is
resumed; this updates the sample period after a wrmsr so running
counters will accurately reflect their new value.

Signed-off-by: Eric Hankland <ehankland@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
/openbmc/linux/arch/x86/kvm/vmx/
H A Dpmu_intel.cdiff 168d918f2643d7d3f0240e768d40b4f8aba3540a Fri Feb 21 20:34:13 CST 2020 Eric Hankland <ehankland@google.com> KVM: x86: Adjust counter sample period after a wrmsr

The sample_period of a counter tracks when that counter will
overflow and set global status/trigger a PMI. However this currently
only gets set when the initial counter is created or when a counter is
resumed; this updates the sample period after a wrmsr so running
counters will accurately reflect their new value.

Signed-off-by: Eric Hankland <ehankland@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>