Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: "Garg, Shivank" <shivankg@amd.com>
To: "pbonzini@redhat.com" <pbonzini@redhat.com>,
	"seanjc@google.com" <seanjc@google.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 6/7] KVM: selftests: Automatically run xAPIC IPI migration test when possible
Date: Sun, 6 Sep 2026 18:01:01 +0000	[thread overview]
Message-ID: <1f4005631738e2f118956f53dac1997b68ad999a.camel@amd.com> (raw)
In-Reply-To: <20260903001625.2792367-7-seanjc@google.com>

On Wed, 2026-09-02 at 17:16 -0700, Sean Christopherson wrote:
> Rework the interface to the xAPIC IPI test to automatically run the
> migration testcase if at least two NUMA nodes are found.  The test exists
> specifically to validate KVM's handling of migration of the APIC backing
> page, i.e. forcing end users to opt-in to running the test in migration
> mode largely defeats the purpose of the test.
> 
> Run both the "sleeping" and "migration" testcases by default, e.g. so that
> the more basic testcase will fail if KVM completely breaks IPI delivery.
> 
> Keep the -m / migration parameter so that infrastructure that wants to
> specifically test the migration case can do so and not get false passes.
> 
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
>  .../selftests/kvm/x86/xapic_ipi_test.c        | 40 +++++++++++++------
>  1 file changed, 27 insertions(+), 13 deletions(-)
> 
> diff --git a/tools/testing/selftests/kvm/x86/xapic_ipi_test.c b/tools/testing/selftests/kvm/x86/xapic_ipi_test.c
> index 42c601617f5a..c5b506eb5e7f 100644
> --- a/tools/testing/selftests/kvm/x86/xapic_ipi_test.c
> +++ b/tools/testing/selftests/kvm/x86/xapic_ipi_test.c
> @@ -245,14 +245,13 @@ void do_migrations(struct test_data_page *data, int run_secs, int delay_usecs,
>  		delay_usecs);
>  
>  	nodes = kvm_get_numa_memory_nodes(&nodemask);
> +	TEST_ASSERT(nodes > 1,
> +		    "NUMA nodes disappeared?  nodemask = 0x%lx", nodemask);
>  
>  	fprintf(stderr, "Numa nodes found amongst first %lu possible nodes "
>  		"(each 1-bit indicates node is present): %#lx\n",
>  		BITS_PER_TYPE(nodemask), nodemask);
>  
> -	TEST_ASSERT(nodes > 1,
> -		    "Did not find at least 2 numa nodes. Can't do migration");
> -
>  	fprintf(stderr, "Migrating amongst %d nodes found\n", nodes);
>  
>  	from = kvm_get_next_numa_node(nodemask, -1);
> @@ -351,26 +350,17 @@ void get_cmdline_args(int argc, char *argv[], int *run_secs,
>  	}
>  }
>  
> -int main(int argc, char *argv[])
> +static void test_xapic_ipi(int run_secs, int delay_usecs, bool migrate)
>  {
>  	int wait_secs;
>  	const int max_halter_wait = 10;
> -	int run_secs = 0;
> -	int delay_usecs = 0;
>  	struct test_data_page *data;
>  	gva_t test_data_page_gva;
> -	bool migrate = false;
>  	pthread_t threads[2];
>  	struct thread_params params[2];
>  	struct kvm_vm *vm;
>  	u64 *pipis_rcvd;
>  
> -	get_cmdline_args(argc, argv, &run_secs, &migrate, &delay_usecs);
> -	if (run_secs <= 0)
> -		run_secs = DEFAULT_RUN_SECS;
> -	if (delay_usecs <= 0)
> -		delay_usecs = DEFAULT_DELAY_USECS;
> -
>  	vm = vm_create_with_one_vcpu(&params[0].vcpu, halter_guest_code);
>  
>  	vm_install_exception_handler(vm, IPI_VECTOR, guest_ipi_handler);
> @@ -458,5 +448,29 @@ int main(int argc, char *argv[])
>  
>  	kvm_vm_free(vm);
>  
> +}
> +
> +int main(int argc, char *argv[])
> +{
> +	bool force_migrate = false;
> +	unsigned long nodemask;
> +	int run_secs = 0;
> +	int delay_usecs = 0;
> +
> +	get_cmdline_args(argc, argv, &run_secs, &force_migrate, &delay_usecs);
> +	if (run_secs <= 0)
> +		run_secs = DEFAULT_RUN_SECS;
> +	if (delay_usecs <= 0)
> +		delay_usecs = DEFAULT_DELAY_USECS;
> +
> +	if (!force_migrate)
> +		test_xapic_ipi(run_secs, delay_usecs, false);
> +
> +	if (kvm_get_numa_memory_nodes(&nodemask) > 1)
> +		test_xapic_ipi(run_secs, delay_usecs, true);
> +	else
> +		TEST_ASSERT(!force_migrate,
> +			    "Did not find at least 2 numa nodes. Can't do migration");
> +
>  	return 0;
>  }


Reviewed-by: Shivank Garg <shivankg@amd.com>

Thanks,
Shivank

  reply	other threads:[~2026-09-06 18:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  0:16 [PATCH 0/7] KVM: selftests: Fix maxnodes bugs and cleanup related code Sean Christopherson
2026-09-03  0:16 ` [PATCH 1/7] KVM: selftests: Account for kernel's off-by-one bug in NUMA node syscalls Sean Christopherson
2026-09-06 10:08   ` Garg, Shivank
2026-09-03  0:16 ` [PATCH 2/7] KVM: selftests: Fix maxnode argument to migrate_pages() in xapic_ipi_test Sean Christopherson
2026-09-03  0:16 ` [PATCH 3/7] KVM: selftests: use BITS_PER_TYPE() for NUMA masks Sean Christopherson
2026-09-03  0:16 ` [PATCH 4/7] KVM: selftests: Compute node masks on-demand in xAPIC IPI test Sean Christopherson
2026-09-06 17:05   ` Garg, Shivank
2026-09-03  0:16 ` [PATCH 5/7] KVM: selftests: Add common helper to get mask+number of usable memory NUMA nodes Sean Christopherson
2026-09-06 17:53   ` Garg, Shivank
2026-09-03  0:16 ` [PATCH 6/7] KVM: selftests: Automatically run xAPIC IPI migration test when possible Sean Christopherson
2026-09-06 18:01   ` Garg, Shivank [this message]
2026-09-03  0:16 ` [PATCH 7/7] KVM: selftests: Skip xAPIC IPI migration test when forced but unsupported Sean Christopherson
2026-09-06 18:13   ` Garg, Shivank

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=1f4005631738e2f118956f53dac1997b68ad999a.camel@amd.com \
    --to=shivankg@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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