From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Harrison, John C" <john.c.harrison@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2 1/1] drm/i915/pxp: Add missing tag for Wa_14019159160
Date: Thu, 30 Nov 2023 00:41:18 +0000 [thread overview]
Message-ID: <6f50e997920c5ed4a08d30296c73dabeb2e7ee27.camel@intel.com> (raw)
In-Reply-To: <c38b5486ed98e04ce2369a0dc29c14ab9c7d3961.camel@intel.com>
On Wed, 2023-11-29 at 13:13 -0800, Teres Alexis, Alan Previn wrote:
> On Mon, 2023-11-27 at 15:24 -0500, Vivi, Rodrigo wrote:
> > On Wed, Nov 22, 2023 at 12:30:03PM -0800, Alan Previn wrote:
> alan:snip
> alan: thanks for reviewing and apologize for replying to this late.
>
> > > /*
> > > - * On MTL and newer platforms, protected contexts require setting
> > > - * the LRC run-alone bit or else the encryption will not happen.
> > > + * Wa_14019159160 - Case 2: mtl
> > > + * On some platforms, protected contexts require setting
> > > + * the LRC run-alone bit or else the encryption/decryption will not happen.
> > > + * NOTE: Case 2 only applies to PXP use-case of said workaround.
> > > */
> >
> > hmm, interesting enough, on the wa description I read that it is incomplete for MTL/ARL
> > and something about a fuse bit. We should probably chase for some clarification in the
> > HSD?!
> alan: yes, i went through the HSD description with the architect and we both had agreed that
> that from the KMD's perspective. At that time, the checking of the fuse from KMD's
> could be optimized out for Case-2-PXP: if the fuses was set a certain way, KMD can skip setting
> the bit in lrc because hw will enforce runalone in pxp mode irrespective of what KMD does but
> if fuse was was not set that way KMD needed to set the runalone in lrc. So for case2, its simpler
> to just turn it on always when the context is protected. However, that said, i realized the
> wording of the HSDs have changed since the original patch was implemented so i will reclarify
> offline and reply back. NOTE: i believe John Harrison is working on case-3 through a
> separate series.
alan: based on conversations with the architect, a different WA number, 14019725520,
has the details of case-2 that explains the relationship the new fuse.
However, as before it can be optimized as explained above where PXP context
need to always set this bit to ensure encryption/decryption engages.
prev parent reply other threads:[~2023-11-30 0:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 20:30 [PATCH v2 1/1] drm/i915/pxp: Add missing tag for Wa_14019159160 Alan Previn
2023-11-27 20:24 ` Rodrigo Vivi
2023-11-29 21:13 ` Teres Alexis, Alan Previn
2023-11-30 0:41 ` 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=6f50e997920c5ed4a08d30296c73dabeb2e7ee27.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).