From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Yosry Ahmed <yosry.ahmed@linux.dev>
Subject: [PATCH v2 0/3] KVM: x86: Add a module param for device posted IRQs
Date: Thu, 20 Mar 2025 07:20:19 -0700 [thread overview]
Message-ID: <20250320142022.766201-1-seanjc@google.com> (raw)
Add a module param, enable_device_posted_irqs, to control and enumerate
KVM support for device posted IRQs.
v2:
- Add prep patches to use kvm_arch_has_irq_bypass() in vendor code when
querying support IRQ bypass, a.k.a. device posted IRQs, so as not to
unexpectedly introduce a (desired) dependency on enable_apicv. [Yosry]
- Use "&=" when constraining enable_device_posted_irqs based on APICv
and IOMMU posting support. [Yosry]
v1: https://lore.kernel.org/all/20250315025615.2367411-1-seanjc@google.com
Sean Christopherson (3):
KVM: VMX: Don't send UNBLOCK when starting device assignment without
APICv
KVM: SVM: Don't update IRTEs if APICv/AVIC is disable
KVM: x86: Add a module param to control and enumerate device posted
IRQs
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/kvm/svm/avic.c | 3 +--
arch/x86/kvm/vmx/posted_intr.c | 7 +++----
arch/x86/kvm/x86.c | 10 +++++++++-
4 files changed, 14 insertions(+), 7 deletions(-)
base-commit: c9ea48bb6ee6b28bbc956c1e8af98044618fed5e
--
2.49.0.395.g12beb8f557-goog
next reply other threads:[~2025-03-20 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 14:20 Sean Christopherson [this message]
2025-03-20 14:20 ` [PATCH v2 1/3] KVM: VMX: Don't send UNBLOCK when starting device assignment without APICv Sean Christopherson
2025-03-20 14:20 ` [PATCH v2 2/3] KVM: SVM: Don't update IRTEs if APICv/AVIC is disable Sean Christopherson
2025-03-20 16:08 ` Jim Mattson
2025-03-20 14:20 ` [PATCH v2 3/3] KVM: x86: Add a module param to control and enumerate device posted IRQs Sean Christopherson
2025-03-20 16:02 ` Jim Mattson
2025-03-20 17:54 ` Sean Christopherson
2025-03-20 17:59 ` Sean Christopherson
2025-03-20 18:14 ` Yosry Ahmed
2025-03-21 1:57 ` Chao Gao
2025-03-21 20:44 ` Sean Christopherson
2025-03-24 9:26 ` Chao Gao
2025-03-24 13:41 ` Sean Christopherson
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=20250320142022.766201-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=yosry.ahmed@linux.dev \
/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