From: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, akash.goel@intel.com
Subject: Re: [PATCH 11/11] drm/i915: Extend GET_APERTURE ioctl to report available map space
Date: Tue, 07 Jun 2016 14:22:28 +0530 [thread overview]
Message-ID: <1465289548.23549.11.camel@ankitprasad-desktop> (raw)
In-Reply-To: <574EB995.7070309@linux.intel.com>
On Wed, 2016-06-01 at 11:31 +0100, Tvrtko Ursulin wrote:
> On 31/05/16 07:19, ankitprasad.r.sharma@intel.com wrote:
> > From: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
.
.
.
> > +
> > +void i915_gem_stolen_size_info(struct drm_i915_private *dev_priv,
> > + uint64_t *stolen_free,
> > + uint64_t *stolen_largest)
> > +{
> > + struct drm_mm *mm = &dev_priv->mm.stolen;
> > + struct drm_mm_node *hole;
> > + uint64_t hole_size, hole_start, hole_end, largest_hole = 0;
> > + uint64_t total_free = 0;
> > +
> > + if (dev_priv->mm.volatile_stolen) {
> > + *stolen_free = 0;
> > + *stolen_largest = 0;
> > + return;
> > + }
>
> Is it worth having this special case? I am assuming the list below will
> always be empty in the volatile_stolen case?
FBC uses this space to store the compressed framebuffer, so the list may
not be empty if volatile_stolen case is true.
Thanks,
Ankit
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-07 9:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 6:19 [PATCH v20 00/11] Support for creating/using Stolen memory backed objects ankitprasad.r.sharma
2016-05-31 6:19 ` [PATCH 01/11] drm/i915: Add support for mapping an object page by page ankitprasad.r.sharma
2016-06-02 22:28 ` Chris Wilson
2016-05-31 6:19 ` [PATCH 02/11] drm/i915: Introduce i915_gem_object_get_dma_address() ankitprasad.r.sharma
2016-05-31 6:19 ` [PATCH 03/11] drm/i915: Use insert_page for pwrite_fast ankitprasad.r.sharma
2016-05-31 6:19 ` [PATCH 04/11] drm/i915: Clearing buffer objects via CPU/GTT ankitprasad.r.sharma
2016-05-31 6:19 ` [PATCH 05/11] drm/i915: Support for creating Stolen memory backed objects ankitprasad.r.sharma
2016-05-31 6:19 ` [PATCH 06/11] drm/i915: Propagating correct error codes to the userspace ankitprasad.r.sharma
2016-05-31 6:19 ` [PATCH 07/11] drm/i915: Add support for stealing purgable stolen pages ankitprasad.r.sharma
2016-05-31 6:19 ` [PATCH 08/11] drm/i915: Support for pread/pwrite from/to non shmem backed objects ankitprasad.r.sharma
2016-05-31 6:19 ` [PATCH 09/11] drm/i915: Migrate stolen objects before hibernation ankitprasad.r.sharma
2016-05-31 6:19 ` [PATCH 10/11] drm/i915: Disable use of stolen area by User when Intel RST is present ankitprasad.r.sharma
2016-05-31 6:19 ` [PATCH 11/11] drm/i915: Extend GET_APERTURE ioctl to report available map space ankitprasad.r.sharma
2016-06-01 10:31 ` Tvrtko Ursulin
2016-06-07 8:52 ` Ankitprasad Sharma [this message]
2016-06-01 12:11 ` Emil Velikov
2016-06-01 12:31 ` Emil Velikov
2016-05-31 11:05 ` ✗ Ro.CI.BAT: failure for Support for creating/using Stolen memory backed objects (rev15) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2016-06-08 9:26 [PATCH v21 00/11] Support for creating/using Stolen memory backed objects ankitprasad.r.sharma
2016-06-08 9:26 ` [PATCH 11/11] drm/i915: Extend GET_APERTURE ioctl to report available map space ankitprasad.r.sharma
2016-06-08 12:20 [PATCH v22 00/11] Support for creating/using Stolen memory backed objects ankitprasad.r.sharma
2016-06-08 12:20 ` [PATCH 11/11] drm/i915: Extend GET_APERTURE ioctl to report available map space ankitprasad.r.sharma
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=1465289548.23549.11.camel@ankitprasad-desktop \
--to=ankitprasad.r.sharma@intel.com \
--cc=akash.goel@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.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;
as well as URLs for NNTP newsgroup(s).