From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Jani Nikula <jani.nikula@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH v5] drm/i915: Remove i915.enable_ppgtt override
Date: Thu, 27 Sep 2018 13:57:53 +0300 [thread overview]
Message-ID: <153804587294.12651.7216001532114970960@jlahtine-desk.ger.corp.intel.com> (raw)
In-Reply-To: <153803850331.11401.8913862675827627936@skylake-alporthouse-com>
Quoting Chris Wilson (2018-09-27 11:55:03)
> Quoting Joonas Lahtinen (2018-09-27 09:20:06)
> > Quoting Chris Wilson (2018-09-26 23:12:22)
> > > Now that we are confident in providing full-ppgtt where supported,
> > > remove the ability to override the context isolation.
> > >
> > > v2: Remove faked aliasing-ppgtt for testing as it no longer is accepted.
> > > v3: s/USES/HAS/ to match usage and reject attempts to load the module on
> > > old GVT-g setups that do not provide support for full-ppgtt.
> > > v4: Insulate ABI ppGTT values from our internal enum (later plans
> > > involve moving ppGTT depth out of the enum, thus potentially breaking
> > > ABI unless we document the current values).
> > >
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > > Cc: Matthew Auld <matthew.auld@intel.com>
> > > Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> #v3
> >
> > + Jani for awareness when handling dinq, this solidifies existing uAPI
> > And drops the reporting of 48-bit ppGTT through this getparam as we
> > already have context specific I915_CONTEXT_PARAM_GTT_SIZE for that and
> > no known abusers for the unintended reporting outside 0,1,2 set.
>
> Are we past the 4.20 cutoff? I'd rather have this in 4.21 so that we
> have a cycle in front of users before sealing the transition.
Yes we are. Just go ahead with the merge.
Regards, Joonas
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-09-27 10:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 11:48 [PATCH v4] drm/i915: Remove i915.enable_ppgtt override Chris Wilson
2018-09-25 12:06 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2018-09-25 12:28 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-09-25 13:14 ` Patchwork
2018-09-25 13:22 ` [PATCH v4] " Joonas Lahtinen
2018-09-25 18:01 ` Zhi Wang
2018-09-26 1:06 ` He, Min
2018-09-26 8:02 ` Joonas Lahtinen
2018-09-26 12:29 ` Zhi Wang
2018-10-08 9:53 ` Zhenyu Wang
2018-10-08 13:58 ` Wang, Zhi A
2018-10-09 2:15 ` Zhenyu Wang
2018-10-09 6:55 ` Zhi Wang
2018-10-09 7:35 ` Chris Wilson
2018-09-25 13:27 ` Joonas Lahtinen
2018-09-26 13:16 ` Joonas Lahtinen
2018-09-26 20:12 ` [PATCH v5] " Chris Wilson
2018-09-27 8:20 ` Joonas Lahtinen
2018-09-27 8:55 ` Chris Wilson
2018-09-27 10:57 ` Joonas Lahtinen [this message]
2018-09-27 11:07 ` Chris Wilson
2018-09-26 21:34 ` ✗ Fi.CI.SPARSE: warning for drm/i915: Remove i915.enable_ppgtt override (rev2) Patchwork
2018-09-26 21:55 ` ✓ Fi.CI.BAT: success " Patchwork
2018-09-27 3:00 ` ✓ 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=153804587294.12651.7216001532114970960@jlahtine-desk.ger.corp.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=matthew.auld@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.