1. Feb 02, 2018
    • Arnd Bergmann's avatar
      drm/nouveau: nouveau: use correct string length · ee0d5810
      Arnd Bergmann authored
      
      
      gcc-8 reports
      
      drivers/gpu/drm/nouveau/nvkm/engine/pm/base.c: In function 'nvkm_perfmon_mthd':
      include/linux/string.h:265:9: error: '__builtin_strncpy' specified bound 64 equals destination size [-Werror=stringop-truncation]
      
      We need one less byte or call strlcpy() to make it a
      nul-terminated string.
      
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarBen Skeggs <bskeggs@redhat.com>
      ee0d5810
    • Christoph Böhmwalder's avatar
      drm/nouveau/drm/nouveau/mmu: fix odd_ptr_err.cocci warnings · 94ee54dc
      Christoph Böhmwalder authored
      The kbuild test bot complained about a new coccinelle warning nearby,
      which sparked a discussion about the assignment to 'memory' inside of
      the conditional expression.  See Link below for the original post.
      
      Fix the assignment to silence the coccinelle warning and also make the
      code look a little nicer.
      
      Link: https://lists.freedesktop.org/archives/nouveau/2017-November/029242.html
      
      
      Signed-off-by: default avatarChristoph Böhmwalder <christoph@boehmwalder.at>
      Signed-off-by: default avatarBen Skeggs <bskeggs@redhat.com>
      Reviewed-by: default avatarKarol Herbst <kherbst@redhat.com>
      94ee54dc
    • Karol Herbst's avatar
      drm/nouveau/pmu/fuc: don't use movw directly anymore · fe9748b7
      Karol Herbst authored
      
      
      Fixes failure to compile with recent envyas as a result of the 'movw'
      alias being removed for v5.
      
      A bit of history:
      
      v3 only has a 16-bit sign-extended immediate mov op. In order to set
      the high bits, there's a separate 'sethi' op. envyas validates that
      the value passed to mov(imm) is between -0x8000 and 0x7fff. In order
      to simplify macros that load both the low and high word, a 'movw'
      alias was added which takes an unsigned 16-bit immediate. However the
      actual hardware op still sign extends.
      
      v5 has a full 32-bit immediate mov op. The v3 16-bit immediate mov op
      is gone (loads 0 into the dst reg). However due to a bug in envyas,
      the movw alias still existed, and selected the no-longer-present v3
      16-bit immediate mov op. As a result usage of movw on v5 is the same
      as mov with a 0x0 argument.
      
      The proper fix throughout is to only ever use the 'movw' alias in
      combination with 'sethi'. Anything else should get the sign-extended
      validation to ensure that the intended value ends up in the
      destination register.
      
      Changes in fuc3 binaries is the result of a different encoding being
      selected for a mov with an 8-bit value.
      
      v2: added commit message written by Ilia, thanks for that!
      v3: messed up rebasing, now it should apply
      
      Signed-off-by: default avatarKarol Herbst <kherbst@redhat.com>
      Signed-off-by: default avatarBen Skeggs <bskeggs@redhat.com>
      fe9748b7
  2. Feb 01, 2018
  3. Jan 31, 2018
  4. Jan 25, 2018
  5. Jan 23, 2018
  6. Jan 20, 2018
  7. Jan 19, 2018
  8. Jan 18, 2018
  9. Jan 17, 2018
  10. Jan 15, 2018
  11. Jan 14, 2018