From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 217379] Latency issues in irq_bypass_register_consumer
Date: Fri, 04 Apr 2025 21:26:41 +0000 [thread overview]
Message-ID: <bug-217379-28872-iXqvlQbQMV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217379-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217379
Sean Christopherson (seanjc@google.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |seanjc@google.com
--- Comment #3 from Sean Christopherson (seanjc@google.com) ---
Huh. Rereading this almost two years later, I realized I completely missed
that (a) your setup wasn't actually using irqbypass and (b) you suggested
giving userspace a way to disable irqbypass in KVM when it couldn't possibly be
utilized.
I've proposed adding a module param for other reasons[1]. If that doesn't
suffice, KVM could also provide KVM_IRQFD_FLAG_NO_IRQBYPASS (which would also
be useful for other reasons).
As for the ugly latency problems, I posted a new patch to use xarray to
mitigate the issue[2].
[1] https://lore.kernel.org/all/20250401161804.842968-1-seanjc@google.com
[2] https://lore.kernel.org/all/20250404211449.1443336-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.
prev parent reply other threads:[~2025-04-04 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 7:27 [Bug 217379] New: Latency issues in irq_bypass_register_consumer bugzilla-daemon
2023-05-01 16:51 ` Sean Christopherson
2023-07-17 11:58 ` Like Xu
2023-07-17 15:25 ` Paolo Bonzini
2023-07-18 3:43 ` Like Xu
2023-07-18 9:51 ` Paolo Bonzini
2023-05-01 16:51 ` [Bug 217379] " bugzilla-daemon
2023-05-11 9:59 ` bugzilla-daemon
2025-04-04 21:26 ` bugzilla-daemon [this message]
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-217379-28872-iXqvlQbQMV@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