From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org, ashutosh.dixit@linux.intel.com,
andy.shyti@linux.intel.com
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915: Reduce I915_MAX_GT to 2
Date: Fri, 02 Jun 2023 17:38:04 -0700 [thread overview]
Message-ID: <87leh1l6s3.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230603001348.GS6953@mdroper-desk1.amr.corp.intel.com>
On Fri, 02 Jun 2023 17:13:48 -0700, Matt Roper wrote:
>
> On Fri, Jun 02, 2023 at 04:17:53PM -0700, Matt Atwood wrote:
> > According to Ashutosh there is no current or planned product in i915 for
> > I915_MAX_GT to be 4 anymore.
> >
> > Cc: Matt Roper <matthew.d.roper@intel.com>
> > Cc: Ashutosh Dixit <ashutosh.dixit@linux.intel.com>
> > Cc: Andi Shyti <andy.shyti@linux.intel.com>
> > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
> >
> > Signed-off-by: Matt Atwood <matthew.s.atwood@intel.com>
>
> MTL is the only platform where we've enabled multiple GTs at the moment
> (one primary, one media). Although multi-tile platforms could
> potentially have more, we haven't enabled multi-tile on i915 for xehpsdv
> and pvc, and will probably refocus that work on the Xe driver now. So
> reducing to 2 sounds fine.
>
> Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
Thanks Matt R for confirming reducing to 2 is ok:
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
next prev parent reply other threads:[~2023-06-03 0:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 23:17 [Intel-gfx] [PATCH 0/2] Update various *MAX_GT* definitions Matt Atwood
2023-06-02 23:17 ` [Intel-gfx] [PATCH 1/2] drm/i915: Reduce I915_MAX_GT to 2 Matt Atwood
2023-06-03 0:13 ` Matt Roper
2023-06-03 0:38 ` Dixit, Ashutosh [this message]
2023-06-02 23:17 ` [Intel-gfx] [PATCH 2/2] drm/i915: rename I915_PMU_MAX_GTS to I915_PMU_MAX_GT Matt Atwood
2023-06-03 0:15 ` Matt Roper
2023-06-05 9:24 ` Tvrtko Ursulin
2023-06-03 1:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Update various *MAX_GT* definitions Patchwork
2023-06-03 1:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-05 17:00 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-06-06 18:05 ` Matt Roper
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=87leh1l6s3.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=andy.shyti@linux.intel.com \
--cc=ashutosh.dixit@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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 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.