From: kernel test robot <lkp@intel.com>
To: Stefan Roesch <shr@devkernel.io>, kernel-team@fb.com
Cc: oe-kbuild-all@lists.linux.dev, shr@devkernel.io,
akpm@linux-foundation.org, david@redhat.com, hannes@cmpxchg.org,
riel@surriel.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v2 1/4] mm/ksm: add ksm advisor
Date: Sat, 28 Oct 2023 15:33:05 +0800 [thread overview]
Message-ID: <202310281513.BWtopDPM-lkp@intel.com> (raw)
In-Reply-To: <20231028000945.2428830-2-shr@devkernel.io>
Hi Stefan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 12d04a7bf0da67321229d2bc8b1a7074d65415a9]
url: https://github.com/intel-lab-lkp/linux/commits/Stefan-Roesch/mm-ksm-add-ksm-advisor/20231028-081347
base: 12d04a7bf0da67321229d2bc8b1a7074d65415a9
patch link: https://lore.kernel.org/r/20231028000945.2428830-2-shr%40devkernel.io
patch subject: [PATCH v2 1/4] mm/ksm: add ksm advisor
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20231028/202310281513.BWtopDPM-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231028/202310281513.BWtopDPM-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/202310281513.BWtopDPM-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/ksm.c:334: warning: Function parameter or member 'cpu_time' not described in 'advisor_ctx'
vim +334 mm/ksm.c
321
322 /**
323 * struct advisor_ctx - metadata for KSM advisor
324 * @start_scan: start time of the current scan
325 * @scan_time: scan time of previous scan
326 * @change: change in percent to pages_to_scan parameter
327 * @cpu_percent: average cpu percent usage of the ksmd thread for the last scan
328 */
329 struct advisor_ctx {
330 ktime_t start_scan;
331 unsigned long scan_time;
332 unsigned long change;
333 unsigned long long cpu_time;
> 334 };
335 static struct advisor_ctx advisor_ctx;
336
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-28 7:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 0:09 [PATCH v2 0/4] mm/ksm: Add ksm advisor Stefan Roesch
2023-10-28 0:09 ` [PATCH v2 1/4] mm/ksm: add " Stefan Roesch
2023-10-28 7:33 ` kernel test robot [this message]
2023-11-20 10:51 ` David Hildenbrand
2023-11-22 17:20 ` Stefan Roesch
2023-11-24 15:37 ` David Hildenbrand
2023-11-24 15:39 ` David Hildenbrand
2023-10-28 0:09 ` [PATCH v2 2/4] mm/ksm: add sysfs knobs for advisor Stefan Roesch
2023-11-20 10:32 ` David Hildenbrand
2023-11-22 17:42 ` Stefan Roesch
2023-11-22 17:43 ` Stefan Roesch
2023-11-20 10:53 ` David Hildenbrand
2023-11-22 17:41 ` Stefan Roesch
2023-10-28 0:09 ` [PATCH v2 3/4] mm/ksm: add tracepoint for ksm advisor Stefan Roesch
2023-10-28 0:09 ` [PATCH v2 4/4] mm/ksm: document ksm advisor and its sysfs knobs Stefan Roesch
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=202310281513.BWtopDPM-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=riel@surriel.com \
--cc=shr@devkernel.io \
/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.