mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gerd Bayer <gbayer@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,
	schnelle@linux.ibm.com, mjrosato@linux.ibm.com,
	alifm@linux.ibm.com, farman@linux.ibm.com, pasic@linux.ibm.com,
	alex@shazbot.org, frankja@linux.ibm.com, imbrenda@linux.ibm.com,
	Gerd Bayer <gbayer@linux.ibm.com>
Subject: Re: [PATCH v12 3/5] s390/pci: Improve FMB memory management
Date: Fri, 06 Nov 2026 12:03:41 +0100	[thread overview]
Message-ID: <d683bc7a4852857f132187097eb2f610c53c76b9.camel@linux.ibm.com> (raw)
In-Reply-To: <20261103150114.68873-4-oelghoul@linux.ibm.com>

On Tue, 2026-11-03 at 10:01 -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.

TIL about the power-of-two alignment guarantee of kmalloc(). Nice!

> 
> 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.

Nit: maybe add "in hardware" to the last sentence?

> 
> Signed-off-by: Omar Elghoul <oelghoul@linux.ibm.com>
> ---
>  arch/s390/include/asm/pci.h |  1 +
>  arch/s390/pci/pci.c         | 59 +++++++++++++++++++++----------------
>  arch/s390/pci/pci_debug.c   |  2 +-
>  3 files changed, 35 insertions(+), 27 deletions(-)
> 
> diff --git a/arch/s390/include/asm/pci.h b/arch/s390/include/asm/pci.h
> index dd58c48ac2ed..6d3c1b8ac75b 100644
> --- a/arch/s390/include/asm/pci.h
> +++ b/arch/s390/include/asm/pci.h
> @@ -209,6 +209,7 @@ struct zpci_dev {
>  	u16		fmb_update;	/* update interval */
>  	u16		fmb_length;
>  	u8		statistics_on	: 1; /* desired FMB enablement */
> +	u8		fmb_enabled	: 1; /* actual FMB enablement */

Nit: Maybe reword the comment for fmb_enabled to "enabled in hardware"
- to better distinguish the layers where enablement happens?

>  
>  	u8		version;
>  	enum pci_bus_speed max_bus_speed;
> diff --git a/arch/s390/pci/pci.c b/arch/s390/pci/pci.c
> index f49736386eb7..f066a7ffc35c 100644
> --- a/arch/s390/pci/pci.c
> +++ b/arch/s390/pci/pci.c
> @@ -62,8 +62,6 @@ EXPORT_SYMBOL_GPL(zpci_iomap_start);
>  
>  DEFINE_STATIC_KEY_FALSE(have_mio);
>  
> -static struct kmem_cache *zdev_fmb_cache;
> -
>  /* AEN structures that must be preserved over KVM module re-insertion */
>  union zpci_sic_iib *zpci_aipb;
>  EXPORT_SYMBOL_GPL(zpci_aipb);
> @@ -205,13 +203,17 @@ int zpci_fmb_enable(struct zpci_dev *zdev)
>  
>  	lockdep_assert_held(&zdev->fmb_lock);
>  
> -	if (zdev->fmb || sizeof(*zdev->fmb) < zdev->fmb_length)
> +	if (zdev->fmb_enabled || sizeof(*zdev->fmb) < zdev->fmb_length)
>  		return -EINVAL;
>  
> -	zdev->fmb = kmem_cache_zalloc(zdev_fmb_cache, GFP_KERNEL);
> -	if (!zdev->fmb)
> -		return -ENOMEM;
> -	WARN_ON((u64) zdev->fmb & 0xf);
> +	if (!zdev->fmb) {
> +		zdev->fmb = kzalloc_obj(*zdev->fmb, GFP_KERNEL);
> +		if (!zdev->fmb)
> +			return -ENOMEM;
> +	} else {
> +		/* reuse the same FMB buffer for as long as the zdev lives */
> +		memset(zdev->fmb, 0, sizeof(*zdev->fmb));
> +	}
>  
>  	/* reset software counters */
>  	spin_lock_irqsave(&zdev->dom_lock, flags);
> @@ -229,11 +231,12 @@ int zpci_fmb_enable(struct zpci_dev *zdev)
>  	fib.fmb_addr = virt_to_phys(zdev->fmb);
>  	fib.gd = zdev->gisa;
>  	cc = zpci_mod_fc(req, &fib, &status);
> -	if (cc) {
> -		kmem_cache_free(zdev_fmb_cache, zdev->fmb);
> -		zdev->fmb = NULL;
> -	}
> -	return cc ? -EIO : 0;
> +
> +	if (cc)
> +		return -EIO;
> +
> +	zdev->fmb_enabled = 1;
> +	return 0;
>  }
>  
>  /* Modify PCI: Disable PCI function measurement */
> @@ -245,7 +248,7 @@ int zpci_fmb_disable(struct zpci_dev *zdev)
>  
>  	lockdep_assert_held(&zdev->fmb_lock);
>  
> -	if (!zdev->fmb)
> +	if (!zdev->fmb_enabled)
>  		return -EINVAL;
>  
>  	fib.gd = zdev->gisa;
> @@ -255,11 +258,11 @@ int zpci_fmb_disable(struct zpci_dev *zdev)
>  	if (cc == 3) /* Function already gone. */
>  		cc = 0;
>  
> -	if (!cc) {
> -		kmem_cache_free(zdev_fmb_cache, zdev->fmb);
> -		zdev->fmb = NULL;
> -	}
> -	return cc ? -EIO : 0;
> +	if (cc)
> +		return -EIO;
> +
> +	zdev->fmb_enabled = 0;
> +	return 0;
>  }
>  
>  static int zpci_cfg_load(struct zpci_dev *zdev, int offset, u32 *val, u8 len)
> @@ -802,6 +805,12 @@ int zpci_disable_device(struct zpci_dev *zdev)
>  	} else {
>  		rc = -EIO;
>  	}
> +
> +	if (!rc) {
> +		guard(mutex)(&zdev->fmb_lock);
> +		zdev->fmb_enabled = 0;
> +	}
> +
>  	return rc;
>  }
>  EXPORT_SYMBOL_GPL(zpci_disable_device);
> @@ -1047,6 +1056,12 @@ void zpci_release_device(struct kref *kref)
>  	if (zdev->has_resources)
>  		zpci_cleanup_bus_resources(zdev);
>  
> +	if (zdev->fmb) {
> +		zdev->fmb_enabled = 0;
> +		kfree(zdev->fmb);
> +		zdev->fmb = NULL;
> +	}
> +
>  	zpci_bus_device_unregister(zdev);
>  	zpci_destroy_iommu(zdev);
>  	zpci_dbg(3, "rem fid:%x\n", zdev->fid);
> @@ -1122,11 +1137,6 @@ static int zpci_mem_init(void)
>  	BUILD_BUG_ON((CONFIG_ILLEGAL_POINTER_VALUE + 0x10000 > ZPCI_IOMAP_ADDR_BASE) &&
>  		     (CONFIG_ILLEGAL_POINTER_VALUE <= ZPCI_IOMAP_ADDR_MAX));
>  
> -	zdev_fmb_cache = kmem_cache_create("PCI_FMB_cache", sizeof(struct zpci_fmb),
> -					   __alignof__(struct zpci_fmb), 0, NULL);
> -	if (!zdev_fmb_cache)
> -		goto error_fmb;
> -
>  	zpci_iomap_start = kzalloc_objs(*zpci_iomap_start, ZPCI_IOMAP_ENTRIES);
>  	if (!zpci_iomap_start)
>  		goto error_iomap;
> @@ -1143,8 +1153,6 @@ static int zpci_mem_init(void)
>  error_iomap_bitmap:
>  	kfree(zpci_iomap_start);
>  error_iomap:
> -	kmem_cache_destroy(zdev_fmb_cache);
> -error_fmb:
>  	return -ENOMEM;
>  }
>  
> @@ -1152,7 +1160,6 @@ static void zpci_mem_exit(void)
>  {
>  	kfree(zpci_iomap_bitmap);
>  	kfree(zpci_iomap_start);
> -	kmem_cache_destroy(zdev_fmb_cache);
>  }
>  
>  static unsigned int s390_pci_probe __initdata = 1;
> diff --git a/arch/s390/pci/pci_debug.c b/arch/s390/pci/pci_debug.c
> index 06e2e8bb2f82..454121bc274c 100644
> --- a/arch/s390/pci/pci_debug.c
> +++ b/arch/s390/pci/pci_debug.c
> @@ -97,7 +97,7 @@ static int pci_perf_show(struct seq_file *m, void *v)
>  		return 0;
>  
>  	mutex_lock(&zdev->fmb_lock);
> -	if (!zdev->fmb) {
> +	if (!zdev->fmb_enabled) {
>  		mutex_unlock(&zdev->fmb_lock);
>  		seq_puts(m, "FMB statistics disabled\n");
>  		return 0;

Otherwise, this looks good - and I think Niklas did cover nicely the
Sashiko comments regarding implicit disablement of PCI functions and
the implication of that to fmb_enable.

Thanks,
Gerd

  reply	other threads:[~2026-11-06 11:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 15:01 [PATCH v12 0/5] vfio-pci/zdev: Improved zPCI Function Measurement Support Omar Elghoul
2026-11-03 15:01 ` [PATCH v12 1/5] s390/pci: Hold fmb_lock when enabling or disabling PCI devices Omar Elghoul
2026-11-03 15:01 ` [PATCH v12 2/5] s390/pci: Improve function measurement state management Omar Elghoul
2026-11-05 16:59   ` Gerd Bayer
2026-11-03 15:01 ` [PATCH v12 3/5] s390/pci: Improve FMB memory management Omar Elghoul
2026-11-06 11:03   ` Gerd Bayer [this message]
2026-11-03 15:01 ` [PATCH v12 4/5] s390/pci: Fence FMB enable/disable via debugfs for passthrough devices Omar Elghoul
2026-11-03 15:01 ` [PATCH v12 5/5] vfio-pci/zdev: Add VFIO FMB device features Omar Elghoul
2026-11-03 21:08   ` Niklas Schnelle
2026-11-03 22:45     ` 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=d683bc7a4852857f132187097eb2f610c53c76b9.camel@linux.ibm.com \
    --to=gbayer@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=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=schnelle@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

all inboxes | Powered by JetHome®