Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/guc: drop guc shared area
Date: Thu, 31 Oct 2019 09:36:45 -0700	[thread overview]
Message-ID: <20191031163645.GB6444@sdutt> (raw)
In-Reply-To: <20191031013040.25803-2-daniele.ceraolospurio@intel.com>

On Wed, Oct 30, 2019 at 06:30:40PM -0700, Daniele Ceraolo Spurio wrote:
>Recent GuC doesn't require the shared area. We still have one user in
>i915 (engine reset via guc) because we haven't updated the command to
>match the current guc submission flow [1]. Since the flow in guc is
>about to change again, just disable the command for now and add a note
>that we'll implement it as part of the new flow.
>
>[1] https://patchwork.freedesktop.org/patch/295038/
>
>Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
>Cc: John Harrison <John.C.Harrison@Intel.com>
>Cc: Matthew Brost <matthew.brost@intel.com>
>Cc: Fernando Pacheco <fernando.pacheco@intel.com>
>---
> drivers/gpu/drm/i915/gt/uc/intel_guc.c | 50 ++------------------------
> drivers/gpu/drm/i915/gt/uc/intel_guc.h |  2 --
> 2 files changed, 3 insertions(+), 49 deletions(-)
>

This patch also works with the GuC redesign work being done.

Reviewed-by: Matthew Brost <matthew.brost@intel.com>
_______________________________________________
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: Matthew Brost <matthew.brost@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915/guc: drop guc shared area
Date: Thu, 31 Oct 2019 09:36:45 -0700	[thread overview]
Message-ID: <20191031163645.GB6444@sdutt> (raw)
Message-ID: <20191031163645.Bh7G_nrJmGbAdBR0AxqXQZA3T4ZLBBT38hab4k86O0s@z> (raw)
In-Reply-To: <20191031013040.25803-2-daniele.ceraolospurio@intel.com>

On Wed, Oct 30, 2019 at 06:30:40PM -0700, Daniele Ceraolo Spurio wrote:
>Recent GuC doesn't require the shared area. We still have one user in
>i915 (engine reset via guc) because we haven't updated the command to
>match the current guc submission flow [1]. Since the flow in guc is
>about to change again, just disable the command for now and add a note
>that we'll implement it as part of the new flow.
>
>[1] https://patchwork.freedesktop.org/patch/295038/
>
>Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
>Cc: John Harrison <John.C.Harrison@Intel.com>
>Cc: Matthew Brost <matthew.brost@intel.com>
>Cc: Fernando Pacheco <fernando.pacheco@intel.com>
>---
> drivers/gpu/drm/i915/gt/uc/intel_guc.c | 50 ++------------------------
> drivers/gpu/drm/i915/gt/uc/intel_guc.h |  2 --
> 2 files changed, 3 insertions(+), 49 deletions(-)
>

This patch also works with the GuC redesign work being done.

Reviewed-by: Matthew Brost <matthew.brost@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-10-31 16:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31  1:30 [PATCH 1/2] drm/i915: drop lrc header page Daniele Ceraolo Spurio
2019-10-31  1:30 ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-10-31  1:30 ` [PATCH 2/2] drm/i915/guc: drop guc shared area Daniele Ceraolo Spurio
2019-10-31  1:30   ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-10-31  9:04   ` Chris Wilson
2019-10-31  9:04     ` [Intel-gfx] " Chris Wilson
2019-10-31 16:36   ` Matthew Brost [this message]
2019-10-31 16:36     ` Matthew Brost
2019-10-31  2:09 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: drop lrc header page Patchwork
2019-10-31  2:09   ` [Intel-gfx] " Patchwork
2019-10-31  8:14 ` [PATCH 1/2] " Chris Wilson
2019-10-31  8:14   ` [Intel-gfx] " Chris Wilson
2019-10-31 16:23 ` Matthew Brost
2019-10-31 16:23   ` [Intel-gfx] " Matthew Brost
2019-11-01  7:16 ` ✓ Fi.CI.IGT: success for series starting with [1/2] " Patchwork
2019-11-01  7:16   ` [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=20191031163645.GB6444@sdutt \
    --to=matthew.brost@intel.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox