Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Srirangan Madhavan <smadhavan@nvidia.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Ira Weiny <ira.weiny@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	linux-cxl@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Alex Williamson <alex.williamson@redhat.com>,
	vsethi@nvidia.com, alwilliamson@nvidia.com,
	Sai Yashwanth Reddy Kancherla <skancherla@nvidia.com>,
	Vishal Aslot <vaslot@nvidia.com>,
	Manish Honap <mhonap@nvidia.com>, Jiandi An <jan@nvidia.com>,
	Richard Cheng <icheng@nvidia.com>,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH v12 09/12] cxl: Restore CXL state after PCI reset
Date: Sat, 12 Sep 2026 02:43:32 +0100	[thread overview]
Message-ID: <20260912024332.17a19b2f@jic23-hlaptop> (raw)
In-Reply-To: <20260910070808.1444264-10-smadhavan@nvidia.com>

On Thu, 10 Sep 2026 07:08:05 +0000
Srirangan Madhavan <smadhavan@nvidia.com> wrote:

> After CXL reset, restore PCI config state enough to reach HDM MMIO,
> restore cached global and per-decoder HDM state, restore the cached
> CXL.cache and CXL.mem enable bits, and then run the normal PCI restore
> callbacks.
> 
> If reset clears a previously locked decoder, restore and commit its
> programming before reapplying the cached lock. Leave a locked committed
> decoder unchanged when that state survives reset.
> 
> Keep the target IOMMU reset block active until CXL state restore completes
> so Bus Master Enable cannot reopen DMA before decoder state is valid.
> 
> Signed-off-by: Srirangan Madhavan <smadhavan@nvidia.com>
I'm nearly out of time for today and have given quite a bit of
feedback on earlier patches. So this is going to be a scan read
at most. Make sure to take another look at this and incorporate
the sort of changes I've asked for elsewhere for v13.

This seems to carry on papering over the cracks after errors that
to me indicate a broken device.  I don't see any reason to do that.
If a device needs quirks to say don't run a particular restore do that
but if they are real errors, just give up - your device is not going
to be useable with only some stuff restored and you may be making
an obvious bug a much more subtle one.

Jonathan


> ---
>  drivers/cxl/core/resource.c | 411 ++++++++++++++++++++++++++++++++++--
>  1 file changed, 396 insertions(+), 15 deletions(-)
>

> +static int cxl_restore_hdm_decoder(struct pci_dev *pdev,
> +				   struct cxl_hdm_decoder_state *state,
> +				   struct cxl_decoder_settings *settings,
> +				   void __iomem *hdm)
> +{
> +	u32 ctrl;
> +	int rc;
> +
> +	rc = cxl_hdm_decoder_uncommit(pdev, hdm, settings->id);
> +	if (rc == -EBUSY)
> +		return 0;
> +	if (rc)
> +		return rc;
> +
> +	cxl_restore_hdm_decoder_state(state, hdm, settings->id);
> +
> +	if (!(settings->flags & CXL_DECODER_F_ENABLE))
> +		return 0;
> +
> +	scoped_guard(rwsem_read, &cxl_rwsem.dpa)
> +		rc = cxl_commit_start(hdm, settings);
> +	if (!rc)

Use a helper function for the stuff in here so you can return directly.

> +		rc = cxl_commit_wait(hdm, settings);
> +	if (rc)
> +		pci_err(pdev, "CXL HDM decoder %d restore failed: %d\n",
> +			settings->id, rc);
> +	else if (settings->flags & CXL_DECODER_F_LOCK) {
> +		ctrl = readl(hdm + CXL_HDM_DECODER0_CTRL_OFFSET(settings->id));
> +		ctrl |= CXL_HDM_DECODER0_CTRL_LOCK;
> +		writel(ctrl, hdm + CXL_HDM_DECODER0_CTRL_OFFSET(settings->id));
> +
> +		ctrl = readl(hdm + CXL_HDM_DECODER0_CTRL_OFFSET(settings->id));
> +		if (PCI_POSSIBLE_ERROR(ctrl) ||
> +		    !(ctrl & CXL_HDM_DECODER0_CTRL_LOCK)) {
> +			pci_err(pdev,
> +				"CXL HDM decoder %d failed to restore lock\n",
> +				settings->id);
> +			return -EIO;
> +		}
> +	}
> +
> +	return rc;
> +}

> +
> +static void cxl_restore_pci_state_for_hdm_restore(struct pci_dev *pdev,
> +						  u16 *command)
> +{
> +	u32 saved_config = pdev->saved_config_space[PCI_COMMAND / 4];
> +
> +	pdev->saved_config_space[PCI_COMMAND / 4] &= ~PCI_COMMAND_MASTER;
> +	pdev->saved_config_space[PCI_COMMAND / 4] |= PCI_COMMAND_INTX_DISABLE;
> +	pci_restore_state(pdev);
> +	pdev->saved_config_space[PCI_COMMAND / 4] = saved_config;
> +	*command = saved_config & 0xffff;
> +}
> +
> +static int cxl_restore_state(struct pci_dev *pdev)
> +{
> +	struct cxl_hdm_info *snap = cxl_snapshot_hdm(pdev);
__free(kfree); looks like it will make life simpler in here.


> +	bool restore_command = false;
> +	void __iomem *hdm;
> +	int first_rc = 0;
> +	u16 command;
> +	int rc;
> +
> +	if (!snap)
> +		return 0;
> +	if (IS_ERR(snap))
> +		return PTR_ERR(snap);
> +
> +	rc = cxl_hdm_enable_mem(pdev, &command, &restore_command);
> +	if (rc) {
> +		kfree(snap);
> +		return rc;
> +	}
> +
> +	hdm = cxl_pci_hdm_ioremap_current(pdev, snap->hdm_bar,
> +					  snap->hdm_offset, snap->hdm_size);
> +	if (IS_ERR(hdm)) {
> +		first_rc = PTR_ERR(hdm);

I'm not really understanding the keep trying and paper over the cracks
going on here.  If almost any of these fail it looks to me like
we are in a bad place and it would be cleaner to report and give up.

I restored 'some state' isn't likely to be very useful to anyone
beyond maybe making the breakage subtle rather than major and easy
to find.


> +	} else {
> +		/*
> +		 * Restore global HDM control before per-decoder commit. PCI
> +		 * config memory decoding is enabled for MMIO access, but bus
> +		 * mastering remains disabled until HDM restore completes.
> +		 */
> +		writel(snap->global_ctrl, hdm + CXL_HDM_DECODER_CTRL_OFFSET);
> +
> +		for (int i = 0; i < snap->decoder_count; i++) {
> +			rc = cxl_restore_hdm_decoder(pdev,
> +						     &snap->decoder_state[i],
> +						     &snap->settings[i], hdm);
> +			if (rc && !first_rc)
> +				first_rc = rc;
> +		}
> +
> +		/* Flush posted HDM writes before PCI_COMMAND can restore BME. */
> +		readl(hdm + CXL_HDM_DECODER_CTRL_OFFSET);
> +		iounmap(hdm);
> +	}
> +
> +	if (!first_rc && snap->dvsec_ctrl_valid) {
> +		rc = cxl_restore_dvsec_ctrl(pdev, snap->dvsec_ctrl);
> +		if (rc)
> +			first_rc = rc;
> +	}
> +
> +	if (restore_command) {
> +		rc = cxl_hdm_restore_command(pdev, command);
> +		if (rc && !first_rc)
> +			first_rc = rc;
> +	}
> +
> +	kfree(snap);
> +	return first_rc;
> +}


  parent reply	other threads:[~2026-09-12  1:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10  7:07 [PATCH v12 00/12] PCI/CXL: Add CXL reset support for Type 2 devices Srirangan Madhavan
2026-09-10  7:07 ` [PATCH v12 01/12] cxl: Move HDM decoder programming helpers Srirangan Madhavan
2026-09-10  7:20   ` sashiko-bot
2026-09-11 23:30   ` Jonathan Cameron
2026-09-10  7:07 ` [PATCH v12 02/12] cxl: Make HDM commit helpers available to reset code Srirangan Madhavan
2026-09-10  7:25   ` sashiko-bot
2026-09-10  7:07 ` [PATCH v12 03/12] cxl: Share HDM decoder decode logic Srirangan Madhavan
2026-09-10  7:18   ` sashiko-bot
2026-09-12  0:07   ` Jonathan Cameron
2026-09-10  7:08 ` [PATCH v12 04/12] cxl: Cache decoder settings on PCI devices Srirangan Madhavan
2026-09-10  7:22   ` sashiko-bot
2026-09-12  0:22   ` Jonathan Cameron
2026-09-10  7:08 ` [PATCH v12 05/12] cxl: Cache endpoint decoder settings during PCI enumeration Srirangan Madhavan
2026-09-10  7:25   ` sashiko-bot
2026-09-12  1:03   ` Jonathan Cameron
2026-09-10  7:08 ` [PATCH v12 06/12] cxl: Add CXL Device Reset helper Srirangan Madhavan
2026-09-10  7:20   ` sashiko-bot
2026-09-12  1:26   ` Jonathan Cameron
2026-09-10  7:08 ` [PATCH v12 07/12] cxl: Validate HDM ranges before CXL reset Srirangan Madhavan
2026-09-10  7:22   ` sashiko-bot
2026-09-12  1:33   ` Jonathan Cameron
2026-09-10  7:08 ` [PATCH v12 08/12] PCI/CXL: Reject CXL Reset on multifunction devices Srirangan Madhavan
2026-09-10  7:20   ` sashiko-bot
2026-09-10  7:08 ` [PATCH v12 09/12] cxl: Restore CXL state after PCI reset Srirangan Madhavan
2026-09-10  7:25   ` sashiko-bot
2026-09-12  1:43   ` Jonathan Cameron [this message]
2026-09-10  7:08 ` [PATCH v12 10/12] PCI/CXL: Expose CXL Reset as a PCI reset method Srirangan Madhavan
2026-09-10  7:29   ` sashiko-bot
2026-09-10  7:08 ` [PATCH v12 11/12] Documentation/ABI: Document CXL Reset " Srirangan Madhavan
2026-09-10  7:20   ` sashiko-bot
2026-09-10  7:08 ` [PATCH v12 12/12] PCI/CXL: Restore CXL state after CXL bus reset Srirangan Madhavan
2026-09-10  7:37   ` sashiko-bot
2026-09-10  7:31 ` [PATCH v12 00/12] PCI/CXL: Add CXL reset support for Type 2 devices Srirangan Madhavan

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=20260912024332.17a19b2f@jic23-hlaptop \
    --to=jic23@kernel.org \
    --cc=alex.williamson@redhat.com \
    --cc=alison.schofield@intel.com \
    --cc=alwilliamson@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=icheng@nvidia.com \
    --cc=ira.weiny@intel.com \
    --cc=jan@nvidia.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mhonap@nvidia.com \
    --cc=skancherla@nvidia.com \
    --cc=smadhavan@nvidia.com \
    --cc=vaslot@nvidia.com \
    --cc=vishal.l.verma@intel.com \
    --cc=vsethi@nvidia.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