From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Omar Elghoul <oelghoul@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Cc: hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
borntraeger@linux.ibm.com, svens@linux.ibm.com,
mjrosato@linux.ibm.com, alifm@linux.ibm.com,
farman@linux.ibm.com, gbayer@linux.ibm.com, pasic@linux.ibm.com,
alex@shazbot.org, frankja@linux.ibm.com, imbrenda@linux.ibm.com
Subject: Re: [PATCH v13 3/5] s390/pci: Improve FMB memory management
Date: Wed, 11 Nov 2026 21:39:08 +0100 [thread overview]
Message-ID: <df4feb17e7c970ea2e259e81784e6dfab0dee5cf.camel@linux.ibm.com> (raw)
In-Reply-To: <20261111162758.9792-4-oelghoul@linux.ibm.com>
On Wed, 2026-11-11 at 11:27 -0500, Omar Elghoul wrote:
> Refactor the FMB memory management code to use kzalloc() instead of a
> dedicated kmem_cache. kzalloc() already guarantees adequate alignment
> for power-of-two sizes, rendering the kmem_cache approach unnecessary.
> This simplifies both the initialization and cleanup procedures.
>
> Allocate the FMB once upon first enable and keep it for the lifetime of
> the zdev instead of freeing it on every disable. Defer freeing the
> buffer until device teardown in zpci_release_device(). Add the field
> fmb_enabled to struct zpci_dev as the new FMB liveness bool, since a
> non-null FMB pointer no longer implies FMB enablement in firmware.
>
> Signed-off-by: Omar Elghoul <oelghoul@linux.ibm.com>
> ---
> arch/s390/include/asm/pci.h | 1 +
> arch/s390/pci/pci.c | 61 +++++++++++++++++++++----------------
> arch/s390/pci/pci_debug.c | 2 +-
> 3 files changed, 37 insertions(+), 27 deletions(-)
And this one too looks good now. In the beginning I had really guessed
that this would have been a series with few hurdles but the devil
really is in the detail. Thanks for the great work.
Reviewed-by: Niklas Schnelle <schnelle@linux.ibm.com>
Thanks,
Niklas
next prev parent reply other threads:[~2026-11-11 20:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 16:27 [PATCH v13 0/5] vfio-pci/zdev: Improved zPCI Function Measurement Support Omar Elghoul
2026-11-11 16:27 ` [PATCH v13 1/5] s390/pci: Hold fmb_lock when enabling or disabling PCI devices Omar Elghoul
2026-11-11 17:00 ` sashiko-bot
2026-11-11 16:27 ` [PATCH v13 2/5] s390/pci: Improve function measurement state management Omar Elghoul
2026-11-11 17:20 ` sashiko-bot
2026-11-11 20:33 ` Niklas Schnelle
2026-11-11 20:37 ` Niklas Schnelle
2026-11-11 16:27 ` [PATCH v13 3/5] s390/pci: Improve FMB memory management Omar Elghoul
2026-11-11 17:32 ` sashiko-bot
2026-11-11 20:39 ` Niklas Schnelle [this message]
2026-11-11 16:27 ` [PATCH v13 4/5] s390/pci: Fence FMB enable/disable via debugfs for passthrough devices Omar Elghoul
2026-11-11 17:36 ` sashiko-bot
2026-11-11 16:27 ` [PATCH v13 5/5] vfio-pci/zdev: Add VFIO FMB device features Omar Elghoul
2026-11-11 17:43 ` 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=df4feb17e7c970ea2e259e81784e6dfab0dee5cf.camel@linux.ibm.com \
--to=schnelle@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=alex@shazbot.org \
--cc=alifm@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=gbayer@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=oelghoul@linux.ibm.com \
--cc=pasic@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 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.