All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/5] Simplify GuC communication handling
Date: Tue, 10 Dec 2019 13:09:14 -0800	[thread overview]
Message-ID: <20191210210919.30846-1-daniele.ceraolospurio@intel.com> (raw)

Since H2G communication will be in the hot path of GuC submission,
the main aim of this series is to get rid of the function pointers to
speed things up and avoid retpolines (in case the compiler decides
they're required). While at it, simplify the general communication
enabling/disabling by removing support for multiple channels since
it is extremely unlikely that we'll ever use more than one.

Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: John Harrison <John.C.Harrison@Intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>

Daniele Ceraolo Spurio (5):
  drm/i915/guc: Merge communication_stop and communication_disable
  drm/i915/guc/ct: stop expecting multiple CT channels
  drm/i915/guc: remove function pointers for send/receive calls
  drm/i915/guc: unify notify() functions
  HAX: force enable_guc=2 and WA i915#571

 drivers/gpu/drm/i915/gt/intel_gt_irq.c        |   2 +-
 drivers/gpu/drm/i915/gt/selftest_gt_pm.c      |   9 +
 drivers/gpu/drm/i915/gt/uc/intel_guc.c        |  43 +--
 drivers/gpu/drm/i915/gt/uc/intel_guc.h        |  41 +--
 drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c     | 298 +++++++-----------
 drivers/gpu/drm/i915/gt/uc/intel_guc_ct.h     |  55 ++--
 drivers/gpu/drm/i915/gt/uc/intel_guc_log.c    |   6 +-
 .../gpu/drm/i915/gt/uc/intel_guc_submission.c |   1 -
 drivers/gpu/drm/i915/gt/uc/intel_uc.c         |  36 +--
 drivers/gpu/drm/i915/i915_params.h            |   2 +-
 10 files changed, 186 insertions(+), 307 deletions(-)

-- 
2.23.0

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2019-12-10 21:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10 21:09 Daniele Ceraolo Spurio [this message]
2019-12-10 21:09 ` [Intel-gfx] [PATCH 1/5] drm/i915/guc: Merge communication_stop and communication_disable Daniele Ceraolo Spurio
2019-12-11 13:12   ` Michal Wajdeczko
2019-12-10 21:09 ` [Intel-gfx] [PATCH 2/5] drm/i915/guc/ct: stop expecting multiple CT channels Daniele Ceraolo Spurio
2019-12-11 13:43   ` Michal Wajdeczko
2019-12-11 17:47     ` Daniele Ceraolo Spurio
2019-12-10 21:09 ` [Intel-gfx] [PATCH 3/5] drm/i915/guc: remove function pointers for send/receive calls Daniele Ceraolo Spurio
2019-12-11 14:04   ` Michal Wajdeczko
2019-12-11 18:01     ` Daniele Ceraolo Spurio
2019-12-10 21:09 ` [Intel-gfx] [PATCH 4/5] drm/i915/guc: unify notify() functions Daniele Ceraolo Spurio
2019-12-11 14:26   ` Michal Wajdeczko
2019-12-10 21:09 ` [Intel-gfx] [PATCH 5/5] HAX: force enable_guc=2 and WA i915#571 Daniele Ceraolo Spurio
2019-12-11  5:25 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Simplify GuC communication handling Patchwork
2019-12-11  5:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2019-12-11 11:33 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2019-12-11 11:52   ` Chris Wilson

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=20191210210919.30846-1-daniele.ceraolospurio@intel.com \
    --to=daniele.ceraolospurio@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.