From: "Naveen N Rao (AMD)" <naveen@kernel.org>
To: <kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Vasant Hegde <vasant.hegde@amd.com>
Subject: [PATCH v2 0/2] KVM: SVM: Add support for 4096 vcpus with x2AVIC
Date: Mon, 3 Feb 2025 12:07:44 +0530 [thread overview]
Message-ID: <cover.1738563890.git.naveen@kernel.org> (raw)
Patch 1 adds support for up to 4096 vcpus with x2AVIC, and is unchanged
since v1:
http://lkml.kernel.org/r/20241008171156.11972-1-suravee.suthikulpanit@amd.com
Patch 2 is new and limits the value that is programmed into
AVIC_PHYSICAL_MAX_INDEX in the VMCB based on the max APIC ID indicated
by the VMM.
- Naveen
Naveen N Rao (AMD) (1):
KVM: SVM: Limit AVIC physical max index based on configured
max_vcpu_ids
Suravee Suthikulpanit (1):
KVM: SVM: Increase X2AVIC limit to 4096 vcpus
arch/x86/include/asm/svm.h | 4 ++
arch/x86/kvm/svm/avic.c | 82 ++++++++++++++++++++++++++++----------
arch/x86/kvm/svm/svm.c | 6 +++
arch/x86/kvm/svm/svm.h | 1 +
4 files changed, 73 insertions(+), 20 deletions(-)
base-commit: eb723766b1030a23c38adf2348b7c3d1409d11f0
--
2.48.1
next reply other threads:[~2025-02-03 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 6:37 Naveen N Rao (AMD) [this message]
2025-02-03 6:37 ` [PATCH v2 1/2] KVM: SVM: Increase X2AVIC limit to 4096 vcpus Naveen N Rao (AMD)
2025-02-03 6:37 ` [PATCH v2 2/2] KVM: SVM: Limit AVIC physical max index based on configured max_vcpu_ids Naveen N Rao (AMD)
2025-02-03 11:41 ` kernel test robot
2025-02-03 18:08 ` kernel test robot
2025-02-03 21:06 ` kernel test robot
2025-02-05 6:48 ` Vasant Hegde
2025-02-06 9:12 ` 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.1738563890.git.naveen@kernel.org \
--to=naveen@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).