From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 203979] kvm_spurious_fault in L1 when running a nested kvm instance on AMD i686-pae
Date: Sun, 30 Jun 2019 23:03:11 +0000 [thread overview]
Message-ID: <bug-203979-28872-Zy5CFsTk5r@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203979-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203979
Jiri Palecek (jpalecek@web.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |karahmed@amazon.de
--- Comment #1 from Jiri Palecek (jpalecek@web.de) ---
So, I have bisected this and found the culprit to be:
commit 8c5fbf1a723107814c20c3f4d6343ab9d694a705 (refs/bisect/bad)
Author: KarimAllah Ahmed <karahmed@amazon.de>
Date: Thu Jan 31 21:24:40 2019 +0100
KVM/nSVM: Use the new mapping API for mapping guest memory
Use the new mapping API for mapping guest memory to avoid depending on
"struct page".
Signed-off-by: KarimAllah Ahmed <karahmed@amazon.de>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-06-30 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 19:09 [Bug 203979] New: kvm_spurious_fault in L1 when running a nested kvm instance on AMD i686-pae bugzilla-daemon
2019-06-30 23:03 ` bugzilla-daemon [this message]
2019-06-30 23:17 ` [Bug 203979] " bugzilla-daemon
2019-07-03 9:45 ` bugzilla-daemon
2019-08-09 15:43 ` 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-203979-28872-Zy5CFsTk5r@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).