From: Dave Jiang <dave.jiang@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: [GIT PULL] Compute Express Link (CXL) Fixes for 6.9-rc4
Date: Thu, 11 Apr 2024 16:37:10 -0700 [thread overview]
Message-ID: <02842127-1716-4372-a77e-d742d7dcab8a@intel.com> (raw)
Hi Linus, please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl tags/cxl-fixes-6.9-rc4
...to receive a collection of fixes for the CXL subsystem.
A set of patches to deal with fixing the computation of access_coordinate performance data computed for the CXL device path.
- An error in the PCI topology walk is addressed to pick up the host bridge performance data from the correct location along the path.
- The incorrect calculation while doing picoseconds to nanoseconds conversion of the CDAT latency data is fixed.
- And a check to verify that the access_coordinate data are valid (not zeroes) is added in the computation path to prevent failed perf data from leaking to the user space via sysfs.
Fix an of off by 1 indexing of Clear Event Record handles in cxl_clear_event_record().
Fix of a use before init of a variable map->reg_type in cxl_decode_regblock().
Fix of initialization of mbox_cmd.size_out in cxl_mem_get_records_log() before sending to hardware.
This has build success notification from the kbuild-robot. They have been in the -next for a week with no reported issues.
---
The following changes since commit 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git tags/cxl-fixes-6.9-rc4
for you to fetch changes up to 7bcf809b1e7889ab7e75fe1fcf8f1a98332f36d2:
cxl: Add checks to access_coordinate calculation to fail missing data (2024-04-08 08:25:21 -0700)
----------------------------------------------------------------
cxl fixes for v6.9-rc4
- Fix index of Clear Event Record handles in cxl_clear_event_record().
- Fix use before init of map->reg_type in cxl_decode_regblock().
- Fix initialization of mbox_cmd.size_out in cxl_mem_get_records_log().
- Series fixing CXL path access_coordinate computation.
- Remove unneded check of iter in loop.
- Fix of retrieving of access_coordinate in PCI topology walk.
- Fix of incorrect region access_coordinate data calculation.
- Consolidate of access_coordinates attached to downstream port
context.
- Add check to validate access_coordinate validity to prevent
incorrect data being exposed via sysfs.
----------------------------------------------------------------
Dave Jiang (6):
cxl/core/regs: Fix usage of map->reg_type in cxl_decode_regblock() before assigned
cxl: Remove checking of iter in cxl_endpoint_get_perf_coordinates()
cxl: Fix retrieving of access_coordinates in PCIe path
cxl: Fix incorrect region perf data calculation
cxl: Consolidate dport access_coordinate ->hb_coord and ->sw_coord into ->coord
cxl: Add checks to access_coordinate calculation to fail missing data
Kwangjin Ko (1):
cxl/core: Fix initialization of mbox_cmd.size_out in get event
Yuquan Wang (1):
cxl/mem: Fix for the index of Clear Event Record Handle
drivers/cxl/acpi.c | 13 +---
drivers/cxl/core/cdat.c | 152 ++++++++++++++++++++++---------------------
drivers/cxl/core/mbox.c | 5 +-
drivers/cxl/core/port.c | 114 +++++++++++++++++++-------------
drivers/cxl/core/regs.c | 5 +-
drivers/cxl/cxl.h | 8 +--
drivers/cxl/cxlmem.h | 2 +-
tools/testing/cxl/test/cxl.c | 10 +--
8 files changed, 164 insertions(+), 145 deletions(-)
next reply other threads:[~2024-04-11 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 23:37 Dave Jiang [this message]
2024-04-11 23:53 ` [GIT PULL] Compute Express Link (CXL) Fixes for 6.9-rc4 pr-tracker-bot
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=02842127-1716-4372-a77e-d742d7dcab8a@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).