From: Sean Christopherson <seanjc@google.com>
To: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
pbonzini@redhat.com, rkrcmar@redhat.com, jon.grimm@amd.com,
santosh.shukla@amd.com
Subject: Re: [PATCH] KVM: SVM: Increase X2AVIC limit to 4096 vcpus
Date: Thu, 31 Oct 2024 08:09:40 -0700 [thread overview]
Message-ID: <ZyOdtFzfARpJ8_fj@google.com> (raw)
In-Reply-To: <682cefa6-9a74-4b8b-97e2-38a1c58c6e72@amd.com>
On Thu, Oct 31, 2024, Suravee Suthikulpanit wrote:
> Hi All,
>
> Any concerns for this patch?
Don't know, I haven't looked closely. I am not planning on looking at this for
3+ weeks, as I want to sort out the KVM_CAP_MAX_VCPUS mess first[*], along with
a multitude of other bugs/flaws in the AVIC and posted interrupt code. I have
crude patches, but they need changelogs and more testing; I don't expect to post
them for at least 2 weeks.
[*] https://lore.kernel.org/all/20230815213533.548732-1-seanjc@google.com
prev parent reply other threads:[~2024-10-31 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 17:11 [PATCH] KVM: SVM: Increase X2AVIC limit to 4096 vcpus Suravee Suthikulpanit
2024-10-31 9:46 ` Suthikulpanit, Suravee
2024-10-31 15:09 ` Sean Christopherson [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=ZyOdtFzfARpJ8_fj@google.com \
--to=seanjc@google.com \
--cc=jon.grimm@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=santosh.shukla@amd.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 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.