From: Jani Nikula <jani.nikula@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Akash Goel <akash.goel@intel.com>
Subject: Re: [PATCH 0/7] Increase the utilization of Stolen area on VLV
Date: Thu, 09 Jan 2014 10:30:17 +0200 [thread overview]
Message-ID: <87a9f5blra.fsf@intel.com> (raw)
In-Reply-To: <1389245389-10746-1-git-send-email-akash.goel@intel.com>
Hi Akash, please check your git sendemail.thread configuration (or
format.thread for format-patch) to make the patches in-reply-to the
cover letter.
Thanks,
Jani.
On Thu, 09 Jan 2014, akash.goel@intel.com wrote:
> From: Akash Goel <akash.goel@intel.com>
>
> These patches are mainly for increasing the utilization
> of stolen memory area on VLV.
> Although the changes were already there to allocate few
> internal resources from stolen area, but due to a resource
> conflict the stolen area was not getting used at all.
> The third patch is also a bug fix but specific only to VLV.
> The rest of the patches actually increase the utilization
> stolen area on VLV by allocating User created frame buffers
> (only X tiled).
> These changes proved especially useful for Android BYT products,
> which had smaller RAM(1GB), where it enabled playback of most
> of the available 3D games/Apps.
>
> Akash Goel (7):
> drm/i915: Fix the offset issue for the stolen GEM objects
> drm/i915: Resolving the memory region conflict for Stolen area
> drm/i915/vlv: Not reallocating VLV PCTX upon every suspend/resume
> drm/i915: Added an identifier for User frame buffers to Gem obj
> structure
> drm/i915/vlv: Increase the utilization of stolen memory on VLV.
> drm/i915/vlv: Clear out contents of Frame buffer allocations from
> Stolen area
> drm/i915/vlv: Use Blitter Engine to clear out contents of Stolen frame
> buffers
>
> drivers/gpu/drm/i915/i915_drv.h | 6 +
> drivers/gpu/drm/i915/i915_gem.c | 21 +++
> drivers/gpu/drm/i915/i915_gem_stolen.c | 246 ++++++++++++++++++++++++++++++++-
> drivers/gpu/drm/i915/intel_display.c | 2 +
> drivers/gpu/drm/i915/intel_pm.c | 9 +-
> 5 files changed, 275 insertions(+), 9 deletions(-)
>
> --
> 1.8.5.2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
prev parent reply other threads:[~2014-01-09 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 5:29 [PATCH 0/7] Increase the utilization of Stolen area on VLV akash.goel
2014-01-09 8:30 ` Jani Nikula [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=87a9f5blra.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=akash.goel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox