Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1268735

Re: [PATCH] KVM: x86: expose MSR_TSC_AUX to userspace

From Paolo Bonzini <pbonzini@redhat.com>
Newsgroups linux.kernel
Subject Re: [PATCH] KVM: x86: expose MSR_TSC_AUX to userspace
Date 2015-11-13 10:50 +0100
Message-ID <quj9w-4FD-11@gated-at.bofh.it> (permalink)
References <qu0qe-16P-7@gated-at.bofh.it> <qu0qe-16P-13@gated-at.bofh.it> <quj9w-4FD-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


> Paolo, under what circumstances (which versions of Windows? Anything
> special running in the guest?) has this failure happened? I'd like to repro
> this, I'm not sure if we've observed it before.

We saw it with migration under Windows 10, nothing special running in the
guest.  It's very hard to reproduce, we've only seen it once but the BSOD
parameters provided surprisingly good evidence:

----------------------------------
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a01f58a88e3638, Reserved
Arg2: b3b72bdefb0f076f, Reserved
Arg3: 00000001c0000103, Failure type dependent information
Arg4: 0000000000000007, Type of corrupted region, can be
	...
	7   : Critical MSR modification
----------------------------------

Argument 1 and 2 might be related to the old and new value (perhaps some
kind of hash).

Argument 3 is not documented either, but the low 32 bits look a lot like
the MSR_TSC_AUX index. :)

Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH] KVM: svm: add support for RDTSCP Paolo Bonzini <pbonzini@redhat.com> - 2015-11-12 14:50 +0100
  [PATCH] KVM: x86: expose MSR_TSC_AUX to userspace Paolo Bonzini <pbonzini@redhat.com> - 2015-11-12 14:50 +0100
    Re: [PATCH] KVM: x86: expose MSR_TSC_AUX to userspace Paolo Bonzini <pbonzini@redhat.com> - 2015-11-13 10:50 +0100
      Re: [PATCH] KVM: x86: expose MSR_TSC_AUX to userspace Peter Hornyack <peterhornyack@google.com> - 2015-11-13 18:50 +0100
  Re: [PATCH] KVM: svm: add support for RDTSCP Joerg Roedel <joro@8bytes.org> - 2015-11-12 15:50 +0100
    Re: [PATCH] KVM: svm: add support for RDTSCP Paolo Bonzini <pbonzini@redhat.com> - 2015-11-12 17:20 +0100

csiph-web