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: [PATCH 0/4] Start removing legacy guc code
Date: Wed,  6 Nov 2019 14:25:46 -0800	[thread overview]
Message-ID: <20191106222550.20752-1-daniele.ceraolospurio@intel.com> (raw)

Now that we have a clearer picture of what the new GuC submission flow
is going to look like, we can start removing the code that we know we
won't use in the future. As a starter, we can get rid of the doorbells
and the GuC client code, because the former will be replaced by an H2G
notification to GuC while the latter won't make sense in the new flow as
the proxy submission mechanism is gone.

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 (4):
  drm/i915/guc: Drop leftover preemption code
  drm/i915/guc: add a helper to allocate and map guc vma
  drm/i915/guc: kill doorbell code and selftests
  drm/i915/guc: kill the GuC client

 drivers/gpu/drm/i915/gt/intel_reset.c         |   6 +-
 drivers/gpu/drm/i915/gt/uc/intel_guc.c        |  34 +
 drivers/gpu/drm/i915/gt/uc/intel_guc.h        |  16 +-
 drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c    |  21 +-
 drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h   |   1 -
 .../gpu/drm/i915/gt/uc/intel_guc_submission.c | 627 +++---------------
 .../gpu/drm/i915/gt/uc/intel_guc_submission.h |  54 +-
 drivers/gpu/drm/i915/gt/uc/intel_uc.c         |   7 +-
 drivers/gpu/drm/i915/gt/uc/selftest_guc.c     | 299 ---------
 drivers/gpu/drm/i915/i915_debugfs.c           |  18 -
 .../drm/i915/selftests/i915_live_selftests.h  |   1 -
 11 files changed, 141 insertions(+), 943 deletions(-)
 delete mode 100644 drivers/gpu/drm/i915/gt/uc/selftest_guc.c

-- 
2.23.0

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

WARNING: multiple messages have this Message-ID (diff)
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/4] Start removing legacy guc code
Date: Wed,  6 Nov 2019 14:25:46 -0800	[thread overview]
Message-ID: <20191106222550.20752-1-daniele.ceraolospurio@intel.com> (raw)
Message-ID: <20191106222546.kaddMmZDCfdmlqd4QLP2idsSY3TBjJ9sZqHW08Xm_iw@z> (raw)

Now that we have a clearer picture of what the new GuC submission flow
is going to look like, we can start removing the code that we know we
won't use in the future. As a starter, we can get rid of the doorbells
and the GuC client code, because the former will be replaced by an H2G
notification to GuC while the latter won't make sense in the new flow as
the proxy submission mechanism is gone.

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 (4):
  drm/i915/guc: Drop leftover preemption code
  drm/i915/guc: add a helper to allocate and map guc vma
  drm/i915/guc: kill doorbell code and selftests
  drm/i915/guc: kill the GuC client

 drivers/gpu/drm/i915/gt/intel_reset.c         |   6 +-
 drivers/gpu/drm/i915/gt/uc/intel_guc.c        |  34 +
 drivers/gpu/drm/i915/gt/uc/intel_guc.h        |  16 +-
 drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c    |  21 +-
 drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h   |   1 -
 .../gpu/drm/i915/gt/uc/intel_guc_submission.c | 627 +++---------------
 .../gpu/drm/i915/gt/uc/intel_guc_submission.h |  54 +-
 drivers/gpu/drm/i915/gt/uc/intel_uc.c         |   7 +-
 drivers/gpu/drm/i915/gt/uc/selftest_guc.c     | 299 ---------
 drivers/gpu/drm/i915/i915_debugfs.c           |  18 -
 .../drm/i915/selftests/i915_live_selftests.h  |   1 -
 11 files changed, 141 insertions(+), 943 deletions(-)
 delete mode 100644 drivers/gpu/drm/i915/gt/uc/selftest_guc.c

-- 
2.23.0

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

             reply	other threads:[~2019-11-06 22:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 22:25 Daniele Ceraolo Spurio [this message]
2019-11-06 22:25 ` [Intel-gfx] [PATCH 0/4] Start removing legacy guc code Daniele Ceraolo Spurio
2019-11-06 22:25 ` [PATCH 1/4] drm/i915/guc: Drop leftover preemption code Daniele Ceraolo Spurio
2019-11-06 22:25   ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-11-07  8:17   ` Chris Wilson
2019-11-07  8:17     ` [Intel-gfx] " Chris Wilson
2019-11-06 22:25 ` [PATCH 2/4] drm/i915/guc: add a helper to allocate and map guc vma Daniele Ceraolo Spurio
2019-11-06 22:25   ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-11-07  8:19   ` Chris Wilson
2019-11-07  8:19     ` [Intel-gfx] " Chris Wilson
2019-11-06 22:25 ` [PATCH 3/4] drm/i915/guc: kill doorbell code and selftests Daniele Ceraolo Spurio
2019-11-06 22:25   ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-11-14 23:56   ` John Harrison
2019-11-14 23:56     ` [Intel-gfx] " John Harrison
2019-11-18 22:20     ` Daniele Ceraolo Spurio
2019-11-18 22:20       ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-11-06 22:25 ` [PATCH 4/4] drm/i915/guc: kill the GuC client Daniele Ceraolo Spurio
2019-11-06 22:25   ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-11-15  0:22   ` John Harrison
2019-11-15  0:22     ` [Intel-gfx] " John Harrison
2019-11-07  0:52 ` ✗ Fi.CI.CHECKPATCH: warning for Start removing legacy guc code Patchwork
2019-11-07  0:52   ` [Intel-gfx] " Patchwork
2019-11-07  1:08 ` ✗ Fi.CI.DOCS: " Patchwork
2019-11-07  1:08   ` [Intel-gfx] " Patchwork
2019-11-07  1:15 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-07  1:15   ` [Intel-gfx] " Patchwork
2019-11-08  4:36 ` ✓ Fi.CI.IGT: " Patchwork
2019-11-08  4:36   ` [Intel-gfx] " 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=20191106222550.20752-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.