From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 209079] CPU 0/KVM: page allocation failure on 5.8 kernel
Date: Wed, 09 Sep 2020 06:41:20 +0000 [thread overview]
Message-ID: <bug-209079-28872-gJV3XpdGDm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209079-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209079
Sean Christopherson (sean.j.christopherson@intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sean.j.christopherson@intel
| |.com
--- Comment #2 from Sean Christopherson (sean.j.christopherson@intel.com) ---
Are you disabling NPT (via KVM module param)? You're obviously running a
64-bit kernel, and presumably that CPU supports NPT, so the only way KVM should
reach the failing allocation is if NPT is being explicitly disabled. There's
nothing wrong with using shadow paging, it's just uncommon these days.
NPT aside, the interesting part of the failing allocation is that it uses
GFP_DMA32. I did a quick test to force that allocation on my system and
nothing exploded. Odds are good the bug is outside of KVM, which means a
bisection is probably necessary.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-09-09 6:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 15:22 [Bug 209079] New: CPU 0/KVM: page allocation failure on 5.8 kernel bugzilla-daemon
2020-09-09 6:00 ` [Bug 209079] " bugzilla-daemon
2020-09-09 6:41 ` bugzilla-daemon [this message]
2020-09-10 15:33 ` bugzilla-daemon
2020-09-10 16:21 ` bugzilla-daemon
2020-09-10 21:03 ` bugzilla-daemon
2020-09-11 16:19 ` bugzilla-daemon
2020-09-20 9:17 ` bugzilla-daemon
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=bug-209079-28872-gJV3XpdGDm@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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).