From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 210695] error: kvm run failed Invalid argument
Date: Wed, 16 Dec 2020 02:03:28 +0000 [thread overview]
Message-ID: <bug-210695-28872-vQTu33nCVK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210695-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210695
Sean Christopherson (seanjc@google.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |seanjc@google.com
--- Comment #1 from Sean Christopherson (seanjc@google.com) ---
Hrm, this is more than likely related to refactoring for the introduction of
the TDP MMU.
> kernel get_mmio_spte: detect reserved bits on spte, addr 0xfe013000, dump
> hierarchy:
> kernel ------ spte 0x80000b0e level 3.
This SPTE looks odd/wrong, but unless I'm misreading things, there are no
reserved bits set.
> kernel ------ spte 0x49c0027 level 2.
> kernel ------ spte 0x38001ffe0134d7 level 1.
And this SPTE obviously has reserved bits set, but that's intentional and this
should not trigger the warning as the SPTE should be recognized as an MMIO
SPTE.
I'll stare at this more tomorrow and play with things a bit to see if I can
figure out what's broken.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-12-16 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 0:11 [Bug 210695] New: error: kvm run failed Invalid argument bugzilla-daemon
2020-12-15 0:13 ` [Bug 210695] " bugzilla-daemon
2020-12-16 2:03 ` bugzilla-daemon [this message]
2020-12-16 2:28 ` bugzilla-daemon
2020-12-16 2:57 ` bugzilla-daemon
2020-12-16 20:49 ` bugzilla-daemon
2020-12-16 23:08 ` bugzilla-daemon
2020-12-16 23:14 ` bugzilla-daemon
2020-12-17 19:54 ` bugzilla-daemon
2020-12-18 3:10 ` 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-210695-28872-vQTu33nCVK@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).