All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: shuang.he@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm: Make drm_read() more robust against multithreaded races
Date: Fri, 5 Dec 2014 21:59:37 +0100	[thread overview]
Message-ID: <20141205205937.GC20350@phenom.ffwll.local> (raw)
In-Reply-To: <71e320$en27kg@orsmga003.jf.intel.com>

On Thu, Dec 04, 2014 at 06:19:54PM -0800, shuang.he@intel.com wrote:
> Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang.he@intel.com)
> -------------------------------------Summary-------------------------------------
> Platform          Delta          drm-intel-nightly          Series Applied
> PNV                                  364/364              364/364
> ILK                                  366/366              366/366
> SNB                                  450/450              450/450
> IVB              +17                 481/498              498/498

Today there have been a lot of prts test results with +17 for ivb. Is
something wrong with the baseline results that there's always the same
regressions/improvements?

In general there's an awful lot of noise in prts results, and off-by-one
in comparing results would explain a lot ...
-Daniel

> BYT                                  289/289              289/289
> HSW                                  564/564              564/564
> BDW                                  417/417              417/417
> -------------------------------------Detailed-------------------------------------
> Platform  Test                                drm-intel-nightly          Series Applied
>  IVB  igt_kms_3d      DMESG_WARN(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_cursor_crc_cursor-128x128-onscreen      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_cursor_crc_cursor-128x128-random      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_cursor_crc_cursor-128x128-sliding      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_cursor_crc_cursor-256x256-offscreen      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_cursor_crc_cursor-256x256-onscreen      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_cursor_crc_cursor-256x256-sliding      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_cursor_crc_cursor-64x64-offscreen      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_cursor_crc_cursor-64x64-onscreen      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_cursor_crc_cursor-64x64-random      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_cursor_crc_cursor-64x64-sliding      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_cursor_crc_cursor-size-change      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_fence_pin_leak      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_mmio_vs_cs_flip_setcrtc_vs_cs_flip      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_mmio_vs_cs_flip_setplane_vs_cs_flip      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_rotation_crc_primary-rotation      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
>  IVB  igt_kms_rotation_crc_sprite-rotation      NSPT(1, M34)PASS(10, M4M34M21)      PASS(1, M34)
> Note: You need to pay more attention to line start with '*'
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2014-12-05 20:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 10:56 [PATCH 1/2] drm: Fix memory leak at error path of drm_read() Takashi Iwai
2014-12-04 10:56 ` [PATCH 2/2] drm: Implement nonblocking mode in drm_read() Takashi Iwai
2014-12-04 11:46 ` [PATCH 1/2] drm: Fix memory leak at error path of drm_read() Daniel Vetter
2014-12-04 11:50   ` Takashi Iwai
2014-12-04 11:51     ` Takashi Iwai
2014-12-04 11:51 ` Chris Wilson
2014-12-04 11:56   ` Takashi Iwai
2014-12-04 12:13     ` Chris Wilson
2014-12-04 12:27       ` Takashi Iwai
2014-12-04 12:28   ` Daniel Vetter
2014-12-04 16:31     ` Chris Wilson
2014-12-04 16:38       ` Chris Wilson
2014-12-04 16:55         ` Takashi Iwai
2014-12-04 21:03           ` [PATCH] drm: Make drm_read() more robust against multithreaded races Chris Wilson
2014-12-05  2:19             ` shuang.he
2014-12-05 20:59               ` Daniel Vetter [this message]
2014-12-05  8:42             ` Takashi Iwai
2015-01-05 10:18               ` [Intel-gfx] " Daniel Vetter
2014-12-05  8:44             ` Daniel Vetter
2014-12-04 17:25       ` [PATCH 1/2] drm: Fix memory leak at error path of drm_read() Daniel Vetter
2014-12-05  8:01         ` Chris Wilson

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=20141205205937.GC20350@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=shuang.he@intel.com \
    /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.