From: Bob Paauwe <bob.j.paauwe@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 3/3] drm/i915: Remove HAS_FULL_PPGTT and device_info.ppgtt enum (v3)
Date: Thu, 7 Feb 2019 11:13:15 -0800 [thread overview]
Message-ID: <20190207111315.3fb73eb5@bpaauwe-desk.fm.intel.com> (raw)
In-Reply-To: <154955771820.27542.5151671235510292778@skylake-alporthouse-com>
On Thu, 7 Feb 2019 16:41:58 +0000
Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Bob Paauwe (2019-02-07 16:29:53)
> > With the address range being specified for each platform, we can use
> > that instead of the .ppgtt enum to handle the differences between
> > 3 level and 4 level PPGTT. In most cases, we really only care if the
> > platform supports PPGTT or not. Because of this, we can now remove
> > the HAS_FULL_PPGTT macro and the device info ppgtt field.
> >
> > Aliasing PPGTT used by GEN 6 is a bit of an exception. For those cases,
> > it makes just as much sense to check if we're running on GEN 6 as it
> > does to check a device info flag.
> >
> > v2: Reword the commit message to make it correct wrt aliasing ppgtt (Chris)
> > v3: Rebase on current drm-tip
>
> The point of adding the type into the device_info was that it was
> included in the error state so that I didn't have to remember which w/a
> applied to which gen. gen6 has full-ppgtt, we can't enabled it as no one
> has solved how to make it work.
> -Chris
OK, I had assumed that the point was to control the code flow so I'm
not sure how best to proceed.
This patch doesn't really change any program logic so we can drop it
and keep both the ppgtt type and size in device info.
Alternately, I could add the ppgtt size to error state output. But I'm
not sure that really provides what you're looking for wrt gen6.
If you have a better idea or something specific you'd like to see me do
with this, I could use some direction.
Thanks,
Bob
--
--
Bob Paauwe
Bob.J.Paauwe@intel.com
IOTG / PED Software Organization
Intel Corp. Folsom, CA
(916) 356-6193
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-02-07 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 16:29 [PATCH 1/3] drm/i915: Make 48bit full ppgtt configuration generic (v11) Bob Paauwe
2019-02-07 16:29 ` [PATCH 2/3] drm/i915: Remove HAS_4LVL_PPGTT Bob Paauwe
2019-02-07 16:29 ` [PATCH 3/3] drm/i915: Remove HAS_FULL_PPGTT and device_info.ppgtt enum (v3) Bob Paauwe
2019-02-07 16:41 ` Chris Wilson
2019-02-07 19:13 ` Bob Paauwe [this message]
2019-03-14 20:09 ` Bob Paauwe
2019-03-14 20:58 ` Chris Wilson
2019-02-07 16:53 ` [PATCH 1/3] drm/i915: Make 48bit full ppgtt configuration generic (v11) Chris Wilson
2019-02-07 17:37 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/3] " Patchwork
2019-02-07 17:58 ` ✓ Fi.CI.BAT: success " Patchwork
2019-02-07 20:16 ` ✗ Fi.CI.IGT: 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=20190207111315.3fb73eb5@bpaauwe-desk.fm.intel.com \
--to=bob.j.paauwe@intel.com \
--cc=chris@chris-wilson.co.uk \
--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