mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ioe-lkml@rameria.de>
To: "Dave Airlie" <airlied@gmail.com>
Cc: "Greg KH" <greg@kroah.com>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>,
	"Thomas Hellstr?m" <thomas@tungstengraphics.com>,
	"Jesse Barnes" <jbarnes@virtuousgeek.org>,
	"Eric Anholt" <eric@anholt.net>
Subject: Re: [RFC] [PATCH] DRM TTM Memory Manager patch
Date: Wed, 2 May 2007 00:36:36 +0200	[thread overview]
Message-ID: <200705020036.38322.ioe-lkml@rameria.de> (raw)
In-Reply-To: <21d7e9970704301610u5d5132uc282ac697c9df2be@mail.gmail.com>

On Tuesday 01 May 2007, Dave Airlie wrote:
> >   - what's with the /proc interface?  Don't add new proc code for
> >     non-process related things.  This should all go into sysfs
> >     somewhere.  And yes, I know /proc/dri/ is there today, but don't add
> >     new stuff please.
> 
> Well we should move all that stuff to sysfs, but we have all the
> infrastructure for publishing this stuff under /proc/dri and adding
> new files doesn't take a major amount, as much as I appreciate sysfs,
> it isn't suitable for this sort of information dump, the whole one
> value per file is quite useless to provide this sort of information
> which is uni-directional for users to send to us for debugging without
> have to install some special tool to join all the values into one
> place.. and I don't think drmfs is the answer either... or maybe it
> is....

Ok, what about debugfs then? If it is just for debugging blobs -> debugfs,
if it is crucial for operation -> sysfs and representation of one value 
per file.


Regards

Ingo Oeser

  parent reply	other threads:[~2007-05-01 22:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26  6:55 Dave Airlie
2007-04-27 16:39 ` Greg KH
2007-04-30 23:10   ` Dave Airlie
2007-04-30 23:50     ` Dave Jones
2007-05-01  0:10     ` Thomas Hellström
2007-05-01 22:36     ` Ingo Oeser [this message]
2007-05-02  3:59       ` Greg KH
2007-05-02 20:21 ` Eric Anholt
2007-05-02 23:01   ` Thomas Hellström
2007-05-04  4:07     ` Keith Packard
2007-05-04  8:07       ` Thomas Hellström
2007-05-04  8:49         ` Jerome Glisse
2007-05-04  9:40           ` Jerome Glisse
2007-05-04 15:28             ` Keith Packard
2007-05-04 11:03           ` Thomas Hellström
2007-05-04 11:57             ` Jerome Glisse
2007-05-04 12:32               ` Thomas Hellström
2007-05-04 12:52                 ` Jerome Glisse
2007-05-04 15:32                 ` Keith Packard
2007-05-04 15:15         ` Keith Packard
2007-05-04 15:57           ` Keith Whitwell
2007-05-04 16:26             ` Keith Packard

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=200705020036.38322.ioe-lkml@rameria.de \
    --to=ioe-lkml@rameria.de \
    --cc=airlied@gmail.com \
    --cc=eric@anholt.net \
    --cc=greg@kroah.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@tungstengraphics.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

all inboxes | Powered by JetHome®