From: "Thomas Hellström (Intel)" <thomas_os@shipmail.org>
To: Robert Beckett <bob.beckett@collabora.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Matthew Auld <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH v5 1/5] drm/i915: add needs_compact_pt flag
Date: Thu, 27 Jan 2022 10:37:49 +0100 [thread overview]
Message-ID: <ce91e091-0df1-5c4d-a070-7b82d74d3f42@shipmail.org> (raw)
In-Reply-To: <19bf8290-9308-b5c6-eb73-4020fa81aa66@collabora.com>
On 1/26/22 18:11, Robert Beckett wrote:
>
>
> On 26/01/2022 13:49, Thomas Hellström (Intel) wrote:
>>
>> On 1/25/22 20:35, Robert Beckett wrote:
>>> From: Ramalingam C <ramalingam.c@intel.com>
>>>
>>> Add a new platform flag, needs_compact_pt, to mark the requirement of
>>> compact pt layout support for the ppGTT when using 64K GTT pages.
>>>
>>> With this flag has_64k_pages will only indicate requirement of 64K
>>> GTT page sizes or larger for device local memory access.
>>>
>>> Suggested-by: Matthew Auld <matthew.auld@intel.com>
>>> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
>>> Signed-off-by: Robert Beckett <bob.beckett@collabora.com>
>>> ---
>>> drivers/gpu/drm/i915/i915_drv.h | 10 +++++++---
>>> drivers/gpu/drm/i915/i915_pci.c | 2 ++
>>> drivers/gpu/drm/i915/intel_device_info.h | 1 +
>>> 3 files changed, 10 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/i915_drv.h
>>> b/drivers/gpu/drm/i915/i915_drv.h
>>> index 44c1f98144b4..1258b7779705 100644
>>> --- a/drivers/gpu/drm/i915/i915_drv.h
>>> +++ b/drivers/gpu/drm/i915/i915_drv.h
>>> @@ -1512,12 +1512,16 @@ IS_SUBPLATFORM(const struct drm_i915_private
>>> *i915,
>>> /*
>>> * Set this flag, when platform requires 64K GTT page sizes or
>>> larger for
>>> - * device local memory access. Also this flag implies that we
>>> require or
>>> - * at least support the compact PT layout for the ppGTT when using
>>> the 64K
>>> - * GTT pages.
>>
>> Why do we remove these comment lines?
> Because HAS_64K_PAGES now means just 64K page, it no longer means also
> requires compact pt.
> This is to support other products that will have 64K but not have the
> PDE non-sharing restriction in future.
>
> Those lines moved to the next change NEEDS_COMPACT_PT, which is now
> separate.
Yes, NEEDS_COMPACT_PT indicates that compact is *required* but does
"HAS_64K_PAGES" still mean compact is supported? That information is lost.
/Thomas
next prev parent reply other threads:[~2022-01-27 9:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 19:35 [Intel-gfx] [PATCH v5 0/5] discrete card 64K page support Robert Beckett
2022-01-25 19:35 ` [Intel-gfx] [PATCH v5 1/5] drm/i915: add needs_compact_pt flag Robert Beckett
2022-01-26 13:49 ` Thomas Hellström (Intel)
2022-01-26 17:11 ` Robert Beckett
2022-01-27 9:37 ` Thomas Hellström (Intel) [this message]
2022-01-31 14:19 ` Robert Beckett
2022-01-31 14:58 ` Thomas Hellström
2022-01-25 19:35 ` [Intel-gfx] [PATCH v5 2/5] drm/i915: enforce min GTT alignment for discrete cards Robert Beckett
2022-01-26 15:45 ` Thomas Hellström (Intel)
2022-01-26 17:21 ` Robert Beckett
2022-01-25 19:35 ` [Intel-gfx] [PATCH v5 3/5] drm/i915: support 64K GTT pages " Robert Beckett
2022-01-31 11:19 ` Thomas Hellström
2022-01-25 19:35 ` [Intel-gfx] [PATCH v5 4/5] drm/i915: add gtt misalignment test Robert Beckett
2022-01-26 14:05 ` Thomas Hellström (Intel)
2022-01-26 17:22 ` Robert Beckett
2022-01-25 19:35 ` [Intel-gfx] [PATCH v5 5/5] drm/i915/uapi: document behaviour for DG2 64K support Robert Beckett
2022-01-26 14:11 ` Thomas Hellström (Intel)
2022-01-25 22:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for discrete card 64K page support (rev3) Patchwork
2022-01-25 22:14 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-01-25 22:42 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=ce91e091-0df1-5c4d-a070-7b82d74d3f42@shipmail.org \
--to=thomas_os@shipmail.org \
--cc=airlied@linux.ie \
--cc=bob.beckett@collabora.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.auld@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.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;
as well as URLs for NNTP newsgroup(s).