From: Fernando Pacheco <fernando.pacheco@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/4] Perma-pin uC firmware and re-enable global reset
Date: Tue, 9 Apr 2019 14:30:58 -0700 [thread overview]
Message-ID: <20190409213102.30124-1-fernando.pacheco@intel.com> (raw)
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/
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Fernando Pacheco (4):
drm/i915/uc: Rename uC firmware init function
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"
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 | 9 ++-
drivers/gpu/drm/i915/intel_guc.h | 11 ++++
drivers/gpu/drm/i915/intel_guc_fw.c | 45 +++++++++++---
drivers/gpu/drm/i915/intel_guc_fw.h | 3 +
drivers/gpu/drm/i915/intel_huc.c | 72 +++++++++++++++++-----
drivers/gpu/drm/i915/intel_huc.h | 4 ++
drivers/gpu/drm/i915/intel_huc_fw.c | 82 ++++++++++++++++++++----
drivers/gpu/drm/i915/intel_huc_fw.h | 3 +
drivers/gpu/drm/i915/intel_uc.c | 39 ++++++++++--
drivers/gpu/drm/i915/intel_uc.h | 1 +
drivers/gpu/drm/i915/intel_uc_fw.c | 96 ++++++++++++++++++++---------
drivers/gpu/drm/i915/intel_uc_fw.h | 15 ++++-
16 files changed, 329 insertions(+), 82 deletions(-)
--
2.21.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-04-09 21:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 21:30 Fernando Pacheco [this message]
2019-04-09 21:30 ` [PATCH 1/4] drm/i915/uc: Rename uC firmware init function Fernando Pacheco
2019-04-09 22:08 ` Chris Wilson
2019-04-09 21:31 ` [PATCH 2/4] drm/i915/uc: Reserve upper range of GGTT Fernando Pacheco
2019-04-09 21:41 ` Chris Wilson
2019-04-09 21:43 ` Chris Wilson
2019-04-09 22:40 ` Fernando Pacheco
2019-04-15 22:32 ` Fernando Pacheco
2019-04-16 7:21 ` Chris Wilson
2019-04-09 22:12 ` Daniele Ceraolo Spurio
2019-04-09 21:31 ` [PATCH 3/4] drm/i915/uc: Place uC firmware in " Fernando Pacheco
2019-04-09 21:53 ` Chris Wilson
2019-04-09 22:53 ` Fernando Pacheco
2019-04-09 23:04 ` Chris Wilson
2019-04-09 22:11 ` Chris Wilson
2019-04-09 23:18 ` Fernando Pacheco
2019-04-09 22:22 ` Chris Wilson
2019-04-16 14:51 ` Fernando Pacheco
2019-04-16 15:04 ` Chris Wilson
2019-04-16 15:21 ` Fernando Pacheco
2019-04-09 21:31 ` [PATCH 4/4] Revert "drm/i915/guc: Disable global reset" Fernando Pacheco
2019-04-09 21:54 ` Chris Wilson
2019-04-16 14:45 ` Fernando Pacheco
2019-04-16 15:05 ` Chris Wilson
2019-04-16 15:10 ` Fernando Pacheco
2019-04-09 22:31 ` ✗ Fi.CI.SPARSE: warning for Perma-pin uC firmware and re-enable global reset Patchwork
2019-04-09 22:56 ` ✗ Fi.CI.BAT: failure " 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=20190409213102.30124-1-fernando.pacheco@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.