Re: [Intel-gfx] [PATCH i-g-t] intel_l3_parity: More helpful output in case of errors

On 09/05/2017 07:16 PM, Daniel Vetter wrote: On Tue, Sep 05, 2017 at 03:39:49PM +0300, Petri Latvala wrote: When no action is specified on the command line, print the usage help text and exit with failure instead of SIGABRT. Fix some typos on the usage text. Keep the abort() call in places

Re: [Intel-gfx] [PATCH 1/4] drm/: Support registering driver-specific ioctls dynamically

/RFC-drm-Allow-driver-specific-ioctls-to-be-registered/20170906-130119 base: git://anongit.freedesktop.org/drm-intel for-linux-next reproduce: make htmldocs All warnings (new ones prefixed by >>): WARNING: convert(1) not found, for SVG to PDF conversion install ImageMagick

Re: [Intel-gfx] Supporting Intel GPU tracing in gpuvis

Quoting Daniel Vetter (2017-09-06 08:46:50) > Hi Pierre, > > On Tue, Sep 5, 2017 at 11:15 PM, Pierre-Loup A. Griffais > wrote: > > Hi Daniel, > > > > In the past couple of months we've been working on gpuvis, a GPU tracing > > tool similar to GPUView on Windows. It's

Re: [Intel-gfx] [PATCH i-g-t] build: Define _GNU_SOURCE in Makefile.am

On Tue, Sep 5, 2017 at 11:08 PM, Chris Wilson wrote: > Quoting Daniel Vetter (2017-09-05 17:19:45) >> In meson I want to just set this everywhere (no reason not to), and >> doing so will allow us to clean up a few things. > > If we are keeping config.h in meson, why move

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Move device_info.has_snoop into the static tables

Quoting Ville Syrjälä (2017-09-05 18:28:50) > On Tue, Sep 05, 2017 at 02:47:34PM +0100, Chris Wilson wrote: > > Currently we define any !llc machine as using snoop instead. However, > > some platforms run into trouble using snoop that we would like to > > disable, and to do so easily we want to be

[Intel-gfx] ✓ Fi.CI.BAT: success for RFC: meson build system support (rev6)

== Series Details == Series: RFC: meson build system support (rev6) URL : https://patchwork.freedesktop.org/series/29823/ State : success == Summary == IGT patchset tested on top of latest successful build 918863f8e3e8f49235fd2e4a36e11f386c06c11c intel_display_poller: Fix truncation of a

[Intel-gfx] [PATCH i-g-t] tests/igt_command_line.sh: Allow testing individual tests

meso will use this to run the tests for all testcases in parallel, for great speedup! v2: Fix bugs in the conversion. Oops, I broke the automake build. v3: Try harder at being posix shell compliant. Signed-off-by: Daniel Vetter --- tests/igt_command_line.sh | 42

[Intel-gfx] ✗ Fi.CI.BAT: failure for RFC: meson build system support (rev5)

== Series Details == Series: RFC: meson build system support (rev5) URL : https://patchwork.freedesktop.org/series/29823/ State : failure == Summary == IGT patchset build failed on latest successful build 918863f8e3e8f49235fd2e4a36e11f386c06c11c intel_display_poller: Fix truncation of a test

[Intel-gfx] ✗ Fi.CI.BAT: failure for RFC: meson build system support (rev5)

== Series Details == Series: RFC: meson build system support (rev5) URL : https://patchwork.freedesktop.org/series/29823/ State : failure == Summary == IGT patchset build failed on latest successful build 918863f8e3e8f49235fd2e4a36e11f386c06c11c intel_display_poller: Fix truncation of a test

Re: [Intel-gfx] Supporting Intel GPU tracing in gpuvis

Hi Pierre, On Tue, Sep 5, 2017 at 11:15 PM, Pierre-Loup A. Griffais wrote: > Hi Daniel, > > In the past couple of months we've been working on gpuvis, a GPU tracing > tool similar to GPUView on Windows. It's lower level than other API-based > tracing tools and lets

[Intel-gfx] ✗ Fi.CI.BAT: warning for series starting with [1/2] drm/i915: Move device_info.has_snoop into the static tables

== Series Details == Series: series starting with [1/2] drm/i915: Move device_info.has_snoop into the static tables URL : https://patchwork.freedesktop.org/series/29829/ State : warning == Summary == Series 29829v1 series starting with [1/2] drm/i915: Move device_info.has_snoop into the

<    1   2