From: "Naveen N Rao (AMD)" <naveen@kernel.org>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: <kvm@vger.kernel.org>, Jim Mattson <jmattson@google.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
Vasant Hegde <vasant.hegde@amd.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Nikunj A Dadhania <nikunj@amd.com>,
Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
Joao Martins <joao.m.martins@oracle.com>,
"Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>
Subject: [RFC PATCH v2 0/5] KVM: SVM: Enable AVIC by default on Zen 4+
Date: Thu, 4 Sep 2025 23:30:37 +0530 [thread overview]
Message-ID: <cover.1756993734.git.naveen@kernel.org> (raw)
This is v2 of the RFC posted here:
http://lkml.kernel.org/r/20250626145122.2228258-1-naveen@kernel.org
I have split up the patches and incorporated feedback on the RFC. This
still depends on at least two other fixes:
- Reducing SVM IRQ Window inhibit lock contention:
http://lkml.kernel.org/r/cover.1752819570.git.naveen@kernel.org
- Fixing TPR handling when AVIC is active:
http://lkml.kernel.org/r/cover.1756139678.git.maciej.szmigiero@oracle.com
- Naveen
Naveen N Rao (AMD) (5):
KVM: SVM: Stop warning if x2AVIC feature bit alone is enabled
KVM: SVM: Simplify the message printed with 'force_avic'
KVM: SVM: Move all AVIC setup to avic_hardware_setup()
KVM: SVM: Move 'force_avic' module parameter to svm.c
KVM: SVM: Enable AVIC by default from Zen 4
arch/x86/kvm/svm/svm.h | 3 ++-
arch/x86/kvm/svm/avic.c | 48 ++++++++++++++++++-----------------------
arch/x86/kvm/svm/svm.c | 22 +++++++++++++------
3 files changed, 38 insertions(+), 35 deletions(-)
base-commit: ecbcc2461839e848970468b44db32282e5059925
--
2.50.1
next reply other threads:[~2025-09-04 18:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 18:00 Naveen N Rao (AMD) [this message]
2025-09-04 18:00 ` [RFC PATCH v2 1/5] KVM: SVM: Stop warning if x2AVIC feature bit alone is enabled Naveen N Rao (AMD)
2025-09-15 20:04 ` Sean Christopherson
2025-09-16 7:14 ` Naveen N Rao
2025-09-16 13:40 ` Mario Limonciello
2025-09-16 13:51 ` Sean Christopherson
2025-09-16 18:37 ` Naveen N Rao
2025-09-16 19:26 ` Mario Limonciello
2025-09-17 0:44 ` Sean Christopherson
2025-09-04 18:00 ` [RFC PATCH v2 2/5] KVM: SVM: Simplify the message printed with 'force_avic' Naveen N Rao (AMD)
2025-09-15 22:42 ` Sean Christopherson
2025-09-04 18:00 ` [RFC PATCH v2 3/5] KVM: SVM: Move all AVIC setup to avic_hardware_setup() Naveen N Rao (AMD)
2025-09-15 19:59 ` Sean Christopherson
2025-09-04 18:00 ` [RFC PATCH v2 4/5] KVM: SVM: Move 'force_avic' module parameter to svm.c Naveen N Rao (AMD)
2025-09-15 22:43 ` Sean Christopherson
2025-09-04 18:00 ` [RFC PATCH v2 5/5] KVM: SVM: Enable AVIC by default from Zen 4 Naveen N Rao (AMD)
2025-09-15 22:53 ` Sean Christopherson
2025-09-16 7:39 ` Naveen N Rao
2025-09-16 14:27 ` Sean Christopherson
2025-09-16 18:53 ` Naveen N Rao
2025-09-15 23:17 ` Sean Christopherson
2025-09-16 10:17 ` Naveen N Rao
2025-09-15 23:23 ` [RFC PATCH v2 0/5] KVM: SVM: Enable AVIC by default on Zen 4+ Sean Christopherson
2025-09-16 10:31 ` Naveen N Rao
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=cover.1756993734.git.naveen@kernel.org \
--to=naveen@kernel.org \
--cc=alejandro.j.jimenez@oracle.com \
--cc=jmattson@google.com \
--cc=joao.m.martins@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=maciej.szmigiero@oracle.com \
--cc=mlevitsk@redhat.com \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
/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.