dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Rodrigo Siqueira" <Rodrigo.Siqueira@amd.com>,
	"Harry Wentland" <harry.wentland@amd.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Peter Zijlstra" <peterz@infradead.org>,
	aric.cyr@amd.com
Cc: kbuild-all@lists.01.org, amd-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/4] drm/amd/display: Add FPU event trace
Date: Thu, 1 Apr 2021 03:28:36 +0800	[thread overview]
Message-ID: <202104010342.0B6CU5pd-lkp@intel.com> (raw)
In-Reply-To: <20210331122502.1031073-3-Rodrigo.Siqueira@amd.com>

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

Hi Rodrigo,

I love your patch! Perhaps something to improve:

[auto build test WARNING on next-20210331]
[cannot apply to linus/master v5.12-rc5 v5.12-rc4 v5.12-rc3 v5.12-rc5]
[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/Rodrigo-Siqueira/drm-amd-display-Base-changes-for-isolating-FPU-operation-in-a-single-place/20210331-202750
base:    7a43c78d0573e0bbbb0456b033e2b9a895b89464
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/5859110d0579f7ee57ca1b1840c3960492a9c0c0
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Rodrigo-Siqueira/drm-amd-display-Base-changes-for-isolating-FPU-operation-in-a-single-place/20210331-202750
        git checkout 5859110d0579f7ee57ca1b1840c3960492a9c0c0
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

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

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.c:41:6: warning: no previous prototype for 'dc_fpu_begin' [-Wmissing-prototypes]
      41 | void dc_fpu_begin(const char *function_name, const int line)
         |      ^~~~~~~~~~~~
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.c:57:6: warning: no previous prototype for 'dc_fpu_end' [-Wmissing-prototypes]
      57 | void dc_fpu_end(const char *function_name, const int line)
         |      ^~~~~~~~~~


vim +/dc_fpu_begin +41 drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/dc_fpu.c

    30	
    31	/**
    32	 * dc_fpu_begin - Enables FPU protection
    33	 * @function_name: A string containing the function name for debug purposes
    34	 * @line: A-line number where DC_FP_START was invoked for debug purpose
    35	 *
    36	 * This function is responsible for managing the use of kernel_fpu_begin() with
    37	 * the advantage of providing an event trace for debugging.
    38	 *
    39	 * Note: Do not call this function directly; always use DC_FP_START().
    40	 */
  > 41	void dc_fpu_begin(const char *function_name, const int line)
    42	{
    43		TRACE_DCN_FPU(true, function_name, line);
    44		kernel_fpu_begin();
    45	}
    46	
    47	/**
    48	 * dc_fpu_end - Disable FPU protection
    49	 * @function_name: A string containing the function name for debug purposes
    50	 * @line: A-line number where DC_FP_END was invoked for debug purpose
    51	 *
    52	 * This function is responsible for managing the use of kernel_fpu_end() with
    53	 * the advantage of providing an event trace for debugging.
    54	 *
    55	 * Note: Do not call this function directly; always use DC_FP_END().
    56	 */
  > 57	void dc_fpu_end(const char *function_name, const int line)

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

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 65866 bytes --]

[-- Attachment #3: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2021-03-31 19:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 12:24 [PATCH 0/4] drm/amd/display: Base changes for isolating FPU operation in a single place Rodrigo Siqueira
2021-03-31 12:24 ` [PATCH 1/4] drm/amd/display: Introduce FPU directory inside DC Rodrigo Siqueira
2021-03-31 17:25   ` kernel test robot
2021-03-31 12:25 ` [PATCH 2/4] drm/amd/display: Add FPU event trace Rodrigo Siqueira
2021-03-31 19:28   ` kernel test robot [this message]
2021-03-31 20:26   ` kernel test robot
2021-03-31 12:25 ` [PATCH 3/4] drm/amd/display: Add ref count control for FPU utilization Rodrigo Siqueira
2021-03-31 12:44   ` Christian König
2021-03-31 12:25 ` [PATCH 4/4] drm/amd/display: Add DC_FP helper to check FPU state Rodrigo Siqueira
2021-03-31 12:47   ` Christian König
2021-03-31 12:49 ` [PATCH 0/4] drm/amd/display: Base changes for isolating FPU operation in a single place Christian König

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=202104010342.0B6CU5pd-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Rodrigo.Siqueira@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=aric.cyr@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=kbuild-all@lists.01.org \
    --cc=peterz@infradead.org \
    /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