Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH v6 1/1] drm/i915/pxp: Promote pxp subsystem to top-level of i915
Date: Thu, 1 Dec 2022 23:55:53 +0000	[thread overview]
Message-ID: <897d34b8c97fe4f4ffa65d08f88a9582f0ccb822.camel@intel.com> (raw)
In-Reply-To: <20221130020245.3909555-1-alan.previn.teres.alexis@intel.com>



On Tue, 2022-11-29 at 18:02 -0800, Teres Alexis, Alan Previn wrote:
Alan: [snip]
> +	newpxp->ctrl_gt = pxp_get_ctrl_gt(newpxp->i915);
> +
> +	if (!newpxp->ctrl_gt)
> +		return -ENODEV;
>  
>  	/*
>  	 * If HuC is loaded by GSC but PXP is disabled, we can skip the init of
>  	 * the full PXP session/object management and just init the tee channel.
>  	 */
> -	if (HAS_PXP(gt->i915))
> -		pxp_init_full(pxp);
> -	else if (intel_huc_is_loaded_by_gsc(&gt->uc.huc) && intel_uc_uses_huc(&gt->uc))
> -		intel_pxp_tee_component_init(pxp);
> +	if (HAS_PXP(newpxp->i915))
> +		pxp_init_full(newpxp);

I realize with rev6 now having pxp as top-level and defining ctrl_gt properly in the header, its actually the correct
time to switch HAS_PXP(i915) to HAS_PXP(pxp) so we can check the VDBOX mask on the ctrl_gt (instead of root gt as it is
now). This assures HAS_PXP continues to be a global-macro as was it was originally intended.

...alan

  parent reply	other threads:[~2022-12-01 23:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30  2:02 [Intel-gfx] [PATCH v6 1/1] drm/i915/pxp: Promote pxp subsystem to top-level of i915 Alan Previn
2022-11-30  2:28 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for series starting with [v6,1/1] " Patchwork
2022-11-30  2:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-30 11:20 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-12-01 19:25   ` Teres Alexis, Alan Previn
2022-11-30 17:32 ` [Intel-gfx] [PATCH v6 1/1] " Matt Roper
2022-11-30 17:42   ` Vivi, Rodrigo
2022-12-01 19:20     ` Teres Alexis, Alan Previn
2022-12-01 23:55 ` Teres Alexis, Alan Previn [this message]
2022-12-02  0:11   ` Teres Alexis, Alan Previn

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=897d34b8c97fe4f4ffa65d08f88a9582f0ccb822.camel@intel.com \
    --to=alan.previn.teres.alexis@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --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