From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/mtl: Add support for 32 bit OAG formats in MTL
Date: Tue, 29 Nov 2022 17:17:13 -0800 [thread overview]
Message-ID: <877czd44x2.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20221129012146.995006-1-umesh.nerlige.ramappa@intel.com>
On Mon, 28 Nov 2022 17:21:46 -0800, Umesh Nerlige Ramappa wrote:
>
Hi Umesh,
Overall looks ok, just a couple of questions below. Splitting the patches
would be nice and easier to review, but I'm almost done with this one ;-)
> @@ -1876,7 +1875,13 @@ static int alloc_noa_wait(struct i915_perf_stream *stream)
> MI_PREDICATE_RESULT_2_ENGINE(base) :
> MI_PREDICATE_RESULT_1(RENDER_RING_BASE);
>
> - bo = i915_gem_object_create_internal(i915, 4096);
> + /*
> + * gt->scratch was being used to save/restore the GPR registers, but on
> + * MTL the scratch uses stolen lmem. An MI_SRM to this memory region
> + * causes an engine hang. Instead allocate an additional page here to
> + * save/restore GPR registers
> + */
> + bo = i915_gem_object_create_internal(i915, 8192);
Do we know how much space was used in stream->noa_wait originally? Anyway
allocating an additional page is not an issue so ok to skip the question.
> @@ -4746,6 +4772,7 @@ static void oa_init_supported_formats(struct i915_perf *perf)
> break;
>
> case INTEL_DG2:
> + case INTEL_METEORLAKE:
> oa_format_add(perf, I915_OAR_FORMAT_A32u40_A4u32_B8_C8);
> oa_format_add(perf, I915_OA_FORMAT_A24u40_A14u32_B8_C8);
Do these formats also need to be added?
oa_format_add(perf, I915_OAR_FORMAT_A32u40_A4u32_B8_C8);
oa_format_add(perf, I915_OA_FORMAT_A24u40_A14u32_B8_C8);
oa_format_add(perf, I915_OAR_FORMAT_A36u64_B8_C8);
oa_format_add(perf, I915_OA_FORMAT_A38u64_R2u64_B8_C8);
Or these are not considered OAG formats?
> break;
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2022-11-30 1:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 1:21 [Intel-gfx] [PATCH] drm/i915/mtl: Add support for 32 bit OAG formats in MTL Umesh Nerlige Ramappa
2022-11-29 2:20 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-11-29 2:45 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-11-29 7:15 ` [Intel-gfx] [PATCH] " Lucas De Marchi
2022-11-29 18:40 ` Umesh Nerlige Ramappa
2022-11-30 1:17 ` Dixit, Ashutosh [this message]
2022-11-30 1:47 ` Dixit, Ashutosh
2022-11-30 1:51 ` Dixit, Ashutosh
2022-11-30 20:00 ` Umesh Nerlige Ramappa
2022-11-30 20:14 ` Dixit, Ashutosh
2022-11-30 23:39 ` Umesh Nerlige Ramappa
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=877czd44x2.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=umesh.nerlige.ramappa@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.