From: Fernando Pacheco <fernando.pacheco@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 0/5] Perma-pin uC firmware and re-enable global reset
Date: Thu, 18 Apr 2019 16:43:24 -0700 [thread overview]
Message-ID: <ec98a9ec-88d8-6f8b-d80a-df053f4e0cd7@intel.com> (raw)
In-Reply-To: <20190418233151.17510-1-fernando.pacheco@intel.com>
On 4/18/19 4:31 PM, Fernando Pacheco wrote:
> The intent is to move the GuC and HuC firmware images to the
> top of the address space. This portion is inaccessible during
> normal GuC operations and should be relatively safe to house
> both firmware images. By making the move we can re-enable the
> full gpu reset with GuC enabled.
>
> Placing the firmware images above GUC_GGTT_TOP was discussed
> previously here:
> https://patchwork.freedesktop.org/patch/273616/
>
> v2:
> The decision to rename both the uc_fw init and fini functions
> made it easier to pull the bind/unbind operations out of
> intel_guc_fw.* and intel_huc_fw.*. The bind/unbind will now
> take place within the newly repurposed intel_uc_fw_init/fini.
> All other changes should be called out in their respective patches
> and should be the direct result of a review comment.
Chris, I didn't address two of your earlier review comments, so I'll try
to do so here:
1. You are correct about the inline function in the first patch, but I felt that
could be fixed separate from this series.
2. Your comment on not needing to pin the fw pages made sense to me, but I found that the
explicit pin/unpin was necessary for the binding. Please let me know if I'm missing
something here!
Thanks,
Fernando
>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>
> Fernando Pacheco (5):
> drm/i915/uc: Rename uC firmware init/fini functions
> drm/i915/uc: Reserve upper range of GGTT
> drm/i915/uc: Place uC firmware in upper range of GGTT
> Revert "drm/i915/guc: Disable global reset"
> drm/i915/selftests: Check that gpu reset is usable from atomic context
>
> drivers/gpu/drm/i915/i915_gem.c | 2 +
> drivers/gpu/drm/i915/i915_gem_gtt.c | 25 ++--
> drivers/gpu/drm/i915/i915_gem_gtt.h | 1 +
> drivers/gpu/drm/i915/i915_reset.c | 3 -
> drivers/gpu/drm/i915/intel_guc.c | 58 ++++++++-
> drivers/gpu/drm/i915/intel_guc.h | 2 +
> drivers/gpu/drm/i915/intel_guc_fw.c | 20 +--
> drivers/gpu/drm/i915/intel_huc.c | 74 ++++++++---
> drivers/gpu/drm/i915/intel_huc.h | 6 +-
> drivers/gpu/drm/i915/intel_huc_fw.c | 49 +++++--
> drivers/gpu/drm/i915/intel_uc.c | 39 +++++-
> drivers/gpu/drm/i915/intel_uc.h | 1 +
> drivers/gpu/drm/i915/intel_uc_fw.c | 122 +++++++++++++-----
> drivers/gpu/drm/i915/intel_uc_fw.h | 12 +-
> .../gpu/drm/i915/selftests/intel_hangcheck.c | 6 +-
> 15 files changed, 319 insertions(+), 101 deletions(-)
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-18 23:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 23:31 [PATCH v2 0/5] Perma-pin uC firmware and re-enable global reset Fernando Pacheco
2019-04-18 23:31 ` [PATCH v2 1/5] drm/i915/uc: Rename uC firmware init/fini functions Fernando Pacheco
2019-04-18 23:31 ` [PATCH v2 2/5] drm/i915/uc: Reserve upper range of GGTT Fernando Pacheco
2019-04-19 7:14 ` Chris Wilson
2019-04-19 17:14 ` Fernando Pacheco
2019-04-19 17:22 ` Chris Wilson
2019-04-18 23:31 ` [PATCH v2 3/5] drm/i915/uc: Place uC firmware in " Fernando Pacheco
2019-04-19 7:15 ` Chris Wilson
2019-04-18 23:31 ` [PATCH v2 4/5] Revert "drm/i915/guc: Disable global reset" Fernando Pacheco
2019-04-18 23:31 ` [PATCH v2 5/5] drm/i915/selftests: Check that gpu reset is usable from atomic context Fernando Pacheco
2019-04-18 23:43 ` Fernando Pacheco [this message]
2019-04-18 23:45 ` ✗ Fi.CI.SPARSE: warning for Perma-pin uC firmware and re-enable global reset (rev2) Patchwork
2019-04-19 0:04 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-19 2:55 ` ✓ Fi.CI.IGT: " Patchwork
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=ec98a9ec-88d8-6f8b-d80a-df053f4e0cd7@intel.com \
--to=fernando.pacheco@intel.com \
--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