From: David Weinehall <david.weinehall@linux.intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 7/7] drm/i915: Move stolen memory initialization earlier during loading
Date: Fri, 22 Jan 2016 14:23:08 +0200 [thread overview]
Message-ID: <20160122122308.GK3193@boom> (raw)
In-Reply-To: <1453209992-25995-8-git-send-email-imre.deak@intel.com>
On Tue, Jan 19, 2016 at 03:26:32PM +0200, Imre Deak wrote:
> The only device specific dependency of the stolen memory setup is the
> MMIO mapping and the stolen memory size. Both are already available in
> i915_gtt_init(), so move the stolen initialization to there. The
> clean-up code for i915_gtt_init() is in i915_global_gtt_cleanup(), so
> move the stolen memory clean-up code there too.
>
> This will be needed by an upcoming patch that needs the details of the
> memory we reserve, but the change is also part of our generic goal to
> move the initialization of resources with no or little dependencies on
> other device specific resources towards the beginning of the init
> sequence.
>
> Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
Reviewed-by: David Weinehall <david.weinehall@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-01-22 12:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 13:26 [PATCH 0/7] drm/i915: Move load time stolen memory init earlier Imre Deak
2016-01-19 13:26 ` [PATCH 1/7] drm/i915: Sanitize up DMC/CSR ucode cleanup code Imre Deak
2016-01-22 12:10 ` David Weinehall
2016-01-19 13:26 ` [PATCH 2/7] drm/i915: Sanitize i915_get_bridge_dev() error path Imre Deak
2016-01-22 12:11 ` David Weinehall
2016-01-19 13:26 ` [PATCH 3/7] drm/i915: Sanitize GEM shrinker init and clean-up Imre Deak
2016-01-22 12:15 ` David Weinehall
2016-01-19 13:26 ` [PATCH 4/7] drm/i915: Sanitize i915_gem_load() " Imre Deak
2016-01-22 12:17 ` David Weinehall
2016-01-19 13:26 ` [PATCH 5/7] drm/i915: Move allocation of various workqueues earlier during init Imre Deak
2016-01-22 12:19 ` David Weinehall
2016-01-19 13:26 ` [PATCH 6/7] drm/i915: Move MCHBAR setup " Imre Deak
2016-01-22 12:21 ` David Weinehall
2016-01-19 13:26 ` [PATCH 7/7] drm/i915: Move stolen memory initialization earlier during loading Imre Deak
2016-01-22 12:23 ` David Weinehall [this message]
2016-01-27 16:39 ` Imre Deak
2016-01-19 13:49 ` ✗ Fi.CI.BAT: failure for drm/i915: Move load time stolen memory init earlier Patchwork
2016-01-19 16:22 ` Imre Deak
2016-01-25 16:21 ` Daniel Vetter
2016-01-25 17:34 ` Imre Deak
2016-01-25 17:47 ` Daniel Vetter
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=20160122122308.GK3193@boom \
--to=david.weinehall@linux.intel.com \
--cc=imre.deak@intel.com \
--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 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.