From: Janosch Frank <frankja@linux.ibm.com>
To: Andrew Donnellan <ajd@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Cc: Nicholas Miehlbradt <nicholas@linux.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
David Hildenbrand <david@kernel.org>
Subject: Re: [PATCH v2 3/3] KVM: s390: Use generic VIRT_XFER_TO_GUEST_WORK functions
Date: Thu, 27 Nov 2025 15:37:47 +0100 [thread overview]
Message-ID: <e76ed034-7c7a-4cd6-ae10-945ad39c2b00@linux.ibm.com> (raw)
In-Reply-To: <20251126-s390-kvm-xfer-to-guest-work-v2-3-1b8767879235@linux.ibm.com>
On 11/26/25 06:33, Andrew Donnellan wrote:
> Switch to using the generic infrastructure to check for and handle pending
> work before transitioning into guest mode.
>
> xfer_to_guest_mode_handle_work() does a few more things than the current
> code does when deciding whether or not to exit the __vcpu_run() loop. The
> exittime tests from kvm-unit-tests, in my tests, were within a few percent
> compared to before this series, which is within noise tolerance.
>
> Co-developed-by: Heiko Carstens <hca@linux.ibm.com>
> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
> Signed-off-by: Andrew Donnellan <ajd@linux.ibm.com>
> ---
> v2: if work is handled, recheck for outstanding work with interrupts
> disabled before entering guest (Heiko)
>
> The way I've implemented this, I do the check between vcpu_pre_run() and
> entering the guest, and bail out of the loop if
> kvm_xfer_to_guest_mode_handle_work() returns nonzero, without calling
> vcpu_post_run(). My impression is that this is safe, but it does mean
> there is an sie_enter vcpu event and trace event which isn't matched with
> corresponding exit events. Is this a problem?
Acked-by: Janosch Frank <frankja@linux.ibm.com>
prev parent reply other threads:[~2025-11-27 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 5:33 [PATCH v2 0/3] KVM: s390: Use generic VIRT_XFER_TO_GUEST_WORK entry helpers Andrew Donnellan
2025-11-26 5:33 ` [PATCH v2 1/3] KVM: s390: Add signal_exits counter Andrew Donnellan
2025-11-26 12:23 ` Janosch Frank
2025-11-26 5:33 ` [PATCH v2 2/3] KVM: s390: Enable and disable interrupts in entry code Andrew Donnellan
2025-11-26 12:31 ` Janosch Frank
2025-11-26 5:33 ` [PATCH v2 3/3] KVM: s390: Use generic VIRT_XFER_TO_GUEST_WORK functions Andrew Donnellan
2025-11-27 14:37 ` Janosch Frank [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=e76ed034-7c7a-4cd6-ae10-945ad39c2b00@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=ajd@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=luto@kernel.org \
--cc=nicholas@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
/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