From: Dave Jiang <dave.jiang@intel.com>
To: Foryun Ma <foryun.ma@jaguarmicro.com>, dave@stgolabs.net
Cc: linux-cxl@vger.kernel.org, rrichter@amd.com,
angus.chen@jaguarmicro.com,
Dan Williams <dan.j.williams@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Alison Schofield <alison.schofield@intel.com>
Subject: Re: [PATCH] cxl/pci: the ctrl register should be read when it is being used
Date: Wed, 29 May 2024 09:31:21 -0700 [thread overview]
Message-ID: <c2f43fa5-f5a2-4e18-b192-fccbc2792519@intel.com> (raw)
In-Reply-To: <20240529093354.409-1-foryun.ma@jaguarmicro.com>
On 5/29/24 2:33 AM, Foryun Ma wrote:
> When the cap register and wait_for_valid checks fail, the ctrl register
> read will be redundant.
>
> Signed-off-by: Foryun Ma <foryun.ma@jaguarmicro.com>
Please consider slight change to the subject and commit log:
cxl/core/pci: Move reading of control register to immediately before usage
Relocate the reading of the DVSEC control register to immediately before usage and
avoid unnecessary PCI config access from the read if DVSEC capability check, hdm_count
check, or device validity check results in failure.
Otherwise LGTM
> ---
> drivers/cxl/core/pci.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/cxl/core/pci.c b/drivers/cxl/core/pci.c
> index 8567dd11eaac..627be83881e9 100644
> --- a/drivers/cxl/core/pci.c
> +++ b/drivers/cxl/core/pci.c
> @@ -338,10 +338,6 @@ int cxl_dvsec_rr_decode(struct device *dev, int d,
> if (rc)
> return rc;
>
> - rc = pci_read_config_word(pdev, d + CXL_DVSEC_CTRL_OFFSET, &ctrl);
> - if (rc)
> - return rc;
> -
> if (!(cap & CXL_DVSEC_MEM_CAPABLE)) {
> dev_dbg(dev, "Not MEM Capable\n");
> return -ENXIO;
> @@ -363,6 +359,10 @@ int cxl_dvsec_rr_decode(struct device *dev, int d,
> return rc;
> }
>
> + rc = pci_read_config_word(pdev, d + CXL_DVSEC_CTRL_OFFSET, &ctrl);
> + if (rc)
> + return rc;
> +
> /*
> * The current DVSEC values are moot if the memory capability is
> * disabled, and they will remain moot after the HDM Decoder
prev parent reply other threads:[~2024-05-29 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 9:33 [PATCH] cxl/pci: the ctrl register should be read when it is being used Foryun Ma
2024-05-29 16:30 ` Alison Schofield
2024-05-29 16:31 ` Dave Jiang [this message]
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=c2f43fa5-f5a2-4e18-b192-fccbc2792519@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=angus.chen@jaguarmicro.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=foryun.ma@jaguarmicro.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=rrichter@amd.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