All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 37922] New: NV86: too high power usage.
Date: Sat,  4 Jun 2011 06:38:05 -0700 (PDT)	[thread overview]
Message-ID: <bug-37922-8800@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=37922

           Summary: NV86: too high power usage.
           Product: xorg
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: maximlevitsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


I want to track all the progress I made on reverse-engineering power-management
on my NV86 card.

First, the statistics that should give us the idea about what to expect.
(All measurements done using acpi counters, in more or less controlled
environment. 0% brightness, using vga console and X server running on other VT.
VGA console were running powertop).
The measurement is what appeared to be minimum value.
Wireless was on, and no special knobs to decrease power usage were applied
(like unloading the ethernet driver).

following suggestion of Emil Velikov I changed the vbios slightly so it shows 0
available power levels, thus nvidia driver wasn't able to reclock the card.
(unless I say otherwice)

no drivers loaded..........:  22.6W
nouveau....................:  22.6W
nouveau, pm level 0........:  20.9W

nvidia (no reclock)........:  19.4W
no driver + mmiotrace
replay of above............:  19.4W

nvidia + reclocking........:  15.8W


I was able to reduce the mmiotrace to very small list
and with it I can bring power level to 19.4 (or even less sometimes)
I will attach it here.
Note that trace consists of 6 parts. If I concat them, power usage seems to
increase. Removal of many commands of above traces also increases power usage a
bit, so the conclusion is that traces contain many many commands that each
turns down that or other part of the card.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-06-04 13:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-04 13:38 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-37922-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-06-04 13:39   ` [Bug 37922] NV86: too high power usage bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-04 13:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-04 13:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-04 13:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-04 13:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-04 13:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-04 17:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-08 18:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-29 14:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-29 14:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-29 17:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-30 21:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-01  7:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-03  3:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-03  3:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-03  3:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-04  1:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-04  1:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-04  2:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-04 23:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-04 23:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-05  0:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-09 22:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27 21:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-28  2:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-28 19:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-28 20:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-28 20:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-28 20:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-31  0:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-01-21 16:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-17  0:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-17  5:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-37922-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.