mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vasant Hegde <vasant.hegde@amd.com>
To: "Naveen N Rao (AMD)" <naveen@kernel.org>,
	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>
Subject: Re: [PATCH v3 0/2] KVM: SVM: Add support for 4096 vcpus with x2AVIC
Date: Thu, 20 Mar 2025 11:04:29 +0530	[thread overview]
Message-ID: <aac3b9ab-8dbf-424e-856a-d02135323c8b@amd.com> (raw)
In-Reply-To: <cover.1740036492.git.naveen@kernel.org>

On 2/20/2025 1:08 PM, Naveen N Rao (AMD) wrote:
> This is v3 of the series posted at:
> http://lkml.kernel.org/r/cover.1738563890.git.naveen@kernel.org
> 
> The first patch adds support for up to 4096 vcpus with x2AVIC, while the 
> second patch limits the value that is programmed into 
> AVIC_PHYSICAL_MAX_INDEX in the VMCB based on the max APIC ID indicated 
> by the VMM.

Reviewed-by: Vasant Hegde <vasant.hegde@amd.com>

-Vasant


      parent reply	other threads:[~2025-03-20  5:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20  7:38 Naveen N Rao (AMD)
2025-02-20  7:38 ` [PATCH v3 1/2] KVM: SVM: Increase X2AVIC limit to 4096 vcpus Naveen N Rao (AMD)
2025-06-23 23:17   ` Sean Christopherson
2025-07-18 10:21     ` Naveen N Rao
2025-07-18 14:24       ` Sean Christopherson
2025-07-21 14:11         ` Naveen N Rao
2025-07-21 22:26           ` Sean Christopherson
2025-02-20  7:38 ` [PATCH v3 2/2] KVM: SVM: Limit AVIC physical max index based on configured max_vcpu_ids Naveen N Rao (AMD)
2025-02-20 13:36   ` Gupta, Pankaj
2025-06-24  0:38   ` Sean Christopherson
2025-07-18 10:34     ` Naveen N Rao
2025-07-18 15:17       ` Sean Christopherson
2025-07-21 14:12         ` Naveen N Rao
2025-03-20  5:34 ` Vasant Hegde [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=aac3b9ab-8dbf-424e-856a-d02135323c8b@amd.com \
    --to=vasant.hegde@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveen@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=suravee.suthikulpanit@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

Powered by JetHome