linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Oskolkov <posk@posk.io>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Andy Lutomirski <luto@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-api@vger.kernel.org, llvm@lists.linux.dev,
	kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Paul Turner <pjt@google.com>
Subject: Re: [PATCH v0.9 3/6] sched/umcg: implement UMCG syscalls
Date: Mon, 22 Nov 2021 12:17:04 -0800	[thread overview]
Message-ID: <CAFTs51Xr0jae345RA=uYq5-ZwPu4T20CcPBeRQqxGrhL73enfA@mail.gmail.com> (raw)
In-Reply-To: <202111221834.Q9LmeisY-lkp@intel.com>

On Mon, Nov 22, 2021 at 2:02 AM kernel test robot <lkp@intel.com> wrote:
>
> Hi Peter,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on cb0e52b7748737b2cf6481fdd9b920ce7e1ebbdf]
>
> url:    https://github.com/0day-ci/linux/commits/Peter-Oskolkov/sched-mm-x86-uaccess-implement-User-Managed-Concurrency-Groups/20211122-052209
> base:   cb0e52b7748737b2cf6481fdd9b920ce7e1ebbdf
> config: x86_64-randconfig-c007-20211121 (attached as .config)
> 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
>         # https://github.com/0day-ci/linux/commit/e455791cacec2b140558a717d2b8b07f5561a251
>         git remote add linux-review https://github.com/0day-ci/linux
>         git fetch --no-tags linux-review Peter-Oskolkov/sched-mm-x86-uaccess-implement-User-Managed-Concurrency-Groups/20211122-052209
>         git checkout e455791cacec2b140558a717d2b8b07f5561a251
>         # save the attached .config to linux build tree
>         mkdir build_dir
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
>
> 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 >>):
>
>    In file included from <built-in>:1:
> >> ./usr/include/linux/umcg.h:80:2: error: unknown type name 'u64'
>            u64     state_ts;               /* r/w */

I figured it out - lkp manages to compile uapi so that it sees
__u32/__u64 but not u32/u64. I'll make the change.

As __u64 is actually a different type from u64 (long unsigned int vs
long long unsigned int), I'll need to make corresponding changes in
other files to avoid warnings of "comparing different types" sort.

Why does the kernel have both __u64 and u64, and have them defined as
different types? (This is not really a question, just a complaint).

>            ^
> >> ./usr/include/linux/umcg.h:91:2: error: unknown type name 'u32'
>            u32     next_tid;               /* r   */
>            ^
>    ./usr/include/linux/umcg.h:93:2: error: unknown type name 'u32'
>            u32     flags;                  /* Reserved; must be zero. */
>            ^
>    ./usr/include/linux/umcg.h:101:2: error: unknown type name 'u64'
>            u64     idle_workers_ptr;       /* r/w */
>            ^
>    ./usr/include/linux/umcg.h:107:2: error: unknown type name 'u64'
>            u64     idle_server_tid_ptr;    /* r   */
>            ^
>    5 errors generated.
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

  reply	other threads:[~2021-11-22 20:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-21 21:20 [PATCH v0.9 0/6] sched,mm,x86/uaccess: implement User Managed Concurrency Groups Peter Oskolkov
2021-11-21 21:20 ` [PATCH v0.9 1/6] sched/umcg: add WF_CURRENT_CPU and externise ttwu Peter Oskolkov
2021-11-21 21:20 ` [PATCH v0.9 2/6] mm, x86/uaccess: add userspace atomic helpers Peter Oskolkov
2021-11-22  7:54   ` kernel test robot
2021-11-21 21:20 ` [PATCH v0.9 3/6] sched/umcg: implement UMCG syscalls Peter Oskolkov
2021-11-22  9:09   ` kernel test robot
2021-11-22 10:01   ` kernel test robot
2021-11-22 20:17     ` Peter Oskolkov [this message]
2021-11-22 14:45   ` kernel test robot
2021-11-21 21:20 ` [PATCH v0.9 4/6] sched/umcg, lib/umcg: implement libumcg Peter Oskolkov
2021-11-21 21:20 ` [PATCH v0.9 5/6] sched/umcg: add Documentation/userspace-api/umcg.txt Peter Oskolkov
2021-11-21 21:20 ` [PATCH v0.9 6/6] sched/umcg, lib/umcg: add tools/lib/umcg/libumcg.txt Peter Oskolkov

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='CAFTs51Xr0jae345RA=uYq5-ZwPu4T20CcPBeRQqxGrhL73enfA@mail.gmail.com' \
    --to=posk@posk.io \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=tglx@linutronix.de \
    /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 NNTP newsgroup(s).