All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Yosry Ahmed <yosry@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 10/12] KVM: selftests: Trigger save+restore randomly in the #PF stress test
Date: Tue, 28 Jul 2026 07:58:39 -0700	[thread overview]
Message-ID: <amjDn6fy8lgftsrE@google.com> (raw)
In-Reply-To: <20260727235228.1007324-11-yosry@kernel.org>

On Mon, Jul 27, 2026, Yosry Ahmed wrote:
>  int main(int argc, char *argv[])
>  {
>  	struct kvm_x86_state *state;
>  	int r, i, level;
> +	pthread_t sigusr_thread;
>  	gpa_t gpa, pgtable_gpa;
>  	struct kvm_vcpu *vcpu;
>  	struct kvm_vm *vm;
> @@ -128,18 +156,30 @@ int main(int argc, char *argv[])
>  		pgtable_gpa = PTE_GET_PA(pte);
>  	}
>  
> +	/* Initialize the thread sending SIGUSR and install the handler */
> +	vcpu_sigusr_ignore();
> +	r = pthread_create(&sigusr_thread, NULL, sigusr_thread_fn,
> +			   (void *)pthread_self());
> +	TEST_ASSERT(!r, "pthread_create() failed: %d", r);
> +
>  	for (i = 1; i <= NR_ITERATIONS; i++) {
> +		/*
> +		 * Only handle SIGUSR while the vCPU is running, otherwise
> +		 * ignore it to avoid interrupting other ioctls/syscalls.
> +		 */
> +		vcpu_sigusr_listen();
>  		r = __vcpu_run(vcpu);
> -		TEST_ASSERT(!r, "vcpu_run failed");
> -		TEST_ASSERT_KVM_EXIT_REASON(vcpu, KVM_EXIT_IO);
> -
> -		get_ucall(vcpu, &uc);
> -		if (uc.cmd == UCALL_ABORT) {
> +		if (r == -1)
> +			TEST_ASSERT_EQ(errno, EINTR);

		TEST_ASSERT(!r || errno == EINTR, "Expected success or SIGUSR1");

> +		vcpu_sigusr_ignore();
> +
> +		/* The guest only exits due to a signal or failed assertion */
> +		if (!r) {
> +			TEST_ASSERT_KVM_EXIT_REASON(vcpu, KVM_EXIT_IO);
> +			TEST_ASSERT_EQ(get_ucall(vcpu, &uc), UCALL_ABORT);
>  			REPORT_GUEST_ASSERT(uc);
>  			break;
>  		}
> -		TEST_ASSERT_EQ(uc.cmd, UCALL_SYNC);
> -		TEST_ASSERT_EQ(uc.args[1], i);
>  
>  		state = vcpu_save_state(vcpu);
>  
> @@ -153,8 +193,11 @@ int main(int argc, char *argv[])
>  	pr_info("\n");
>  
>  	sync_global_from_guest(vm, guest_faults);
> +	TEST_ASSERT(guest_faults > 0, "No guest page faults triggered");

Since guest_faults is an unsigned value, the kernel's preferred style is:

	TEST_ASSERT(guest_faults, "No guest page faults triggered");

>  	pr_info("Guest page faults: %lu\n", guest_faults);
>  
> +	pthread_cancel(sigusr_thread);
> +	pthread_join(sigusr_thread, NULL);
>  	kvm_vm_free(vm);
>  	return 0;
>  }
> -- 
> 2.55.0.229.g6434b31f56-goog
> 

  reply	other threads:[~2026-07-28 14:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 23:52 [PATCH v4 00/12] KVM: selftests: Stress save+restore and #PF (ft. nested) Yosry Ahmed
2026-07-27 23:52 ` [PATCH v4 01/12] KVM: selftests: Use __stringify() instead of custom XSTR() macros Yosry Ahmed
2026-07-27 23:52 ` [PATCH v4 02/12] KVM: selftests: Fix RAX and RFLAGS VMCB offsets when running L2 Yosry Ahmed
2026-07-28  0:07   ` sashiko-bot
2026-07-28  0:29     ` Yosry Ahmed
2026-07-27 23:52 ` [PATCH v4 03/12] KVM: selftests: Rework GPR registers switching for SVM (and fix offsets) Yosry Ahmed
2026-07-27 23:52 ` [PATCH v4 04/12] KVM: selftests: Handle rflags save/restore for SVM in guest_regs Yosry Ahmed
2026-07-27 23:52 ` [PATCH v4 05/12] KVM: selftests: Reuse GPR switching logic for nVMX Yosry Ahmed
2026-07-28  0:05   ` sashiko-bot
2026-07-28  0:30     ` Yosry Ahmed
2026-07-27 23:52 ` [PATCH v4 06/12] KVM: selftests: Drop HORRIFIC_L2_UCALL_CLOBBER_HACK Yosry Ahmed
2026-07-27 23:52 ` [PATCH v4 07/12] KVM: selftests: Add a blank line before logging assertion failures Yosry Ahmed
2026-07-27 23:52 ` [PATCH v4 08/12] KVM: selftests: Expose PTE masks to guests as part of an MMU Yosry Ahmed
2026-07-27 23:52 ` [PATCH v4 09/12] KVM: selftests: Add basic stress test for save+restore and #PF handling Yosry Ahmed
2026-07-28 14:53   ` Sean Christopherson
2026-07-27 23:52 ` [PATCH v4 10/12] KVM: selftests: Trigger save+restore randomly in the #PF stress test Yosry Ahmed
2026-07-28 14:58   ` Sean Christopherson [this message]
2026-07-27 23:52 ` [PATCH v4 11/12] KVM: selftests: Support running stress save+restore and #PF test in L2 Yosry Ahmed
2026-07-28 14:43   ` Sean Christopherson
2026-07-28 17:44     ` Yosry Ahmed
2026-07-27 23:52 ` [PATCH v4 12/12] KVM: selftests: Trigger L2->L1 exits stress save+restore and #PF test Yosry Ahmed
2026-07-28  0:09   ` sashiko-bot
2026-07-28  0:31     ` Yosry Ahmed
2026-07-28 15:07 ` [PATCH v4 00/12] KVM: selftests: Stress save+restore and #PF (ft. nested) Sean Christopherson

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=amjDn6fy8lgftsrE@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=yosry@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 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.