From: Dave Jiang <dave.jiang@intel.com>
To: "Kobayashi,Daisuke" <kobayashi.da-06@fujitsu.com>,
kobayashi.da-06@jp.fujitsu.com, linux-cxl@vger.kernel.org
Cc: y-goto@fujitsu.com, linux-pci@vger.kernel.org, mj@ucw.cz,
dan.j.williams@intel.com
Subject: Re: [PATCH v4 2/3] cxl/core/regs: Add rcd_regs initialization at __rcrb_to_component()
Date: Tue, 9 Apr 2024 12:15:50 -0700 [thread overview]
Message-ID: <519bf934-840b-496d-9a5e-7b183c5be258@intel.com> (raw)
In-Reply-To: <20240409073528.13214-3-kobayashi.da-06@fujitsu.com>
On 4/9/24 12:35 AM, Kobayashi,Daisuke wrote:
> Add rcd_regs initialization at __rcrb_to_component() to cache the cxl1.1
> device link status information. Reduce access to the memory map area
> where the RCRB is located by caching the cxl1.1 device link status information.
>
> Signed-off-by: "Kobayashi,Daisuke" <kobayashi.da-06@fujitsu.com>
> ---
> drivers/cxl/core/regs.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/drivers/cxl/core/regs.c b/drivers/cxl/core/regs.c
> index 372786f80955..308eb951613e 100644
> --- a/drivers/cxl/core/regs.c
> +++ b/drivers/cxl/core/regs.c
> @@ -514,6 +514,8 @@ resource_size_t __rcrb_to_component(struct device *dev, struct cxl_rcrb_info *ri
> u32 bar0, bar1;
> u16 cmd;
> u32 id;
> + u16 offset;
> + u32 cap_hdr;
>
> if (which == CXL_RCRB_UPSTREAM)
> rcrb += SZ_4K;
> @@ -537,6 +539,22 @@ resource_size_t __rcrb_to_component(struct device *dev, struct cxl_rcrb_info *ri
> cmd = readw(addr + PCI_COMMAND);
> bar0 = readl(addr + PCI_BASE_ADDRESS_0);
> bar1 = readl(addr + PCI_BASE_ADDRESS_1);
> +
> + offset = readw(addr + PCI_CAPABILITY_LIST);
> + offset &= 0x00ff;
GENMASK(7,0) is preferred to 0x00ff. Although a properly defined mask would be nice.
Also please consider using FIELD_GET().
> + cap_hdr = readl(addr + offset);
> + while ((cap_hdr & 0x000000ff) != PCI_CAP_ID_EXP) {
Same comment as above
> + offset = (cap_hdr >> 8) & 0x000000ff;
Also here
> + if (offset == 0) // End of capability list
Please use /* */ instead of // for Linux kernel code
> + break;
> + cap_hdr = readl(addr + offset);
> + }
> + if (offset) {
> + ri->rcd_lnkcap = readl(addr + offset + PCI_EXP_LNKCAP);
> + ri->rcd_lnkctrl = readl(addr + offset + PCI_EXP_LNKCTL);
> + ri->rcd_lnkstatus = readl(addr + offset + PCI_EXP_LNKSTA);
> + }
> +
> iounmap(addr);
> release_mem_region(rcrb, SZ_4K);
>
next prev parent reply other threads:[~2024-04-09 19:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 7:35 [PATCH v4 0/3] cxl: Export cxl1.1 device link status to sysfs Kobayashi,Daisuke
2024-04-09 7:35 ` [PATCH v4 1/3] cxl: Add rcd_regs to cxl_rcrb_info Kobayashi,Daisuke
2024-04-09 19:08 ` Dave Jiang
2024-04-09 7:35 ` [PATCH v4 2/3] cxl/core/regs: Add rcd_regs initialization at __rcrb_to_component() Kobayashi,Daisuke
2024-04-09 19:15 ` Dave Jiang [this message]
2024-04-10 7:14 ` Daisuke Kobayashi (Fujitsu)
2024-04-09 7:35 ` [PATCH v4 3/3] cxl/pci: Add sysfs attribute for CXL 1.1 device link status Kobayashi,Daisuke
2024-04-09 15:05 ` Bjorn Helgaas
2024-04-09 18:04 ` Dan Williams
2024-04-09 22:18 ` Lukas Wunner
2024-04-09 21:33 ` Dan Williams
2024-04-09 21:47 ` Dan Williams
2024-04-10 7:22 ` Daisuke Kobayashi (Fujitsu)
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=519bf934-840b-496d-9a5e-7b183c5be258@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=kobayashi.da-06@fujitsu.com \
--cc=kobayashi.da-06@jp.fujitsu.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mj@ucw.cz \
--cc=y-goto@fujitsu.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