From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: [PATCH] drm/i915: Allow HW status page to be bound high
Date: Wed, 09 Aug 2017 16:54:53 +0300 [thread overview]
Message-ID: <1502286893.5376.68.camel@linux.intel.com> (raw)
In-Reply-To: <20170808125417.1098-1-chris@chris-wilson.co.uk>
On ti, 2017-08-08 at 13:54 +0100, Chris Wilson wrote:
> At the time of commit 1f767e02d69f ("drm/i915: HWS must be in the
> mappable region for g33"), drm_mm insertion would often default to
> placing a new object high in the zone forcing us to specify that certain
> HWSP must be bound within the low mappable region. Since then, drm_mm
> has gained more finesse over its placement and exposes that to the
> caller, commit 4e64e5539d15 ("drm: Improve drm_mm search (and fix
> topdown allocation) with rbtrees"). As such where possible we want the
> HWSP to be outside of the mappable aperture and so need to tell to
> specify that it is to be pinned high.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Michel Thierry <michel.thierry@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Mika Kuoppala <mika.kuoppala@intel.com>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-08-09 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 12:54 [PATCH] drm/i915: Allow HW status page to be bound high Chris Wilson
2017-08-09 13:54 ` Joonas Lahtinen [this message]
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=1502286893.5376.68.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@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