From: Alison Schofield <alison.schofield@intel.com>
To: Foryun Ma <foryun.ma@jaguarmicro.com>
Cc: dave.jiang@intel.com, dave@stgolabs.net,
linux-cxl@vger.kernel.org, rrichter@amd.com,
angus.chen@jaguarmicro.com
Subject: Re: [PATCH] cxl/core/pci: Move reading of control register to immediately before usage
Date: Wed, 29 May 2024 20:43:01 -0700 [thread overview]
Message-ID: <Zlf1xa3O0DNu8Tv3@aschofie-mobl2> (raw)
In-Reply-To: <20240530013216.491-1-foryun.ma@jaguarmicro.com>
On Thu, May 30, 2024 at 09:32:16AM +0800, Foryun Ma wrote:
> 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.
>
Thanks again. I like DaveJ's suggested wording better than what I
offered.
Please follow-up with:
- needs to be [PATCH v2], a changelog, and recipients list update.
These are described in the kernel documentation for submitting patches [1]
Check out the section of Responding to Reviews also.
FWIW - here's a sample usage that gets the recipient list for a HEAD commit:
$ git show HEAD | perl scripts/get_maintainer.pl --nogit-fallback --no-rolestats
[1] https://docs.kernel.org/process/submitting-patches.html
> Signed-off-by: Foryun Ma <foryun.ma@jaguarmicro.com>
> ---
> 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
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2024-05-30 3:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 1:32 [PATCH] cxl/core/pci: Move reading of control register to immediately before usage Foryun Ma
2024-05-30 3:43 ` Alison Schofield [this message]
2024-05-30 6:47 ` [PATCH v2] " Foryun Ma
2024-05-31 15:31 ` Dan Williams
2024-06-03 15:52 ` Alison Schofield
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=Zlf1xa3O0DNu8Tv3@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=angus.chen@jaguarmicro.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=foryun.ma@jaguarmicro.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