diff options
| author | Richard Cheng <icheng@nvidia.com> | 2026-09-14 17:08:56 +0800 |
|---|---|---|
| committer | Dave Jiang <dave.jiang@intel.com> | 2026-09-15 08:35:58 -0700 |
| commit | 057dc2892d1f69f457119f0080e2acacfcc9a9d0 (patch) | |
| tree | bf8f7143b531e6c0a580f4a8a88eaf6fb9deebfc /tools/perf/scripts/python/task-analyzer.py | |
| parent | fd73f4a6659897191fa0d40695fe370925dd3780 (diff) | |
| download | linux-next-057dc2892d1f69f457119f0080e2acacfcc9a9d0.tar.gz linux-next-057dc2892d1f69f457119f0080e2acacfcc9a9d0.zip | |
cxl/region: Simplify poison_by_decoder() error handling
"rc" carries both an error code and the loop control
signal for device_for_each_child(), so returning it bare is misleading,
the early guards mean "keep walking", not "no error". Zeroing "rc" to
forgive an -EFAULT on a RAM partition adds to that by discarding what
the device actually returned.
Return a literal 0 where the walk should continue, and test the
forgiven case directly instead of rewriting "rc". Give that test a
name, poison_efault_forgiven(), so cxl_get_poison_unmapped() and
poison_by_decoder() spell the same rule the same way. No functional
change.
Suggested-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Signed-off-by: Richard Cheng <icheng@nvidia.com>
Reviewed-by: Alison Schofield <alison.schofield@intel.com>
Link: https://patch.msgid.link/20260914090858.19181-2-icheng@nvidia.com
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions