On Sat, Mar 22, 2014 at 11:13:17AM -0700, Ben Widawsky wrote:
> On Thu, Mar 20, 2014 at 12:08:00PM +, Chris Wilson wrote:
> > On Thu, Mar 20, 2014 at 11:57:42AM +, Chris Wilson wrote:
> > > static void gen6_ppgtt_info(struct seq_file *m, struct drm_device *dev,
> > > bool verbose)
> > > @
On Thu, Mar 20, 2014 at 12:08:00PM +, Chris Wilson wrote:
> On Thu, Mar 20, 2014 at 11:57:42AM +, Chris Wilson wrote:
> > static void gen6_ppgtt_info(struct seq_file *m, struct drm_device *dev,
> > bool verbose)
> > @@ -1838,14 +1841,11 @@ static void gen6_ppgtt_info(struct seq_file *m,
On Thu, Mar 20, 2014 at 11:57:42AM +, Chris Wilson wrote:
> static void gen6_ppgtt_info(struct seq_file *m, struct drm_device *dev, bool
> verbose)
> @@ -1838,14 +1841,11 @@ static void gen6_ppgtt_info(struct seq_file *m,
> struct drm_device *dev, bool ver
>
> list_for_each_entry_rev
On Mon, Mar 17, 2014 at 10:48:33PM -0700, Ben Widawsky wrote:
> There often is not enough memory to dump the full contents of the PPGTT.
> As a temporary bandage, to continue getting valuable basic PPGTT info,
> wrap the dangerous, memory hungry part inside of a new verbose version
> of the debugfs
There often is not enough memory to dump the full contents of the PPGTT.
As a temporary bandage, to continue getting valuable basic PPGTT info,
wrap the dangerous, memory hungry part inside of a new verbose version
of the debugfs file.
Also while here we can split out the ppgtt print function so i
