All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: "Zeng, Oak" <oak.zeng@intel.com>,
	"Das, Nirmoy" <nirmoy.das@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "Hajda, Andrzej" <andrzej.hajda@intel.com>
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/gt: Do not use stolen on MTL
Date: Tue, 4 Jul 2023 17:31:06 +0200	[thread overview]
Message-ID: <c87c16c3-ef15-e2b0-452b-d14c099f3770@linux.intel.com> (raw)
In-Reply-To: <SA1PR11MB699124CCEFAA2F67C424EA27922EA@SA1PR11MB6991.namprd11.prod.outlook.com>

Hi Oak,

On 7/4/2023 5:01 PM, Zeng, Oak wrote:
> Hi Nirmoy,
>
> The changes in this series make sense to me. I searched my code base, there are a few other places where stolen memory is allocated:
Thanks for checking all the places.
>
> 1) intel_dpt_create: I don't know what is dpt. Should we also consider this one? Maybe we never read from cpu?
This expects i915_ggtt_has_aperture() which MTL doesn't have.
> 2) create_ring_vma: I think cpu only write ring buffer but never read it. So should be okay.
Same as above.
> 3) vlv_rc6_init
This  seems to be only for IS_VALLEYVIEW().
> 4) there are a few places calling i915_gem_object_create_stolen_for_preallocated. I think this is also stolen memory?

Where is this from, do you mean I915_BO_PREALLOC ?


>
> For integrated gpu like MTL, do we use stolen memory for ggtt? If yes, does CPU only write ggtt/never read?

GTT pages only seems to be written.


Thanks,

Nirmoy

>
> Thanks,
> Oak
>
>> -----Original Message-----
>> From: Das, Nirmoy <nirmoy.das@intel.com>
>> Sent: June 30, 2023 1:02 PM
>> To: intel-gfx@lists.freedesktop.org
>> Cc: Das, Nirmoy <nirmoy.das@intel.com>; Zeng, Oak <oak.zeng@intel.com>; Jani
>> Nikula <jani.nikula@linux.intel.com>; Joonas Lahtinen
>> <joonas.lahtinen@linux.intel.com>; Andi Shyti <andi.shyti@linux.intel.com>;
>> Hajda, Andrzej <andrzej.hajda@intel.com>
>> Subject: [PATCH 1/2] drm/i915/gt: Do not use stolen on MTL
>>
>> Use smem on MTL due to a HW bug in MTL that prevents
>> reading from stolen memory using LMEM BAR.
>>
>> Cc: Oak Zeng <oak.zeng@intel.com>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>> Cc: Andi Shyti <andi.shyti@linux.intel.com>
>> Cc: Andrzej Hajda <andrzej.hajda@intel.com>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>> ---
>>   drivers/gpu/drm/i915/gt/intel_gt.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/intel_gt.c
>> b/drivers/gpu/drm/i915/gt/intel_gt.c
>> index 33a61046ba58..9f64d61dd5fc 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_gt.c
>> +++ b/drivers/gpu/drm/i915/gt/intel_gt.c
>> @@ -466,7 +466,7 @@ static int intel_gt_init_scratch(struct intel_gt *gt, unsigned
>> int size)
>>   	obj = i915_gem_object_create_lmem(i915, size,
>>   					  I915_BO_ALLOC_VOLATILE |
>>   					  I915_BO_ALLOC_GPU_ONLY);
>> -	if (IS_ERR(obj))
>> +	if (IS_ERR(obj) && !IS_METEORLAKE(i915)) /* Wa_22018444074 */
>>   		obj = i915_gem_object_create_stolen(i915, size);
>>   	if (IS_ERR(obj))
>>   		obj = i915_gem_object_create_internal(i915, size);
>> --
>> 2.39.0

  reply	other threads:[~2023-07-04 15:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 17:01 [Intel-gfx] [PATCH 1/2] drm/i915/gt: Do not use stolen on MTL Nirmoy Das
2023-06-30 17:01 ` [Intel-gfx] [PATCH 2/2] drm/i915/display: " Nirmoy Das
2023-07-05 10:02   ` Andrzej Hajda
2023-07-11 13:44     ` Nirmoy Das
2023-07-06 13:32   ` Tvrtko Ursulin
2023-07-06 13:35     ` Nirmoy Das
2023-07-06 13:43       ` Tvrtko Ursulin
2023-07-10  9:00         ` Nirmoy Das
2023-07-11 15:59           ` Tvrtko Ursulin
2023-07-12 12:43             ` Nirmoy Das
2023-07-11 14:50   ` Andi Shyti
2023-06-30 17:31 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/2] drm/i915/gt: " Patchwork
2023-06-30 17:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-07-01  6:45 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-07-04 15:01 ` [Intel-gfx] [PATCH 1/2] " Zeng, Oak
2023-07-04 15:31   ` Nirmoy Das [this message]
2023-07-04 15:41     ` Zeng, Oak
2023-07-11 14:50   ` Andi Shyti
2023-07-05  9:51 ` Andrzej Hajda
2023-07-11 14:48 ` Andi Shyti
  -- strict thread matches above, loose matches on Subject: below --
2023-07-11 22:06 Nirmoy Das
2023-07-13 15:01 Nirmoy Das

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=c87c16c3-ef15-e2b0-452b-d14c099f3770@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=andrzej.hajda@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nirmoy.das@intel.com \
    --cc=oak.zeng@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.