From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: BIOS and power context stolen mem handling for VLV v6
Date: Wed, 8 May 2013 14:28:42 +0100 [thread overview]
Message-ID: <20130508132842.GF1985@cantiga.alporthouse.com> (raw)
In-Reply-To: <20130507162306.284a9a91@jbarnes-desktop>
On Tue, May 07, 2013 at 04:23:06PM -0700, Jesse Barnes wrote:
> Ok ok I'm sold, at least until we find otherwise or Alan's team reports
> back that the GTT space is needed.
>
> Extending the interface to not reserve GTT space makes sense; I can do
> that as a follow up, if you're ok with the existing code.
I'm happy with the rest of the patch - just wishing that the size was
expressed in pages (6 * GTT_PAGE_SIZE) and similarly the mask
~(GTT_PAGE_SIZE-1).
Bring on the change to avoid reserving GTT space and lets hope it
sticks! :)
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-05-08 13:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 18:50 [PATCH] drm/i915: BIOS and power context stolen mem handling for VLV v3 Jesse Barnes
2013-05-07 19:34 ` [PATCH] drm/i915: BIOS and power context stolen mem handling for VLV v4 Jesse Barnes
2013-05-07 19:50 ` Chris Wilson
2013-05-07 20:37 ` [PATCH] drm/i915: BIOS and power context stolen mem handling for VLV v5 Jesse Barnes
2013-05-07 21:34 ` [PATCH] drm/i915: BIOS and power context stolen mem handling for VLV v6 Jesse Barnes
2013-05-07 21:57 ` Chris Wilson
2013-05-07 22:08 ` Jesse Barnes
2013-05-07 22:14 ` Chris Wilson
2013-05-07 22:32 ` Jesse Barnes
2013-05-07 23:23 ` Jesse Barnes
2013-05-08 13:28 ` Chris Wilson [this message]
2013-05-07 23:18 ` Jesse Barnes
2013-05-08 2:56 ` Teres Alexis, Alan Previn
2013-05-07 19:45 ` [PATCH] drm/i915: BIOS and power context stolen mem handling for VLV v3 Chris Wilson
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=20130508132842.GF1985@cantiga.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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