From: kernel test robot <lkp@intel.com>
To: shiju.jose@huawei.com, linux-cxl@vger.kernel.org,
dan.j.williams@intel.com, dave.jiang@intel.com,
jonathan.cameron@huawei.com, alison.schofield@intel.com,
dave@stgolabs.net, vishal.l.verma@intel.com, ira.weiny@intel.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
tanxiaofei@huawei.com, prime.zeng@hisilicon.com,
linuxarm@huawei.com, shiju.jose@huawei.com
Subject: Re: [PATCH 2/4] cxl/events: Add extra validity checks for corrected memory error count in General Media Event Record
Date: Thu, 17 Jul 2025 11:32:30 +0800 [thread overview]
Message-ID: <202507171153.p2RrAdN4-lkp@intel.com> (raw)
In-Reply-To: <20250716104945.2002-3-shiju.jose@huawei.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on cxl/next]
[also build test WARNING on linus/master v6.16-rc6 next-20250716]
[cannot apply to cxl/pending]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/shiju-jose-huawei-com/cxl-events-Update-Common-Event-Record-to-CXL-spec-rev-3-2/20250716-192336
base: https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git next
patch link: https://lore.kernel.org/r/20250716104945.2002-3-shiju.jose%40huawei.com
patch subject: [PATCH 2/4] cxl/events: Add extra validity checks for corrected memory error count in General Media Event Record
config: arm-randconfig-004-20250717 (https://download.01.org/0day-ci/archive/20250717/202507171153.p2RrAdN4-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 16534d19bf50bde879a83f0ae62875e2c5120e64)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250717/202507171153.p2RrAdN4-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202507171153.p2RrAdN4-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/cxl/core/mbox.c:933:27: warning: address of array 'evt->gen_media.cme_count' will always evaluate to 'true' [-Wpointer-bool-conversion]
933 | !evt->gen_media.cme_count);
| ~~~~~~~~~~~~~~~~^~~~~~~~~
include/asm-generic/bug.h:148:18: note: expanded from macro 'WARN_ON_ONCE'
148 | DO_ONCE_LITE_IF(condition, WARN_ON, 1)
| ^~~~~~~~~
include/linux/once_lite.h:28:27: note: expanded from macro 'DO_ONCE_LITE_IF'
28 | bool __ret_do_once = !!(condition); \
| ^~~~~~~~~
1 warning generated.
vim +933 drivers/cxl/core/mbox.c
888
889 void cxl_event_trace_record(const struct cxl_memdev *cxlmd,
890 enum cxl_event_log_type type,
891 enum cxl_event_type event_type,
892 const uuid_t *uuid, union cxl_event *evt)
893 {
894 if (event_type == CXL_CPER_EVENT_MEM_MODULE) {
895 trace_cxl_memory_module(cxlmd, type, &evt->mem_module);
896 return;
897 }
898 if (event_type == CXL_CPER_EVENT_GENERIC) {
899 trace_cxl_generic_event(cxlmd, type, uuid, &evt->generic);
900 return;
901 }
902
903 if (trace_cxl_general_media_enabled() || trace_cxl_dram_enabled()) {
904 u64 dpa, hpa = ULLONG_MAX, hpa_alias = ULLONG_MAX;
905 struct cxl_region *cxlr;
906
907 /*
908 * These trace points are annotated with HPA and region
909 * translations. Take topology mutation locks and lookup
910 * { HPA, REGION } from { DPA, MEMDEV } in the event record.
911 */
912 guard(rwsem_read)(&cxl_region_rwsem);
913 guard(rwsem_read)(&cxl_dpa_rwsem);
914
915 dpa = le64_to_cpu(evt->media_hdr.phys_addr) & CXL_DPA_MASK;
916 cxlr = cxl_dpa_to_region(cxlmd, dpa);
917 if (cxlr) {
918 u64 cache_size = cxlr->params.cache_size;
919
920 hpa = cxl_dpa_to_hpa(cxlr, cxlmd, dpa);
921 if (cache_size)
922 hpa_alias = hpa - cache_size;
923 }
924
925 if (event_type == CXL_CPER_EVENT_GEN_MEDIA) {
926 if (cxl_store_rec_gen_media((struct cxl_memdev *)cxlmd, evt))
927 dev_dbg(&cxlmd->dev, "CXL store rec_gen_media failed\n");
928
929 if (evt->gen_media.media_hdr.descriptor &
930 CXL_GMER_EVT_DESC_THRESHOLD_EVENT)
931 WARN_ON_ONCE((evt->gen_media.media_hdr.type &
932 CXL_GMER_MEM_EVT_TYPE_AP_CME_COUNTER_EXPIRE) &&
> 933 !evt->gen_media.cme_count);
934 else
935 WARN_ON_ONCE(evt->gen_media.media_hdr.type &
936 CXL_GMER_MEM_EVT_TYPE_AP_CME_COUNTER_EXPIRE);
937
938 trace_cxl_general_media(cxlmd, type, cxlr, hpa,
939 hpa_alias, &evt->gen_media);
940 } else if (event_type == CXL_CPER_EVENT_DRAM) {
941 if (cxl_store_rec_dram((struct cxl_memdev *)cxlmd, evt))
942 dev_dbg(&cxlmd->dev, "CXL store rec_dram failed\n");
943
944 trace_cxl_dram(cxlmd, type, cxlr, hpa, hpa_alias,
945 &evt->dram);
946 }
947 }
948 }
949 EXPORT_SYMBOL_NS_GPL(cxl_event_trace_record, "CXL");
950
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-07-17 3:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 10:49 [PATCH 0/4] cxl/events: Update to rev 3.2, improvements and add trace memory sparing event record shiju.jose
2025-07-16 10:49 ` [PATCH 1/4] cxl/events: Update Common Event Record to CXL spec rev 3.2 shiju.jose
2025-07-16 12:53 ` Jonathan Cameron
2025-07-16 10:49 ` [PATCH 2/4] cxl/events: Add extra validity checks for corrected memory error count in General Media Event Record shiju.jose
2025-07-16 13:04 ` Jonathan Cameron
2025-07-16 21:40 ` Dave Jiang
2025-07-17 3:32 ` kernel test robot [this message]
2025-07-16 10:49 ` [PATCH 3/4] cxl/events: Add extra validity checks for CVME count in DRAM " shiju.jose
2025-07-16 13:07 ` Jonathan Cameron
2025-07-16 21:53 ` Dave Jiang
2025-07-17 5:16 ` kernel test robot
2025-07-16 10:49 ` [PATCH 4/4] cxl/events: Trace Memory Sparing " shiju.jose
2025-07-16 13:16 ` Jonathan Cameron
2025-07-16 15:07 ` Shiju Jose
2025-07-16 22:23 ` Dave Jiang
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=202507171153.p2RrAdN4-lkp@intel.com \
--to=lkp@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=prime.zeng@hisilicon.com \
--cc=shiju.jose@huawei.com \
--cc=tanxiaofei@huawei.com \
--cc=vishal.l.verma@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.