From: kernel test robot <lkp@intel.com>
To: Alan Previn <alan.previn.teres.alexis@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Alan Previn <alan.previn.teres.alexis@intel.com>,
dri-devel@lists.freedesktop.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [Intel-gfx] [PATCH v2 3/3] drm/i915/gt/pxp: User PXP contexts requires runalone bit in lrc
Date: Sat, 12 Aug 2023 11:16:58 +0800 [thread overview]
Message-ID: <202308121007.jU4NvVxe-lkp@intel.com> (raw)
In-Reply-To: <20230811044310.944883-4-alan.previn.teres.alexis@intel.com>
Hi Alan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 51fec314404b6a360493f225481083b2a664e3e1]
url: https://github.com/intel-lab-lkp/linux/commits/Alan-Previn/drm-i915-pxp-mtl-Update-pxp-firmware-response-timeout/20230811-124534
base: 51fec314404b6a360493f225481083b2a664e3e1
patch link: https://lore.kernel.org/r/20230811044310.944883-4-alan.previn.teres.alexis%40intel.com
patch subject: [Intel-gfx] [PATCH v2 3/3] drm/i915/gt/pxp: User PXP contexts requires runalone bit in lrc
config: i386-randconfig-r082-20230812 (https://download.01.org/0day-ci/archive/20230812/202308121007.jU4NvVxe-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230812/202308121007.jU4NvVxe-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/202308121007.jU4NvVxe-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/i915/gt/intel_lrc.c:851:34: sparse: sparse: dereference of noderef expression
vim +851 drivers/gpu/drm/i915/gt/intel_lrc.c
847
848 static bool ctx_needs_runalone(const struct intel_context *ce)
849 {
850 if (GRAPHICS_VER_FULL(ce->engine->i915) >= IP_VER(12, 70) &&
> 851 ce->gem_context && ce->gem_context->uses_protected_content &&
852 (ce->engine->class == COMPUTE_CLASS || ce->engine->class == RENDER_CLASS))
853 return true;
854
855 return false;
856 }
857
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-08-12 3:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 4:43 [Intel-gfx] [PATCH v2 0/3] drm/i915/pxp/mtl: Update gsc-heci cmd submission Alan Previn
2023-08-11 4:43 ` [Intel-gfx] [PATCH v2 1/3] drm/i915/pxp/mtl: Update pxp-firmware response timeout Alan Previn
2023-08-11 4:43 ` [Intel-gfx] [PATCH v2 2/3] drm/i915/pxp/mtl: Update pxp-firmware packet size Alan Previn
2023-08-11 4:43 ` [Intel-gfx] [PATCH v2 3/3] drm/i915/gt/pxp: User PXP contexts requires runalone bit in lrc Alan Previn
2023-08-12 3:16 ` kernel test robot [this message]
2023-08-11 5:15 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/pxp/mtl: Update gsc-heci cmd submission Patchwork
2023-08-11 5:15 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-11 5:33 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-08-11 18:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/pxp/mtl: Update gsc-heci cmd submission (rev2) Patchwork
2023-08-11 18:12 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-11 18:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-13 1:21 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=202308121007.jU4NvVxe-lkp@intel.com \
--to=lkp@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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