From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Cc: Ingo Molnar <mingo@kernel.org>,
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: Wed, 2 Sep 2015 05:50:40 +0200 [thread overview]
Message-ID: <20150902035040.GA420@x4> (raw)
In-Reply-To: <55E6273D.6080701@linux.intel.com>
On 2015.09.02 at 06:31 +0800, Xiao Guangrong wrote:
>
>
> On 09/01/2015 09:56 PM, Markus Trippelsdorf wrote:
> > On 2015.09.01 at 21:00 +0800, Xiao Guangrong wrote:
> >>
> >> Did it trigger the BUG()/BUG_ON() in mtrr2protval()/fallback_mtrr_type()?
> >> If yes, could you please print the actual value out?
> >
> > It is the BUG() in fallback_mtrr_type(). I changed it to a printk and
> > it prints 1 for the value of mtrr.
> >
> > MTRR_TYPE_WRCOMB 1
> >
>
> Then I suspect pat is not enabled in your box, could you please check
> CONFIG_X86_PAT is selected in your .config file, pat is shown in
> /proc/cpuid, "nopat" kernel parameter is used, and dmesg | grep PAT.
No. PAT is of course enabled and booting is successful sometimes even
with the BUG() in allback_mtrr_type(). I suspect a setup (timing) issue.
markus@x4 linux % cat .config | grep X86_PAT
CONFIG_X86_PAT=y
markus@x4 linux % dmesg | grep PAT
[ 0.000000] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT
markus@x4 linux % cat /proc/cpuinfo| grep pat
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate npt lbrv svm_lock nrip_save vmmcall
...
--
Markus
next prev parent reply other threads:[~2015-09-02 3:50 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 ` commit 3c2e7f7de3 (KVM use NPT page attributes) causes boot failures Markus Trippelsdorf
2015-09-01 13:00 ` Xiao Guangrong
2015-09-01 13:56 ` Markus Trippelsdorf
2015-09-01 22:31 ` Xiao Guangrong
2015-09-02 3:50 ` Markus Trippelsdorf [this message]
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=20150902035040.GA420@x4 \
--to=markus@trippelsdorf.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=guangrong.xiao@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.