From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com ([134.134.136.100]:15173 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752786AbeEKOOQ (ORCPT ); Fri, 11 May 2018 10:14:16 -0400 Subject: Re: [PATCH] drm/i915/oa: Disable OA on Haswell To: Chris Wilson , intel-gfx@lists.freedesktop.org Cc: Matthew Auld , Joonas Lahtinen , Rodrigo Vivi , Jani Nikula , stable@vger.kernel.org References: <20180511135602.13071-1-chris@chris-wilson.co.uk> From: Lionel Landwerlin Message-ID: Date: Fri, 11 May 2018 15:14:13 +0100 MIME-Version: 1.0 In-Reply-To: <20180511135602.13071-1-chris@chris-wilson.co.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: stable-owner@vger.kernel.org List-ID: My understanding of the virtual memory addressing from the GPU is limited... But how can the GPU poke at the kernel's allocated data? I thought we mapped into the GPU's address space only what is allocated through gem. - Lionel On 11/05/18 14:56, Chris Wilson wrote: > We observe that the OA architecture is clobbering random memory. Disable > it until this can be resolved. > > References: https://bugs.freedesktop.org/show_bug.cgi?id=106379 > Signed-off-by: Chris Wilson > Cc: Lionel Landwerlin > Cc: Matthew Auld > Cc: Joonas Lahtinen > Cc: Rodrigo Vivi > Cc: Jani Nikula > Cc: stable@vger.kernel.org > --- > drivers/gpu/drm/i915/i915_perf.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c > index 019bd2d073ad..20187f3bf350 100644 > --- a/drivers/gpu/drm/i915/i915_perf.c > +++ b/drivers/gpu/drm/i915/i915_perf.c > @@ -3425,7 +3425,7 @@ static struct ctl_table dev_root[] = { > */ > void i915_perf_init(struct drm_i915_private *dev_priv) > { > - if (IS_HASWELL(dev_priv)) { > + if (IS_HASWELL(dev_priv) && 0) { > dev_priv->perf.oa.ops.is_valid_b_counter_reg = > gen7_is_valid_b_counter_addr; > dev_priv->perf.oa.ops.is_valid_mux_reg =