From: Douglas Freimuth <freimuth@linux.ibm.com>
To: Matthew Rosato <mjrosato@linux.ibm.com>,
borntraeger@linux.ibm.com, imbrenda@linux.ibm.com,
frankja@linux.ibm.com, david@kernel.org, hca@linux.ibm.com,
gor@linux.ibm.com, agordeev@linux.ibm.com, svens@linux.ibm.com,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 3/3] KVM: s390: Introducing kvm_arch_set_irq_inatomic fast inject
Date: Tue, 2 Jun 2026 14:14:59 -0400 [thread overview]
Message-ID: <9c5f80d8-0a08-4cf2-8bbe-e071089e8531@linux.ibm.com> (raw)
In-Reply-To: <c9797cc0-d661-4208-bd89-d96fff3b8a07@linux.ibm.com>
On 6/2/26 1:30 PM, Matthew Rosato wrote:
> On 5/31/26 3:03 PM, Douglas Freimuth wrote:
>> s390 needs a fast path for irq injection, and along those lines we
>> introduce kvm_arch_set_irq_inatomic. Instead of placing all interrupts on
>> the global work queue as it does today, this patch provides a fast path for
>> irq injection.
>>
>> The inatomic fast path cannot lose control since it is running with
>> interrupts disabled. This meant making the following changes that exist on
>> the slow path today. First, the adapter_indicators page needs to be mapped
>> since it is accessed with interrupts disabled, so we added map/unmap
>> functions. Second, access to shared resources between the fast and slow
>> paths needed to be changed from mutex and semaphores to spin_lock's.
>> Finally, the memory allocation on the slow path utilizes GFP_KERNEL_ACCOUNT
>> but we had to implement the fast path with GFP_ATOMIC allocation. Each of
>> these enhancements were required to prevent blocking on the fast inject
>> path.
>>
>> Fencing of Fast Inject in Secure Execution environments is enabled in the
>> patch series by not mapping adapter indicator pages. In Secure Execution
>> environments the path of execution available before this patch is followed.
>>
>> Statistical counters have been added to enable analysis of irq injection on
>> the fast path and slow path including io_390_inatomic, io_flic_inject_airq,
>> io_set_adapter_int and io_390_inatomic_no_inject. The no inject counter
>> captures adapter masked, coalesced and suppressed interrupts.
>>
>> Signed-off-by: Douglas Freimuth <freimuth@linux.ibm.com>
>
> Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
Matt, thank you for all of your inputs across the iterations.>
prev parent reply other threads:[~2026-06-02 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 19:03 [PATCH v9 0/3] KVM: s390: Introducing kvm_arch_set_irq_inatomic Fast Inject Douglas Freimuth
2026-05-31 19:03 ` [PATCH v9 1/3] KVM: s390: Add map/unmap ioctl and clean mappings post-guest Douglas Freimuth
2026-06-01 13:14 ` Janosch Frank
2026-06-02 17:28 ` Douglas Freimuth
2026-05-31 19:03 ` [PATCH v9 2/3] KVM: s390: Enable adapter_indicators_set to use mapped pages Douglas Freimuth
2026-05-31 19:03 ` [PATCH v9 3/3] KVM: s390: Introducing kvm_arch_set_irq_inatomic fast inject Douglas Freimuth
2026-06-02 17:30 ` Matthew Rosato
2026-06-02 18:14 ` Douglas Freimuth [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=9c5f80d8-0a08-4cf2-8bbe-e071089e8531@linux.ibm.com \
--to=freimuth@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--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=mjrosato@linux.ibm.com \
--cc=svens@linux.ibm.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