From: kernel test robot <lkp@intel.com>
To: John.C.Harrison@intel.com, Intel-GFX@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev, intel-gfx@lists.freedesktop.org,
Chris Wilson <chris@chris-wilson.co.uk>,
DRI-Devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v2 2/2] drm/i915: Don't use BAR mappings for ring buffers with LLC
Date: Thu, 16 Feb 2023 10:54:36 +0800 [thread overview]
Message-ID: <202302161021.TjavhrpH-lkp@intel.com> (raw)
In-Reply-To: <20230216002248.1851966-3-John.C.Harrison@Intel.com>
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-tip/drm-tip]
url: https://github.com/intel-lab-lkp/linux/commits/John-C-Harrison-Intel-com/drm-i915-Don-t-use-stolen-memory-for-ring-buffers-with-LLC/20230216-082552
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link: https://lore.kernel.org/r/20230216002248.1851966-3-John.C.Harrison%40Intel.com
patch subject: [Intel-gfx] [PATCH v2 2/2] drm/i915: Don't use BAR mappings for ring buffers with LLC
config: i386-randconfig-a011-20230213 (https://download.01.org/0day-ci/archive/20230216/202302161021.TjavhrpH-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/fa748ad303922e4138a246d4db247dfa96e45651
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review John-C-Harrison-Intel-com/drm-i915-Don-t-use-stolen-memory-for-ring-buffers-with-LLC/20230216-082552
git checkout fa748ad303922e4138a246d4db247dfa96e45651
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 olddefconfig
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202302161021.TjavhrpH-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/i915/gt/intel_ring.c: In function 'intel_ring_unpin':
>> drivers/gpu/drm/i915/gt/intel_ring.c:103:9: error: expected '}' before 'else'
103 | else
| ^~~~
vim +103 drivers/gpu/drm/i915/gt/intel_ring.c
2871ea85c119e6f Chris Wilson 2019-10-24 92
2871ea85c119e6f Chris Wilson 2019-10-24 93 void intel_ring_unpin(struct intel_ring *ring)
2871ea85c119e6f Chris Wilson 2019-10-24 94 {
2871ea85c119e6f Chris Wilson 2019-10-24 95 struct i915_vma *vma = ring->vma;
2871ea85c119e6f Chris Wilson 2019-10-24 96
2871ea85c119e6f Chris Wilson 2019-10-24 97 if (!atomic_dec_and_test(&ring->pin_count))
2871ea85c119e6f Chris Wilson 2019-10-24 98 return;
2871ea85c119e6f Chris Wilson 2019-10-24 99
2871ea85c119e6f Chris Wilson 2019-10-24 100 i915_vma_unset_ggtt_write(vma);
fa748ad303922e4 Daniele Ceraolo Spurio 2023-02-15 101 if (i915_vma_is_map_and_fenceable(vma) && !HAS_LLC(vma->vm->i915)) {
2871ea85c119e6f Chris Wilson 2019-10-24 102 i915_vma_unpin_iomap(vma);
2871ea85c119e6f Chris Wilson 2019-10-24 @103 else
2871ea85c119e6f Chris Wilson 2019-10-24 104 i915_gem_object_unpin_map(vma->obj);
2871ea85c119e6f Chris Wilson 2019-10-24 105
2871ea85c119e6f Chris Wilson 2019-10-24 106 i915_vma_make_purgeable(vma);
a266bf420060043 Chris Wilson 2019-11-18 107 i915_vma_unpin(vma);
2871ea85c119e6f Chris Wilson 2019-10-24 108 }
2871ea85c119e6f Chris Wilson 2019-10-24 109
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-02-16 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230216002248.1851966-1-John.C.Harrison@Intel.com>
2023-02-16 0:22 ` [PATCH v2 1/2] drm/i915: Don't use stolen memory for ring buffers with LLC John.C.Harrison
2023-02-16 0:22 ` [PATCH v2 2/2] drm/i915: Don't use BAR mappings " John.C.Harrison
2023-02-16 2:54 ` kernel test robot [this message]
2023-02-16 8:47 ` [Intel-gfx] " kernel test robot
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=202302161021.TjavhrpH-lkp@intel.com \
--to=lkp@intel.com \
--cc=DRI-Devel@lists.freedesktop.org \
--cc=Intel-GFX@lists.freedesktop.org \
--cc=John.C.Harrison@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.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