All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Xiao Yang <yangx.jy@fujitsu.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v2 2/2] RDMA/rxe: Support RDMA Atomic Write operation
Date: Thu, 13 Jan 2022 20:16:05 +0800	[thread overview]
Message-ID: <202201132027.agYTyFRu-lkp@intel.com> (raw)
In-Reply-To: <20220113030350.2492841-3-yangx.jy@fujitsu.com>

Hi Xiao,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on v5.16]
[also build test ERROR on next-20220113]
[cannot apply to rdma/for-next]
[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]

url:    https://github.com/0day-ci/linux/commits/Xiao-Yang/RDMA-rxe-Add-RDMA-Atomic-Write-operation/20220113-110548
base:    df0cc57e057f18e44dac8e6c18aba47ab53202f9
config: riscv-randconfig-r035-20220113 (https://download.01.org/0day-ci/archive/20220113/202201132027.agYTyFRu-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project d1021978b8e7e35dcc30201ca1731d64b5a602a8)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install riscv cross compiling tool for clang build
        # apt-get install binutils-riscv64-linux-gnu
        # https://github.com/0day-ci/linux/commit/4294d58609cfb4c296c7937eafd58e044a4d81c6
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Xiao-Yang/RDMA-rxe-Add-RDMA-Atomic-Write-operation/20220113-110548
        git checkout 4294d58609cfb4c296c7937eafd58e044a4d81c6
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash drivers/infiniband/sw/rxe/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> drivers/infiniband/sw/rxe/rxe_resp.c:606:2: error: call to __compiletime_assert_499 declared with 'error' attribute: Need native word sized stores/loads for atomicity.
           smp_store_release(dst, *src);
           ^
   include/asm-generic/barrier.h:162:2: note: expanded from macro 'smp_store_release'
           compiletime_assert_atomic_type(*p);                             \
           ^
   include/linux/compiler_types.h:338:2: note: expanded from macro 'compiletime_assert_atomic_type'
           compiletime_assert(__native_word(t),                            \
           ^
   include/linux/compiler_types.h:335:2: note: expanded from macro 'compiletime_assert'
           _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
           ^
   include/linux/compiler_types.h:323:2: note: expanded from macro '_compiletime_assert'
           __compiletime_assert(condition, msg, prefix, suffix)
           ^
   include/linux/compiler_types.h:316:4: note: expanded from macro '__compiletime_assert'
                           prefix ## suffix();                             \
                           ^
   <scratch space>:165:1: note: expanded from here
   __compiletime_assert_499
   ^
   1 error generated.


vim +/error +606 drivers/infiniband/sw/rxe/rxe_resp.c

   593	
   594	static enum resp_states process_atomic_write(struct rxe_qp *qp,
   595						     struct rxe_pkt_info *pkt)
   596	{
   597		struct rxe_mr *mr = qp->resp.mr;
   598	
   599		u64 *src = payload_addr(pkt);
   600	
   601		u64 *dst = iova_to_vaddr(mr, qp->resp.va + qp->resp.offset, sizeof(u64));
   602		if (!dst || (uintptr_t)dst & 7)
   603			return RESPST_ERR_MISALIGNED_ATOMIC;
   604	
   605		/* Do atomic write after all prior operations have completed */
 > 606		smp_store_release(dst, *src);
   607	
   608		/* decrease resp.resid to zero */
   609		qp->resp.resid -= sizeof(u64);
   610	
   611		return RESPST_NONE;
   612	}
   613	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v2 2/2] RDMA/rxe: Support RDMA Atomic Write operation
Date: Thu, 13 Jan 2022 20:16:05 +0800	[thread overview]
Message-ID: <202201132027.agYTyFRu-lkp@intel.com> (raw)
In-Reply-To: <20220113030350.2492841-3-yangx.jy@fujitsu.com>

[-- Attachment #1: Type: text/plain, Size: 3899 bytes --]

Hi Xiao,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on v5.16]
[also build test ERROR on next-20220113]
[cannot apply to rdma/for-next]
[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]

url:    https://github.com/0day-ci/linux/commits/Xiao-Yang/RDMA-rxe-Add-RDMA-Atomic-Write-operation/20220113-110548
base:    df0cc57e057f18e44dac8e6c18aba47ab53202f9
config: riscv-randconfig-r035-20220113 (https://download.01.org/0day-ci/archive/20220113/202201132027.agYTyFRu-lkp(a)intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project d1021978b8e7e35dcc30201ca1731d64b5a602a8)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install riscv cross compiling tool for clang build
        # apt-get install binutils-riscv64-linux-gnu
        # https://github.com/0day-ci/linux/commit/4294d58609cfb4c296c7937eafd58e044a4d81c6
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Xiao-Yang/RDMA-rxe-Add-RDMA-Atomic-Write-operation/20220113-110548
        git checkout 4294d58609cfb4c296c7937eafd58e044a4d81c6
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash drivers/infiniband/sw/rxe/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> drivers/infiniband/sw/rxe/rxe_resp.c:606:2: error: call to __compiletime_assert_499 declared with 'error' attribute: Need native word sized stores/loads for atomicity.
           smp_store_release(dst, *src);
           ^
   include/asm-generic/barrier.h:162:2: note: expanded from macro 'smp_store_release'
           compiletime_assert_atomic_type(*p);                             \
           ^
   include/linux/compiler_types.h:338:2: note: expanded from macro 'compiletime_assert_atomic_type'
           compiletime_assert(__native_word(t),                            \
           ^
   include/linux/compiler_types.h:335:2: note: expanded from macro 'compiletime_assert'
           _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
           ^
   include/linux/compiler_types.h:323:2: note: expanded from macro '_compiletime_assert'
           __compiletime_assert(condition, msg, prefix, suffix)
           ^
   include/linux/compiler_types.h:316:4: note: expanded from macro '__compiletime_assert'
                           prefix ## suffix();                             \
                           ^
   <scratch space>:165:1: note: expanded from here
   __compiletime_assert_499
   ^
   1 error generated.


vim +/error +606 drivers/infiniband/sw/rxe/rxe_resp.c

   593	
   594	static enum resp_states process_atomic_write(struct rxe_qp *qp,
   595						     struct rxe_pkt_info *pkt)
   596	{
   597		struct rxe_mr *mr = qp->resp.mr;
   598	
   599		u64 *src = payload_addr(pkt);
   600	
   601		u64 *dst = iova_to_vaddr(mr, qp->resp.va + qp->resp.offset, sizeof(u64));
   602		if (!dst || (uintptr_t)dst & 7)
   603			return RESPST_ERR_MISALIGNED_ATOMIC;
   604	
   605		/* Do atomic write after all prior operations have completed */
 > 606		smp_store_release(dst, *src);
   607	
   608		/* decrease resp.resid to zero */
   609		qp->resp.resid -= sizeof(u64);
   610	
   611		return RESPST_NONE;
   612	}
   613	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  parent reply	other threads:[~2022-01-13 12:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  3:03 [RFC PATCH v2 0/2] RDMA/rxe: Add RDMA Atomic Write operation Xiao Yang
2022-01-13  3:03 ` [RFC PATCH v2 1/2] RDMA/rxe: Rename send_atomic_ack() and atomic member of struct resp_res Xiao Yang
2022-01-13  3:03 ` [RFC PATCH v2 2/2] RDMA/rxe: Support RDMA Atomic Write operation Xiao Yang
2022-01-13 11:35   ` kernel test robot
2022-01-13 12:16   ` kernel test robot [this message]
2022-01-13 12:16     ` kernel test robot
2022-01-17 13:16   ` Jason Gunthorpe
2022-01-18  8:01     ` yangx.jy
2022-01-18 12:35       ` Jason Gunthorpe
2022-01-19  1:54         ` lizhijian
2022-01-19 12:36           ` Jason Gunthorpe
2022-01-19 16:47             ` Ira Weiny
2022-01-20 12:07             ` Li, Zhijian
2022-01-21 12:58               ` Jason Gunthorpe
2022-01-21 16:06                 ` Ira Weiny
2022-01-21 16:08                   ` Ira Weiny
2022-01-24  3:47                     ` lizhijian
2022-01-27  9:37                   ` yangx.jy
2022-01-27  9:57                     ` hch
2022-01-27 18:08                       ` Ira Weiny
2022-01-28  6:16                         ` hch
2022-01-28 19:15                           ` Ira Weiny
2022-02-10 11:06                             ` yangx.jy
2022-02-11 18:30                               ` Ira Weiny
2022-01-18  8:02     ` yangx.jy
2022-01-18  8:04     ` yangx.jy
2022-01-18  9:03       ` yangx.jy

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=202201132027.agYTyFRu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=llvm@lists.linux.dev \
    --cc=yangx.jy@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 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.