On 01/07/2015 18:06, Peter Hornyack wrote:
If userspace is controlling the crash capabilities then
HV_X64_MSR_CRASH_CTL_CONTENTS is not needed.
Actually you still need to: userspace cannot write anything but 0 or
(1ULL 63). However, the name makes less sense, so I'm in favor of
removing the
On 01/07/15 18:00, Paolo Bonzini wrote:
On 30/06/2015 13:33, Denis V. Lunev wrote:
+#define HV_X64_MSR_CRASH_CTL_NOTIFY(1ULL 63)
+#define HV_X64_MSR_CRASH_CTL_CONTENTS \
+ (HV_X64_MSR_CRASH_CTL_NOTIFY)
Why is HV_X64_MSR_CRASH_CTL_CONTENTS needed? Can I just remove
On 30/06/2015 13:33, Denis V. Lunev wrote:
+#define HV_X64_MSR_CRASH_CTL_NOTIFY (1ULL 63)
+#define HV_X64_MSR_CRASH_CTL_CONTENTS\
+ (HV_X64_MSR_CRASH_CTL_NOTIFY)
Why is HV_X64_MSR_CRASH_CTL_CONTENTS needed? Can I just remove it?
Paolo
--
To unsubscribe from
If userspace is controlling the crash capabilities then
HV_X64_MSR_CRASH_CTL_CONTENTS is not needed.
On Wed, Jul 1, 2015 at 8:53 AM, Denis V. Lunev d...@openvz.org wrote:
On 01/07/15 18:00, Paolo Bonzini wrote:
On 30/06/2015 13:33, Denis V. Lunev wrote:
+#define HV_X64_MSR_CRASH_CTL_NOTIFY
On Tue, Jun 30, 2015 at 4:33 AM, Denis V. Lunev d...@openvz.org wrote:
From: Andrey Smetanin asmeta...@virtuozzo.com
Added Hyper-V crash msrs values - HV_X64_MSR_CRASH*.
Signed-off-by: Andrey Smetanin asmeta...@virtuozzo.com
Signed-off-by: Denis V. Lunev d...@openvz.org
CC: Paolo Bonzini
From: Andrey Smetanin asmeta...@virtuozzo.com
Added Hyper-V crash msrs values - HV_X64_MSR_CRASH*.
Signed-off-by: Andrey Smetanin asmeta...@virtuozzo.com
Signed-off-by: Denis V. Lunev d...@openvz.org
CC: Paolo Bonzini pbonz...@redhat.com
CC: Gleb Natapov g...@kernel.org
---
