public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Sujaritha <sujaritha.sundaresan@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3 2/2] drm/i915/guc : Decouple logs from submission
Date: Tue, 19 Sep 2017 10:19:47 -0700	[thread overview]
Message-ID: <db16deba-de7f-39ec-0cff-bcc6d518d37e@intel.com> (raw)
In-Reply-To: <34978f9e-f9cc-75df-b2c1-dc960ec8f251@intel.com>

Sure, I will rename the commit message. Thanks.


On 09/19/2017 10:11 AM, Daniele Ceraolo Spurio wrote:
> Since we're not decoupling just logs, maybe the commit could be 
> renamed to "Decouple ADS and logs from submission"
>
> On 19/09/17 09:15, Sujaritha Sundaresan wrote:
>> The Additional Data Struct (ADS) contains objects that are required by
>> guc post FW load and are not necessarily submission-only (although 
>> that's
>> our current only use-case). If in the future we load GuC with submission
>> disabled to use some other GuC feature we might still end up requiring
>> something inside the ADS, so it makes more sense for them to be always
>> created if GuC is loaded.
>
> To make a concrete example, the pages used by GuC to save state during 
> suspend are allocated as part of the ADS.
>
>> Similarly, we still want to access GuC logs even if GuC submission is
>> disable to debug issues with GuC loading or with wathever we're using 
>> GuC for.
>>
>> v2: Decoupling ads together with logs
>> v3: Group initialization of GuC objects
>>
>> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> Cc: Oscar Mateo <oscar.mateo@intel.com>
>> Cc: Anusha Srivatsa <anusha.srivatsa@intel.com>
>> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>> Signed-off-by: Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
>
> Acked-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>

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

  reply	other threads:[~2017-09-19 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 16:15 [PATCH v3 2/2] drm/i915/guc : Decouple logs from submission Sujaritha Sundaresan
2017-09-19 17:11 ` Daniele Ceraolo Spurio
2017-09-19 17:19   ` Sujaritha [this message]
2017-09-19 17:26 ` [PATCH v3 2/2] drm/i915/guc : Decouple logs and ADS " Sujaritha Sundaresan
2017-09-21 18:39 ` [PATCH v4 " Sujaritha Sundaresan

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=db16deba-de7f-39ec-0cff-bcc6d518d37e@intel.com \
    --to=sujaritha.sundaresan@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