From: "Michael H. Nguyen" <michael.h.nguyen@intel.com>
To: "Bloomfield, Jon" <jon.bloomfield@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v6 1/5] drm/i915: Implement a framework for batch buffer pools
Date: Wed, 10 Dec 2014 09:05:05 -0800 [thread overview]
Message-ID: <54887D41.1010405@intel.com> (raw)
In-Reply-To: <AD48BB7FB99B174FBCC69E228F58B3B61B0EEA4E@IRSMSX103.ger.corp.intel.com>
On 12/10/2014 08:41 AM, Bloomfield, Jon wrote:
> why do we take the batch_pool lock in i915_gem_batch_pool_info() ?
i915_gem_batch_pool_info() is a new debugfs entry while
print_batch_pool_stats() is just an internal fnc, called from the
debugfs entry i915_gem_object_info(). i915_gem_object_info() handles the
locks.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-12-10 17:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 22:33 [PATCH v6 0/5] Command parser batch buffer copy michael.h.nguyen
2014-12-08 22:33 ` [PATCH v6 1/5] drm/i915: Implement a framework for batch buffer pools michael.h.nguyen
2014-12-09 13:18 ` Daniel Vetter
2014-12-09 19:42 ` Michael H. Nguyen
2014-12-10 11:06 ` Bloomfield, Jon
2014-12-10 16:33 ` Michael H. Nguyen
2014-12-10 16:41 ` Bloomfield, Jon
2014-12-10 17:05 ` Michael H. Nguyen [this message]
2014-12-08 22:33 ` [PATCH v6 2/5] drm/i915: Use batch pools with the command parser michael.h.nguyen
2014-12-08 22:33 ` [PATCH v6 3/5] drm/i915: Use batch length instead of object size in " michael.h.nguyen
2014-12-08 22:33 ` [PATCH v6 4/5] drm/i915: Mark shadow batch buffers as purgeable michael.h.nguyen
2014-12-09 13:21 ` Daniel Vetter
2014-12-09 21:34 ` Michael H. Nguyen
2014-12-11 13:26 ` Bloomfield, Jon
2014-12-11 18:56 ` Michael H. Nguyen
2014-12-08 22:33 ` [PATCH v6 5/5] drm/i915: Tidy up execbuffer command parsing code michael.h.nguyen
2014-12-09 2:05 ` shuang.he
2014-12-09 13:22 ` Daniel Vetter
2014-12-09 21:35 ` Michael H. Nguyen
2014-12-11 13:49 ` Bloomfield, Jon
2014-12-11 18:56 ` Michael H. Nguyen
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=54887D41.1010405@intel.com \
--to=michael.h.nguyen@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jon.bloomfield@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 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.