From: "Christoph Schlameuss" <schlameuss@linux.ibm.com>
To: "Janosch Frank" <frankja@linux.ibm.com>,
"Christoph Schlameuss" <schlameuss@linux.ibm.com>,
<kvm@vger.kernel.org>, <linux-s390@vger.kernel.org>
Cc: "Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Claudio Imbrenda" <imbrenda@linux.ibm.com>,
"David Hildenbrand" <david@kernel.org>,
"Eric Farman" <farman@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Nico Boehr" <nrb@linux.ibm.com>,
"Sven Schnelle" <svens@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Shuah Khan" <shuah@kernel.org>,
"Sean Christopherson" <seanjc@google.com>
Subject: Re: [PATCH v7 08/21] KVM: s390: vsie: Create helpers to alloc and free vsie_pages
Date: Thu, 24 Sep 2026 13:32:12 +0200 [thread overview]
Message-ID: <DLNIHTBTMVCN.63H29I8Y56E2@linux.ibm.com> (raw)
In-Reply-To: <14552c47-8b20-41a6-a194-5aee626251de@linux.ibm.com>
On Wed Sep 23, 2026 at 1:54 PM CEST, Janosch Frank wrote:
> On 9/18/26 5:09 PM, Christoph Schlameuss wrote:
>> Encapsulate allocation of struct vsie_page and free into its own methods
>> to allow this from multiple code paths.
>>
>> Signed-off-by: Christoph Schlameuss <schlameuss@linux.ibm.com>
>> ---
>> arch/s390/kvm/s390/vsie.c | 26 ++++++++++++++++++++++----
>> 1 file changed, 22 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/s390/kvm/s390/vsie.c b/arch/s390/kvm/s390/vsie.c
>> index afc2e56fcabf..e7005bade757 100644
>> --- a/arch/s390/kvm/s390/vsie.c
>> +++ b/arch/s390/kvm/s390/vsie.c
>> @@ -1502,6 +1502,24 @@ static void put_vsie_page(struct vsie_page *vsie_page)
>> clear_bit(VSIE_PAGE_IN_USE, &vsie_page->flags);
>> }
>>
>> +static void free_vsie_page(struct vsie_page *vsie_page)
>> +{
>> + free_page((unsigned long)vsie_page);
>> +}
>> +
>> +static struct vsie_page *alloc_vsie_page(struct kvm *kvm)
>> +{
>> + struct vsie_page *vsie_page;
>> +
>> + vsie_page = (struct vsie_page *)__get_free_page(GFP_KERNEL_ACCOUNT | __GFP_ZERO | GFP_DMA);
>> + if (!vsie_page)
>> + return vsie_page;
>> +
>> + /* Mark it as invalid until it resides in the tree. */
>> + vsie_page->scb_gpa = ULONG_MAX;
>
> I'd appreciate a properly named constant in favor of the comment being
> repeated. This has been a thorn in my side for a while now.
>
> #define VSIE_PAGE_INV ULONG_MAX
>
Yes, I like it. Makes it easier to grasp directly without the comments.
>> + return vsie_page;
>> +}
>> +
>> /*
>> * Get or create a vsie page for a scb address.
>> *
>> @@ -1537,7 +1555,7 @@ static struct vsie_page *get_vsie_page(struct kvm *kvm, unsigned long addr)
>>
>> mutex_lock(&kvm->arch.vsie.mutex);
>> if (kvm->arch.vsie.page_count < nr_vcpus) {
>> - vsie_page = (void *)__get_free_page(GFP_KERNEL_ACCOUNT | __GFP_ZERO | GFP_DMA);
>
> Can't we go the kzalloc route like Mike did for the other page
> allocations? Maybe we can then also get rid of the free function that
> you're introducing?
>
> https://lore.kernel.org/kvm/20260906-s390-kvm-v2-0-2cf6434e6646@kernel.org/
>
Sure, I do not see a reason not to as long as kzalloc() guarantees the page
alignment (which it does).
Will do the same for the vsie_sca allocation in the other patch (which then
should also be guaranteed to be page aligned continuous memory).
>> + vsie_page = alloc_vsie_page(kvm);
>> if (!vsie_page) {
>> mutex_unlock(&kvm->arch.vsie.mutex);
>> return ERR_PTR(-ENOMEM);
>> @@ -1557,9 +1575,9 @@ static struct vsie_page *get_vsie_page(struct kvm *kvm, unsigned long addr)
>> if (vsie_page->scb_gpa != ULONG_MAX)
>> radix_tree_delete(&kvm->arch.vsie.addr_to_page,
>> vsie_page->scb_gpa >> SCB_ALIGNMENT_SHIFT);
next prev parent reply other threads:[~2026-09-24 11:32 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 15:09 [PATCH v7 00/21] KVM: s390: vsie: Add VSIE SIGP ECALL and SRSI Interpretation Christoph Schlameuss
2026-09-18 15:09 ` [PATCH v7 01/21] KVM: s390: vsie: Add SCAO read and write helpers Christoph Schlameuss
2026-09-18 15:14 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 02/21] KVM: s390: vsie: Move SCAO validation into a function Christoph Schlameuss
2026-09-18 15:24 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 03/21] KVM: s390: vsie: Add vsie_interp_extf detection Christoph Schlameuss
2026-09-18 15:15 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 04/21] KVM: s390: vsie: Add ssca_block and ssca_entry structs Christoph Schlameuss
2026-09-18 15:14 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 05/21] KVM: s390: vsie: Move pin/unpin guest page Christoph Schlameuss
2026-09-18 15:16 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 06/21] KVM: s390: vsie: Move pin/unpin_scb methods Christoph Schlameuss
2026-09-18 15:24 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 07/21] KVM: s390: vsie: Move release/acquire gmap shadow Christoph Schlameuss
2026-09-18 15:16 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 08/21] KVM: s390: vsie: Create helpers to alloc and free vsie_pages Christoph Schlameuss
2026-09-18 15:19 ` sashiko-bot
2026-09-23 11:54 ` Janosch Frank
2026-09-24 11:32 ` Christoph Schlameuss [this message]
2026-09-18 15:09 ` [PATCH v7 09/21] KVM: s390: vsie: Replace radix_tree with xarray addr_to_page Christoph Schlameuss
2026-09-18 15:25 ` sashiko-bot
2026-09-23 12:40 ` Janosch Frank
2026-09-18 15:09 ` [PATCH v7 10/21] KVM: s390: vsie: Refactor kvm_s390_vsie_destroy and extract reusable methods Christoph Schlameuss
2026-09-18 15:22 ` sashiko-bot
2026-09-23 12:56 ` Janosch Frank
2026-09-18 15:09 ` [PATCH v7 11/21] KVM: s390: vsie: Add helper reset_vsie_page() and unshadow_intercept() Christoph Schlameuss
2026-09-18 15:25 ` sashiko-bot
2026-09-23 12:58 ` Janosch Frank
2026-09-18 15:09 ` [PATCH v7 12/21] KVM: s390: vsie: Add helper unshadow_intercept() Christoph Schlameuss
2026-09-18 15:27 ` sashiko-bot
2026-09-23 14:04 ` Janosch Frank
2026-09-18 15:09 ` [PATCH v7 13/21] KVM: s390: vsie: Lazily keep original scb pinned after vsie exit Christoph Schlameuss
2026-09-18 15:34 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 14/21] KVM: s390: vsie: Add helper to pin and unpin multiple guest pages Christoph Schlameuss
2026-09-18 15:31 ` sashiko-bot
2026-09-24 12:46 ` Janosch Frank
2026-09-18 15:09 ` [PATCH v7 15/21] KVM: s390: vsie: Add struct vsie_sca with pin and unpin methods Christoph Schlameuss
2026-09-18 15:33 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 16/21] KVM: s390: vsie: Shadow VSIE SCA in guest-1 Christoph Schlameuss
2026-09-18 15:41 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 17/21] KVM: s390: vsie: Allow guest-3 cpu add and remove with ssca Christoph Schlameuss
2026-09-18 15:41 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 18/21] KVM: s390: vsie: Add VSIE max shadow configuration Christoph Schlameuss
2026-09-18 15:45 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 19/21] KVM: s390: vsie: Add VSIE shadow stat counters Christoph Schlameuss
2026-09-18 15:39 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 20/21] KVM: s390: vsie: Create minimal scb shadows for not running g3 blocks Christoph Schlameuss
2026-09-18 15:50 ` sashiko-bot
2026-09-18 15:09 ` [PATCH v7 21/21] KVM: s390: vsie: Enable use of VSIE SSCA Christoph Schlameuss
2026-09-18 15:53 ` sashiko-bot
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=DLNIHTBTMVCN.63H29I8Y56E2@linux.ibm.com \
--to=schlameuss@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@kernel.org \
--cc=farman@linux.ibm.com \
--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-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shuah@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.