On Tue, Feb 23, 2016 at 04:37:12PM +, Daniele Ceraolo Spurio wrote:
>
>
> On 18/02/16 21:10, Chris Wilson wrote:
> >On Thu, Feb 18, 2016 at 05:34:50PM +, daniele.ceraolospu...@intel.com
> >wrote:
> >>+static void ppgtt_walking(void)
> >>+{
> >>+ memset(&execbuf, 0, sizeof(execbuf));
>
On 18/02/16 21:10, Chris Wilson wrote:
On Thu, Feb 18, 2016 at 05:34:50PM +, daniele.ceraolospu...@intel.com wrote:
+static void ppgtt_walking(void)
+{
+ memset(&execbuf, 0, sizeof(execbuf));
+ execbuf.buffers_ptr = (uintptr_t)&gem_exec;
+ execbuf.buffer_count = 1;
+
On Thu, Feb 18, 2016 at 05:34:50PM +, daniele.ceraolospu...@intel.com wrote:
> +static void ppgtt_walking(void)
> +{
> + memset(&execbuf, 0, sizeof(execbuf));
> + execbuf.buffers_ptr = (uintptr_t)&gem_exec;
> + execbuf.buffer_count = 1;
> + execbuf.batch_len = 8;
> +
> + gem
From: Daniele Ceraolo Spurio
The hangcheck logic will not flag an hang if acthd keeps increasing.
However, if a malformed batch jumps to an invalid offset in the ppgtt it
can potentially continue executing through the whole address space
without triggering the hangcheck mechanism.
This patch add
