summaryrefslogtreecommitdiffstats
path: root/include/uapi/linux/pci_regs.h
diff options
context:
space:
mode:
authorDave Jiang <dave.jiang@intel.com>2024-05-02 09:57:34 -0700
committerBjorn Helgaas <bhelgaas@google.com>2024-05-08 13:25:46 -0500
commit934edcd436dca0447e0d3691a908394ba16d06c3 (patch)
tree0230687d2624fdba8b22430d4d8bd26451c7d236 /include/uapi/linux/pci_regs.h
parent53c49b6e6dd2ebc1d3257ae838e067699229bc8d (diff)
downloadlinux-934edcd436dca0447e0d3691a908394ba16d06c3.tar.gz
linux-934edcd436dca0447e0d3691a908394ba16d06c3.tar.bz2
linux-934edcd436dca0447e0d3691a908394ba16d06c3.zip
cxl: Add post-reset warning if reset results in loss of previously committed HDM decoders
Secondary Bus Reset (SBR) is equivalent to a device being hot removed and inserted again. Doing a SBR on a CXL type 3 device is problematic if the exported device memory is part of system memory that cannot be offlined. The event is equivalent to violently ripping out that range of memory from the kernel. While the hardware requires the "Unmask SBR" bit set in the Port Control Extensions register and the kernel currently does not unmask it, user can unmask this bit via setpci or similar tool. The driver does not have a way to detect whether a reset coming from the PCI subsystem is a Function Level Reset (FLR) or SBR. The only way to detect is to note if a decoder is marked as enabled in software but the decoder control register indicates it's not committed. Add a helper function to find discrepancy between the decoder software state versus the hardware register state. Suggested-by: Dan Williams <dan.j.williams@intel.com> Link: https://lore.kernel.org/r/20240502165851.1948523-6-dave.jiang@intel.com Signed-off-by: Dave Jiang <dave.jiang@intel.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'include/uapi/linux/pci_regs.h')
0 files changed, 0 insertions, 0 deletions