| author | Dirk Müller <dmueller@suse.com> | |
| Thu, 1 Oct 2015 11:43:42 +0000 (13:43 +0200) | ||
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | |
| Thu, 22 Oct 2015 21:39:18 +0000 (14:39 -0700) | ||
| commit | 3fd49abb844ff3b97cdc041a73f025288cf75af0 | |
| tree | fab1f945f3bca0b2173bf34d89a8c073cafd7c33 | tree | snapshot (tar.xz tar.gz zip) |
| parent | 76bdbeab6899465e47817b70b16eae5f5b6d9f19 | commit | diff |
Use WARN_ON_ONCE for missing X86_FEATURE_NRIPS
commit d2922422c48df93f3edff7d872ee4f3191fefb08 upstream.
The cpu feature flags are not ever going to change, so warning
everytime can cause a lot of kernel log spam
(in our case more than 10GB/hour).
The warning seems to only occur when nested virtualization is
enabled, so it's probably triggered by a KVM bug. This is a
sensible and safe change anyway, and the KVM bug fix might not
be suitable for stable releases anyway.
Signed-off-by: Dirk Mueller <dmueller@suse.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
commit d2922422c48df93f3edff7d872ee4f3191fefb08 upstream.
The cpu feature flags are not ever going to change, so warning
everytime can cause a lot of kernel log spam
(in our case more than 10GB/hour).
The warning seems to only occur when nested virtualization is
enabled, so it's probably triggered by a KVM bug. This is a
sensible and safe change anyway, and the KVM bug fix might not
be suitable for stable releases anyway.
Signed-off-by: Dirk Mueller <dmueller@suse.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| arch/x86/kvm/svm.c | diff | blob | history |