From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 218259] High latency in KVM guests
Date: Thu, 11 Jan 2024 15:55:08 +0000 [thread overview]
Message-ID: <bug-218259-28872-CSzJkkb9cN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218259-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218259
--- Comment #8 from Sean Christopherson (seanjc@google.com) ---
On Mon, Dec 18, 2023, bugzilla-daemon@kernel.org wrote:
> > I think the kernel is preemptible:
>
> Ya, not fully preemptible (voluntary only), but the important part is that
> KVM
> will drop mmu_lock if there is contention (which is a "requirement" for the
> bug
> that Yan encountered).
For posterity, the above is wrong. Volutary preemption isn't _supposed_ to
enable
yielding of contended spinlocks/rwlocks, but due to a bug with dynamic
preemption,
the behavior got enabled for all preempt models:
https://lore.kernel.org/all/20240110214723.695930-1-seanjc@google.com
--
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:[~2024-01-11 15:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 16:37 [Bug 218259] New: High latency in KVM guests bugzilla-daemon
2023-12-13 16:54 ` Sean Christopherson
2023-12-13 16:54 ` [Bug 218259] " bugzilla-daemon
2023-12-14 7:14 ` bugzilla-daemon
2023-12-18 17:07 ` Sean Christopherson
2023-12-14 7:15 ` bugzilla-daemon
2023-12-14 7:16 ` bugzilla-daemon
2023-12-18 17:07 ` bugzilla-daemon
2024-01-11 15:55 ` Sean Christopherson
2023-12-19 14:09 ` bugzilla-daemon
2023-12-19 15:16 ` Sean Christopherson
2023-12-19 15:16 ` bugzilla-daemon
2024-01-11 15:55 ` bugzilla-daemon [this message]
2024-01-16 13:29 ` bugzilla-daemon
2024-01-17 1:05 ` Sean Christopherson
2024-01-17 1:05 ` bugzilla-daemon
2024-01-17 14:04 ` bugzilla-daemon
2024-11-05 0:27 ` 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-218259-28872-CSzJkkb9cN@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 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.