From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 217304] KVM does not handle NMI blocking correctly in nested virtualization
Date: Fri, 07 Apr 2023 20:14:32 +0000 [thread overview]
Message-ID: <bug-217304-28872-a5z8K12AKP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217304-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217304
--- Comment #2 from Eric Li (lixiaoyi13691419520@gmail.com) ---
<bugzilla-daemon@kernel.org> 于2023年4月6日周四 15:14写道:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=217304
>
> --- Comment #1 from Sean Christopherson (seanjc@google.com) ---
> On Thu, Apr 06, 2023, bugzilla-daemon@kernel.org wrote:
> Ya, KVM blocks NMIs on nested NMI VM-Exits, but doesn't unblock NMIs for all
> other
> exit types. I believe this is the fix (untested):
>
Thanks for the fix. I tested it on Linux 5.19.14, and it passes my experiments.
Detail: I wrote 30 experiments (i.e., tests), numbered from 1 to 30.
Before this bug fix, KVM passes 21 experiments. After this bug fix,
KVM passes 3 more experiments (3, 13, and 14) without introducing any
regression in my experiments. There are 6 more experiments that KVM
still fails (2, 4, 6, 18, 19, and 24). I think we can address them in
another bug on Bugzilla.
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You are on the CC list for the bug.
> You reported the bug.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-04-07 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 4:09 [Bug 217304] New: KVM does not handle NMI blocking correctly in nested virtualization bugzilla-daemon
2023-04-06 19:14 ` Sean Christopherson
2023-04-06 19:14 ` [Bug 217304] " bugzilla-daemon
2023-04-12 17:00 ` Sean Christopherson
2023-04-07 20:14 ` bugzilla-daemon [this message]
2023-04-12 17:00 ` bugzilla-daemon
2023-04-12 20:50 ` 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-217304-28872-a5z8K12AKP@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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