; Sent: Tuesday, December 5, 2017 12:39 PM
> To: Rogovin, Kevin <kevin.rogo...@intel.com>; intel-gfx@lists.freedes
> ktop.org
> Subject: RE: [Intel-gfx] [PATCH 3/3] i965: check scratch page in a
> locked fashion on each ioctl
>
> Quoting Rogovin, Kevin (2017-12-05 10:30:04)
<kevin.rogo...@intel.com>; intel-gfx@lists.freedesktop.org
Subject: RE: [Intel-gfx] [PATCH 3/3] i965: check scratch page in a locked
fashion on each ioctl
Quoting Rogovin, Kevin (2017-12-05 10:30:04)
> Hi,
>
> > Per context, then you can remove the locking. It's fitting sinc
Quoting Rogovin, Kevin (2017-12-05 10:30:04)
> Hi,
>
> > Per context, then you can remove the locking. It's fitting since the
> > scratch page is per-context anyway.
>
> The scratch page is per context? This I did not know, I thought it was per
> PPGTT. If that is the case, then my proposed
Hi,
> Per context, then you can remove the locking. It's fitting since the scratch
> page is per-context anyway.
The scratch page is per context? This I did not know, I thought it was per
PPGTT. If that is the case, then my proposed interface to get/set the scratch
page contents is wrong
Quoting kevin.rogo...@intel.com (2017-12-05 07:48:14)
> From: Kevin Rogovin
>
> ---
> src/mesa/drivers/dri/i965/intel_batchbuffer.c | 27
> ++-
> 1 file changed, 26 insertions(+), 1 deletion(-)
>
> diff --git
From: Kevin Rogovin
---
src/mesa/drivers/dri/i965/intel_batchbuffer.c | 27 ++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git a/src/mesa/drivers/dri/i965/intel_batchbuffer.c
b/src/mesa/drivers/dri/i965/intel_batchbuffer.c
index