From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Galbraith <efault@gmx.de>, Joerg Roedel <jroedel@suse.de>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org
Subject: Re: commit 3c2e7f7de3 (KVM use NPT page attributes) causes boot failures
Date: Tue, 1 Sep 2015 12:04:17 +0200 [thread overview]
Message-ID: <20150901100417.GA424@x4> (raw)
In-Reply-To: <20150901085627.GF6315@gmail.com>
On 2015.09.01 at 10:56 +0200, Ingo Molnar wrote:
>
> * Markus Trippelsdorf <markus@trippelsdorf.de> wrote:
> > As I wrote in my other reply. The boot failure is nondeterministic (boot
> > succeeds roughly every sixth time). So the bisection and the patch is
> > just bogus (,but the boot failure is real).
> >
> > Sorry.
>
> No problem. Please let us know if any of these commits does turn out to be the
> culprit. (Which is always a possibility.)
I'm pretty sure commit 3c2e7f7de3 is the culprit.
commit 3c2e7f7de3240216042b61073803b61b9b3cfb22
Author: Paolo Bonzini <pbonzini@redhat.com>
Date: Tue Jul 7 14:32:17 2015 +0200
KVM: SVM: use NPT page attributes
I've booted ten times in a row successfully with the following patch:
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index 74d825716f4f..3190173a575f 100644
--- a/arch/x86/kvm/svm.c
+++ b/arch/x86/kvm/svm.c
@@ -989,7 +989,7 @@ static __init int svm_hardware_setup(void)
} else
kvm_disable_tdp();
- build_mtrr2protval();
+// build_mtrr2protval();
return 0;
err:
Paolo, your commit causes nondeterministic boot failure on my machine.
It sometimes crashes early with the following backtrace:
map_vsyscall
kvm_arch_hardware_setup
map_vsyscall
kvm_init
map_vsyscall
do_one_initcall
kernel_init_freeable
rest_init
kernel_init
ret_from_fork
rest_init
RIP: svm_hardware_setup
--
Markus
next prev parent reply other threads:[~2015-09-01 10:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 17:24 [GIT PULL] scheduler changes for v4.3 Ingo Molnar
2015-09-01 7:08 ` Markus Trippelsdorf
2015-09-01 7:27 ` Ingo Molnar
2015-09-01 7:44 ` Markus Trippelsdorf
2015-09-01 8:38 ` Ingo Molnar
2015-09-01 8:44 ` Markus Trippelsdorf
2015-09-01 8:56 ` Ingo Molnar
2015-09-01 10:04 ` Markus Trippelsdorf [this message]
2015-09-01 13:00 ` commit 3c2e7f7de3 (KVM use NPT page attributes) causes boot failures Xiao Guangrong
2015-09-01 13:56 ` Markus Trippelsdorf
2015-09-01 22:31 ` Xiao Guangrong
2015-09-02 3:50 ` Markus Trippelsdorf
2015-09-02 9:17 ` Xiao Guangrong
2015-09-02 9:38 ` Markus Trippelsdorf
2015-09-02 10:27 ` Xiao Guangrong
2015-09-02 10:54 ` Markus Trippelsdorf
2015-09-02 10:57 ` Xiao Guangrong
2015-09-01 8:50 ` [GIT PULL] scheduler changes for v4.3 Markus Trippelsdorf
2015-09-01 8:18 ` Markus Trippelsdorf
2015-09-01 8:39 ` Markus Trippelsdorf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150901100417.GA424@x4 \
--to=markus@trippelsdorf.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).