From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>,
"Harrison, John C" <john.c.harrison@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2 1/5] drm/i915/gsc: fixes and updates for GSC memory allocation
Date: Wed, 7 Jun 2023 19:22:32 +0000 [thread overview]
Message-ID: <1458ff61de558ce09b2c1c53da0f84d224b2a89c.camel@intel.com> (raw)
In-Reply-To: <20230606022402.2048235-2-daniele.ceraolospurio@intel.com>
On Mon, 2023-06-05 at 19:23 -0700, Ceraolo Spurio, Daniele wrote:
> A few fixes/updates are required around the GSC memory allocation and it
> is easier to do them all at the same time. The changes are as follows:
>
> 1 - Switch the memory allocation to stolen memory. We need to avoid
> accesses from GSC FW to normal memory after the suspend function has
> completed and to do so we can either switch to using stolen or make sure
> the GSC is gone to sleep before the end of the suspend function. Given
> that the GSC waits for a bit before going idle even if there are no
> pending operations, it is easier and quicker to just use stolen memory.
>
> 2 - Reduce the GSC allocation size to 4MBs, which is the POR requirement.
> The 8MBs were needed only for early FW and I had misunderstood that as
> being the expected POR size when I sent the original patch.
>
> 3 - Perma-map the GSC allocation. This isn't required immediately, but it
> will be needed later to be able to quickly extract the GSC logs, which are
> inside the allocation. Since the mapping code needs to be rewritten due to
> switching to stolen, it makes sense to do the switch immediately to avoid
> having to change it again later.
>
> Note that the explicit setting of CACHE_NONE for Wa_22016122933 has been
> dropped because that's the default setting for stolen memory on !LLC
> platforms.
>
> v2: only memset the memory we're not overwriting (Alan)
>
LGTM so ..
Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>
next prev parent reply other threads:[~2023-06-07 19:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 2:23 [PATCH v2 0/5] drm/i915: GSC FW support for MTL Daniele Ceraolo Spurio
2023-06-06 2:23 ` [PATCH v2 1/5] drm/i915/gsc: fixes and updates for GSC memory allocation Daniele Ceraolo Spurio
2023-06-07 19:22 ` Teres Alexis, Alan Previn [this message]
2023-06-06 2:23 ` [PATCH v2 2/5] drm/i915/mtl/gsc: extract release and security versions from the gsc binary Daniele Ceraolo Spurio
2023-06-08 21:51 ` Teres Alexis, Alan Previn
2023-06-06 2:24 ` [PATCH v2 3/5] drm/i915/mtl/gsc: query the GSC FW for its compatibility version Daniele Ceraolo Spurio
2023-06-08 23:36 ` Teres Alexis, Alan Previn
2023-06-06 2:24 ` [PATCH v2 4/5] drm/i915/mtl/gsc: Add a gsc_info debugfs Daniele Ceraolo Spurio
2023-06-06 4:32 ` [PATCH v3] " Daniele Ceraolo Spurio
2023-06-07 21:23 ` Teres Alexis, Alan Previn
2023-06-06 6:49 ` [Intel-gfx] [PATCH v2 4/5] " kernel test robot
2023-06-06 7:21 ` kernel test robot
2023-06-06 8:04 ` kernel test robot
2023-06-06 8:26 ` kernel test robot
2023-06-06 2:24 ` [PATCH v2 5/5] drm/i915/gsc: define gsc fw Daniele Ceraolo Spurio
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=1458ff61de558ce09b2c1c53da0f84d224b2a89c.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 \
--cc=john.c.harrison@intel.com \
--cc=vinay.belgaumkar@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).