From: Matthew Rosato <mjrosato@linux.ibm.com>
To: Douglas Freimuth <freimuth@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 v2 2/3] KVM: s390: Enable adapter_indicators_set to use mapped pages
Date: Fri, 27 Mar 2026 11:25:35 -0400 [thread overview]
Message-ID: <38452644-a097-4e03-a4b9-902c8c8d23f2@linux.ibm.com> (raw)
In-Reply-To: <20260326014247.2085-3-freimuth@linux.ibm.com>
On 3/25/26 9:42 PM, Douglas Freimuth wrote:
> The S390 adapter_indicators_set function needs to be able to use mapped
> pages so that worked can be processed,on a fast path when interrupts are
> disabled. If adapter indicator pages are not mapped then local mapping is
> done on a slow path as it is prior to this patch. For example, Secure
> Execution environments will take the local mapping path as it does prior to
> this patch.
>
> Signed-off-by: Douglas Freimuth <freimuth@linux.ibm.com>
> ---
[...]
> static int adapter_indicators_set(struct kvm *kvm,
> struct s390_io_adapter *adapter,
> struct kvm_s390_adapter_int *adapter_int)
> {
> unsigned long bit;
> int summary_set, idx;
> - struct page *ind_page, *summary_page;
> + struct s390_map_info *ind_info, *summary_info;
> void *map;
> + struct page *ind_page, *summary_page;
>
> - ind_page = get_map_page(kvm, adapter_int->ind_addr);
> - if (!ind_page)
> - return -1;
> - summary_page = get_map_page(kvm, adapter_int->summary_addr);
> - if (!summary_page) {
> - put_page(ind_page);
> - return -1;
> + ind_info = get_map_info(adapter, adapter_int->ind_addr);
> + if (!ind_info) {
> + ind_page = get_map_page(kvm, adapter_int->ind_addr);
> + if (!ind_page)
> + return -1;
> + idx = srcu_read_lock(&kvm->srcu);
> + map = page_address(ind_page);
> + bit = get_ind_bit(adapter_int->ind_addr,
> + adapter_int->ind_offset, adapter->swap);
> + set_bit(bit, map);
> + mark_page_dirty(kvm, adapter_int->ind_gaddr >> PAGE_SHIFT);
> + set_page_dirty_lock(ind_page);
Sashiko's comments about this area of code should already be addressed
by my comments in v1 wrt to marking the page dirty before unpinning.
> + srcu_read_unlock(&kvm->srcu, idx);
> + } else {
> + map = page_address(ind_info->page);
> + bit = get_ind_bit(ind_info->addr, adapter_int->ind_offset, adapter->swap);
> + set_bit(bit, map);
> + }
> + summary_info = get_map_info(adapter, adapter_int->summary_addr);
> + if (!summary_info) {
> + summary_page = get_map_page(kvm, adapter_int->summary_addr);
> + if (!summary_page) {
> + put_page(ind_page);
Sashiko has a point here. It is possible that you may have taken the
else path above where ind_info != NULL and never used ind_page.
Initialize ind_page to a NULL value first and check for a NULL value
here before attempting a put_page.
Or I think you can also check (!ind_info) and only put the page in this
case like you do later in this function.
[...]
>
> @@ -2890,6 +2924,7 @@ static int set_adapter_int(struct kvm_kernel_irq_routing_entry *e,
> {
> int ret;
> struct s390_io_adapter *adapter;
> + unsigned long flags;
>
> /* We're only interested in the 0->1 transition. */
> if (!level)
> @@ -2897,7 +2932,9 @@ static int set_adapter_int(struct kvm_kernel_irq_routing_entry *e,
> adapter = get_io_adapter(kvm, e->adapter.adapter_id);
> if (!adapter)
> return -1;
> + spin_lock_irqsave(&adapter->maps_lock, flags);
> ret = adapter_indicators_set(kvm, adapter, &e->adapter);
> + spin_unlock_irqrestore(&adapter->maps_lock, flags);
Another point for Sashiko -- This is almost certainly a fallout from my
recommendation to drop the semaphore from patch 1 and go straight to a
spinlock vs adding semaphore in patch 1 and converting in patch 3.
You can't put a spinlock here as you may lose control inside
adapter_indicators_set. You resolve the incompatibility in the next
patch by moving the spinlock inside the call and dropping it before you
could lose control -- but you have to already account for that in this
patch.
> if ((ret > 0) && !adapter->masked) {
> ret = kvm_s390_inject_airq(kvm, adapter);
> if (ret == 0)
next prev parent reply other threads:[~2026-03-27 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 1:42 [PATCH v2 0/3] KVM: s390: Introducing kvm_arch_set_irq_inatomic Fast Inject Douglas Freimuth
2026-03-26 1:42 ` [PATCH v2 1/3] KVM: s390: Add map/unmap ioctl and clean mappings post-guest Douglas Freimuth
2026-03-26 11:46 ` Christian Borntraeger
2026-03-27 15:22 ` Douglas Freimuth
2026-03-26 15:56 ` Janosch Frank
2026-03-27 15:31 ` Douglas Freimuth
2026-03-27 15:24 ` Matthew Rosato
2026-03-26 1:42 ` [PATCH v2 2/3] KVM: s390: Enable adapter_indicators_set to use mapped pages Douglas Freimuth
2026-03-27 15:25 ` Matthew Rosato [this message]
2026-03-26 1:42 ` [PATCH v2 3/3] KVM: s390: Introducing kvm_arch_set_irq_inatomic fast inject Douglas Freimuth
2026-03-27 15:59 ` Matthew Rosato
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=38452644-a097-4e03-a4b9-902c8c8d23f2@linux.ibm.com \
--to=mjrosato@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=freimuth@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=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 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.