All of lore.kernel.org
 help / color / mirror / Atom feed
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:17:46 +0000	[thread overview]
Message-ID: <bug-203979-28872-2NOYIB52Yo@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203979-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=203979

--- Comment #2 from Jiri Palecek (jpalecek@web.de) ---
Created attachment 283501
  --> https://bugzilla.kernel.org/attachment.cgi?id=283501&action=edit
Patch that allows me to run nested kvm instances again

After much looking on the offending commit, which doesn't seem to change any
functionality, but just changes the API, I found out the gfns used inside
__kvm_map_gfn were in fact far off. Further looking into it I found that these
gfns were the result of gfn_to_gpa in some (but not all) places that used the
new api. However, what was clearly meant was gpa_to_gfn. So I prepared this
patch and tested that it allows to run nested linux instances in kvm
successfully on my AMD system.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2019-06-30 23:20 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 ` [Bug 203979] " bugzilla-daemon
2019-06-30 23:17 ` bugzilla-daemon [this message]
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-2NOYIB52Yo@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 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.