From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
kvm@vger.kernel.org, avinashlalotra <abinashlalotra@gmail.com>
Cc: linux-kernel@vger.kernel.org, vkuznets@redhat.com,
pbonzini@redhat.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, avinashlalotra <abinashsinghlalotra@gmail.com>
Subject: Re: [RFC PATCH] KVM: x86: Dynamically allocate bitmap to fix -Wframe-larger-than error
Date: Tue, 24 Jun 2025 12:36:26 -0700 [thread overview]
Message-ID: <175079250757.516293.17591190576479567167.b4-ty@google.com> (raw)
In-Reply-To: <aEylI-O8kFnFHrOH@google.com>
On Fri, Jun 13, 2025, Sean Christopherson wrote:
> Use a preallocated per-vCPU bitmap for tracking the unpacked set of vCPUs
> being targeted for Hyper-V's paravirt TLB flushing. If KVM_MAX_NR_VCPUS
> is set to 4096 (which is allowed even for MAXSMP=n builds), putting the
> vCPU mask on-stack pushes kvm_hv_flush_tlb() past the default FRAME_WARN
> limit.
>
> [...]
Applied my version to kvm-x86 fixes, thanks!
[1/1] KVM: x86/hyper-v: Use preallocated per-vCPU buffer for de-sparsified vCPU masks
https://github.com/kvm-x86/linux/commit/4bbcc07a56e6
--
https://github.com/kvm-x86/kvm-unit-tests/tree/next
prev parent reply other threads:[~2025-06-24 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 11:10 avinashlalotra
2025-06-13 11:25 ` Paolo Bonzini
2025-06-13 13:58 ` Sean Christopherson
2025-06-13 17:17 ` Abinash
2025-06-13 22:24 ` Sean Christopherson
2025-06-24 19:36 ` 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=175079250757.516293.17591190576479567167.b4-ty@google.com \
--to=seanjc@google.com \
--cc=abinashlalotra@gmail.com \
--cc=abinashsinghlalotra@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®