Received-SPF: pass (google.com: domain of linux-kernel+bounces-136113-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Date: Mon,  8 Apr 2024 19:01:23 -0700
In-Reply-To: <20240315143507.102629-1-mlevitsk@redhat.com>
Precedence: bulk
Mime-Version: 1.0
References: <20240315143507.102629-1-mlevitsk@redhat.com>
Message-ID: <171262713897.1419961.5139969748119275014.b4-ty@google.com>
Subject: Re: [PATCH] KVM: selftests: fix max_guest_memory_test with more that
 256 vCPUs
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>, kvm@vger.kernel.org, 
	Maxim Levitsky <mlevitsk@redhat.com>
Cc: linux-kernel@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>, 
	linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Content-Type: text/plain; charset="utf-8"

On Fri, 15 Mar 2024 10:35:07 -0400, Maxim Levitsky wrote:
> max_guest_memory_test uses ucalls to sync with the host, but
> it also resets the guest RIP back to its initial value in between
> tests stages.
> 
> This makes the guest never reach the code which frees the ucall struct
> and since a fixed pool of 512 ucall structs is used, the test starts
> to fail when more that 256 vCPUs are used.
> 
> [...]

Applied to kvm-x86 fixes, thanks!

[1/1] KVM: selftests: fix max_guest_memory_test with more that 256 vCPUs
      https://github.com/kvm-x86/linux/commit/0ef2dd1f4144

--
https://github.com/kvm-x86/linux/tree/next