From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Cc: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v5 3/3] drm/i915/lrc: User PXP contexts requires runalone bit in lrc
Date: Fri, 15 Sep 2023 18:04:44 +0000 [thread overview]
Message-ID: <0c57ebe16cb77949cf4ec3d1b5640e5b478fe322.camel@intel.com> (raw)
In-Reply-To: <20230909223848.427849-4-alan.previn.teres.alexis@intel.com>
On Sat, 2023-09-09 at 15:38 -0700, Teres Alexis, Alan Previn wrote:
> On Meteorlake onwards, HW specs require that all user contexts that
> run on render or compute engines and require PXP must enforce
> run-alone bit in lrc. Add this enforcement for protected contexts.
alan:snip
>
> Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com>
> @@ -860,6 +881,8 @@ static void init_common_regs(u32 * const regs,
> if (GRAPHICS_VER(engine->i915) < 11)
> ctl |= _MASKED_BIT_DISABLE(CTX_CTRL_ENGINE_CTX_SAVE_INHIBIT |
> CTX_CTRL_RS_CTX_ENABLE);
> + if (ctx_needs_runalone(ce))
> + ctl |= _MASKED_BIT_ENABLE(BIT(7));
> regs[CTX_CONTEXT_CONTROL] = ctl;
>
> regs[CTX_TIMESTAMP] = ce->stats.runtime.last;
alan: to align intel-gfx ml, Vivaik reviewed this on dri-devel at https://lists.freedesktop.org/archives/dri-devel/2023-September/422875.html - snippet:
thus, will rerev this (with the others fixes in this series).
>> Can we please get the bit defined in intel_engine_regs.h with a define
>> instead of a number identification?
>>
>> Review completed conditional to the above fix.
>>
>> Reviewed-by: Balasubrawmanian, Vivaik
>> <vivaik.balasubrawmanian at intel.com>
>> <mailto:vivaik.balasubrawmanian at intel.com>
prev parent reply other threads:[~2023-09-15 18:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 22:38 [PATCH v5 0/3] drm/i915/pxp/mtl: Update gsc-heci cmd submission to align with fw/hw spec Alan Previn
2023-09-09 22:38 ` [PATCH v5 1/3] drm/i915/pxp/mtl: Update pxp-firmware response timeout Alan Previn
2023-09-14 22:25 ` Balasubrawmanian, Vivaik
2023-09-15 17:30 ` Teres Alexis, Alan Previn
2023-09-15 17:58 ` Teres Alexis, Alan Previn
2023-09-09 22:38 ` [PATCH v5 2/3] drm/i915/pxp/mtl: Update pxp-firmware packet size Alan Previn
2023-09-15 17:28 ` Teres Alexis, Alan Previn
2023-09-15 18:02 ` Teres Alexis, Alan Previn
2023-09-09 22:38 ` [PATCH v5 3/3] drm/i915/lrc: User PXP contexts requires runalone bit in lrc Alan Previn
2023-09-14 22:51 ` Balasubrawmanian, Vivaik
2023-09-15 18:04 ` Teres Alexis, Alan Previn [this message]
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=0c57ebe16cb77949cf4ec3d1b5640e5b478fe322.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox