All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	Ben Skeggs <bskeggs@redhat.com>, Greg KH <greg@kroah.com>,
	Alexandre Courbot <acourbot@nvidia.com>,
	David Airlie <airlied@linux.ie>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: unparseable, undocumented /sys/class/drm/.../pstate
Date: Sat, 21 Jun 2014 20:50:51 +0200	[thread overview]
Message-ID: <20140621185051.GA25094@amd.pavel.ucw.cz> (raw)
In-Reply-To: <CAKb7UvhOCiBHcsB6a0qKBNsC3c9pmb=Wc7zucbBuP6vt-tx2eA@mail.gmail.com>

On Sat 2014-06-21 14:22:59, Ilia Mirkin wrote:
> On Sat, Jun 21, 2014 at 2:02 PM, Pavel Machek <pavel@ucw.cz> wrote:
> > Hi!
> >
> > AFAICT, pstate file will contain something like
> >
> > 07: core 100 MHz memory 123 MHz *
> > 08: core 100-200 MHz memory 123 MHz
> >
> > ...which does not look exactly like one-value-per-file, and I'm pretty
> > sure userspace will get it wrong if it tries to parse it. Plus, I
> > don't see required documentation in Documentation/ABI.
...
> 
> FTR, this file has been in place since 3.13, and there was a different
> file before it (performance_levels), with a comparable format since
> much earlier (definitely 3.8, probably earlier). I think it's meant
> a

According to the article, it is only starting to work now. I know
articles can be wrong, but I don't have that hardware... Sorry if it
is the case.

> lot more for people looking at it and echo'ing stuff to it to modify
> the levels (where supported), than for programs parsing it. Perhaps
> sysfs is the wrong place for this -- what is the right place? debugfs?

debugfs would work, yes.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Greg KH <greg@kroah.com>,
	kernel list <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	Ben Skeggs <bskeggs@redhat.com>
Subject: Re: unparseable, undocumented /sys/class/drm/.../pstate
Date: Sat, 21 Jun 2014 20:50:51 +0200	[thread overview]
Message-ID: <20140621185051.GA25094@amd.pavel.ucw.cz> (raw)
In-Reply-To: <CAKb7UvhOCiBHcsB6a0qKBNsC3c9pmb=Wc7zucbBuP6vt-tx2eA@mail.gmail.com>

On Sat 2014-06-21 14:22:59, Ilia Mirkin wrote:
> On Sat, Jun 21, 2014 at 2:02 PM, Pavel Machek <pavel@ucw.cz> wrote:
> > Hi!
> >
> > AFAICT, pstate file will contain something like
> >
> > 07: core 100 MHz memory 123 MHz *
> > 08: core 100-200 MHz memory 123 MHz
> >
> > ...which does not look exactly like one-value-per-file, and I'm pretty
> > sure userspace will get it wrong if it tries to parse it. Plus, I
> > don't see required documentation in Documentation/ABI.
...
> 
> FTR, this file has been in place since 3.13, and there was a different
> file before it (performance_levels), with a comparable format since
> much earlier (definitely 3.8, probably earlier). I think it's meant
> a

According to the article, it is only starting to work now. I know
articles can be wrong, but I don't have that hardware... Sorry if it
is the case.

> lot more for people looking at it and echo'ing stuff to it to modify
> the levels (where supported), than for programs parsing it. Perhaps
> sysfs is the wrong place for this -- what is the right place? debugfs?

debugfs would work, yes.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2014-06-21 18:50 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-21 18:02 unparseable, undocumented /sys/class/drm/.../pstate Pavel Machek
2014-06-21 18:22 ` Ilia Mirkin
2014-06-21 18:22   ` Ilia Mirkin
2014-06-21 18:50   ` Pavel Machek [this message]
2014-06-21 18:50     ` Pavel Machek
2014-06-21 19:34     ` Ilia Mirkin
2014-06-21 19:34       ` Ilia Mirkin
2014-06-21 19:45   ` Greg KH
2014-06-21 19:45     ` Greg KH
2014-06-23  2:12     ` Ilia Mirkin
2014-06-23  2:12       ` Ilia Mirkin
2014-06-23 13:02       ` Pavel Machek
2014-06-23 13:02         ` Pavel Machek
2014-06-23 13:29         ` Ilia Mirkin
2014-06-23 13:29           ` Ilia Mirkin
2014-06-23 20:15           ` Pavel Machek
2014-06-23 20:15             ` Pavel Machek
2014-06-23 20:18             ` Ilia Mirkin
2014-06-23 20:18               ` Ilia Mirkin
2014-06-23 20:26               ` Greg KH
2014-06-23 20:26                 ` Greg KH
2014-06-23 20:32                 ` Ilia Mirkin
2014-06-23 20:32                   ` Ilia Mirkin
2014-06-24  0:06                 ` Ben Skeggs
2014-06-24  0:06                   ` Ben Skeggs
2014-06-24 16:00                   ` Greg KH
2014-06-24 16:00                     ` Greg KH
2014-06-23 16:07       ` Greg KH
2014-06-23 16:07         ` Greg KH
2014-06-23 16:18         ` Ilia Mirkin
2014-06-23 16:18           ` Ilia Mirkin
2014-06-23 16:36           ` Greg KH
2014-06-23 16:36             ` Greg KH
2014-06-23 16:40             ` Ilia Mirkin
2014-06-23 16:40               ` Ilia Mirkin
2014-06-23 17:46               ` Martin Peres
2014-06-23 17:46                 ` Martin Peres
2014-06-23 17:56                 ` Ilia Mirkin
2014-06-23 17:56                   ` Ilia Mirkin
2014-06-23 18:00                   ` Martin Peres
2014-06-23 18:00                     ` Martin Peres
2014-06-23 18:05                     ` Ilia Mirkin
2014-06-23 18:05                       ` Ilia Mirkin
2014-06-23 18:09                 ` Greg KH
2014-06-23 18:09                   ` Greg KH
2014-06-23 18:08               ` Greg KH
2014-06-23 18:08                 ` Greg KH

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=20140621185051.GA25094@amd.pavel.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=acourbot@nvidia.com \
    --cc=airlied@linux.ie \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=greg@kroah.com \
    --cc=imirkin@alum.mit.edu \
    --cc=linux-kernel@vger.kernel.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 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.