From: John Spotswood <john.a.spotswood@intel.com>
To: "Sagar Arun Kamble" <sagar.a.kamble@intel.com>,
"Chris Wilson" <chris@chris-wilson.co.uk>,
"Michel Thierry" <michel.thierry@intel.com>,
"Piotr Piórkowski" <piotr.piorkowski@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/guc: Removed unused GuC parameters.
Date: Thu, 01 Mar 2018 11:14:37 -0800 [thread overview]
Message-ID: <1519931677.9578.6.camel@intel.com> (raw)
In-Reply-To: <9e20cda2-998f-fcc6-4322-de2880fedd48@intel.com>
On Thu, 2018-03-01 at 17:35 +0530, Sagar Arun Kamble wrote:
>
> On 3/1/2018 1:32 PM, Chris Wilson wrote:
> >
> > Quoting Michel Thierry (2018-02-28 22:07:51)
> > >
> > > On 28/02/18 12:26, Michel Thierry wrote:
> > > >
> > > > On 28/02/18 10:42, Piotr Piórkowski wrote:
> > > > >
> > > > > In the i915 driver, there is a function,
> > > > > intel_guc_init_params(),
> > > > > which initializes the GuC parameter block which is passed
> > > > > into
> > > > > the GuC. There is parameter GUC_CTL_DEVICE_INFO with values
> > > > > GfxGtType and GfxCoreFamily unused by GuC.
> > > > >
> > > > > This patch remove GUC_CTL_DEVICE_INFO with GfxGtType and
> > > > > GfxCoreFamily parameters and also unnecessary functions
> > > > > get_gt_type() and get_core_family().
> > > > >
> > > > Hi,
> > > >
> > > > Looking at the fw code, you're partially right, GfxGtType is
> > > > ignored...
> > > > but GfxCoreFamily isn't.
> > > >
> > > Unless whoever wrote the fw was smart enough to forget to call
> > > the
> > > function that is reading GfxCoreFamily... I didn't count on that.
> > Is the intention to use GfxCoreFamily documented, i.e. are they
> > expecting it part of the interface and may re-instantiate the check
> > "because it was always supposed to exist" in some future version?
> Usage of GfxCoreFamily is only in SLPC and for platform specific
> initialization and might be removed in future interfaces.
> If needed, we can add as part of SLPC patches.
Michel and I have traced through the FW code, and both parameters are
unused. GfxCoreFamily does appear to be set in the FW, and it gets
passed into SLPC, but then it never gets used. I have confirmed with
FW developers that these parameters have been removed for future gens.
> >
> > -Chris
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-01 19:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 18:42 [PATCH] drm/i915/guc: Removed unused GuC parameters Piotr Piórkowski
2018-02-28 19:16 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-28 20:26 ` [PATCH] " Michel Thierry
2018-02-28 22:07 ` Michel Thierry
2018-03-01 8:02 ` Chris Wilson
2018-03-01 12:05 ` Sagar Arun Kamble
2018-03-01 19:14 ` John Spotswood [this message]
2018-03-02 7:23 ` Sagar Arun Kamble
2018-03-05 11:12 ` Piorkowski, Piotr
2018-03-06 23:50 ` John Spotswood
2018-02-28 23:57 ` ✗ Fi.CI.IGT: failure for " Patchwork
2018-03-05 13:13 ` [PATCH v2] drm/i915/guc: Remove GUC_CTL_DEVICE_INFO parameter Piotr Piórkowski
2018-03-05 18:12 ` Michel Thierry
2018-03-06 4:37 ` Sagar Arun Kamble
2018-04-13 8:55 ` Piorkowski, Piotr
2018-03-06 12:06 ` [PATCH v3] " Piotr Piórkowski
2018-04-13 8:52 ` [PATCH v4] " Piotr Piórkowski
2018-04-13 12:23 ` Chris Wilson
2018-03-05 13:37 ` ✗ Fi.CI.BAT: failure for drm/i915/guc: Removed unused GuC parameters. (rev2) Patchwork
2018-03-06 13:23 ` ✓ Fi.CI.BAT: success for drm/i915/guc: Removed unused GuC parameters. (rev3) Patchwork
2018-03-06 17:41 ` ✗ Fi.CI.IGT: warning " Patchwork
2018-04-13 10:33 ` ✓ Fi.CI.BAT: success for drm/i915/guc: Removed unused GuC parameters. (rev4) Patchwork
2018-04-13 11:22 ` ✓ Fi.CI.IGT: " 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=1519931677.9578.6.camel@intel.com \
--to=john.a.spotswood@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michel.thierry@intel.com \
--cc=piotr.piorkowski@intel.com \
--cc=sagar.a.kamble@intel.com \
/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