From: Arjan van de Ven <arjan at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] [PATCH] Do not exit on MSR read errors
Date: Mon, 11 May 2015 09:54:23 -0700 [thread overview]
Message-ID: <5550DEBF.6000207@linux.intel.com> (raw)
In-Reply-To: 1009270194.15661933.1431362984315.JavaMail.zimbra@redhat.com
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
On 5/11/2015 9:49 AM, Jaroslav Skarvada wrote:
> Hi,
>
> it seems there are virtual environments not correctly implementing the MSR
> (e.g. VirtualBox bug: https://www.virtualbox.org/ticket/14099) or not implementing
> it at all (e.g. KVM). PowerTOP just exits in such environments and cannot run.
>
> The proposed patch makes PowerTOP not to exit on MSR read errors, but still
> report them.
>
> Resending as attachment, because the previous e-mail has been probably blocked
> somewhere
>
Hi,
I have a slightly different patch in a local repo, but it needed a command line option
so I didn't sent it upstream yet.
the solution you have makes the app not crash, but it's really not the right thing.
the reason is that the statistics code still uses the "native intel msr" model,
so it gets all zeroes... it should use "just trust the kernel" model instead.
- if (strcmp(vendor, "GenuineIntel") == 0)
+ if (strcmp(vendor, "GenuineIntel") == 0 && !broken_msrs)
something like that in src/cpu/cpu.cpp (3x) is needed instead....
but today the msr logic runs after this code, not before, so I have not yet found
a good way to set the broken_msrs variable for the case in question
next reply other threads:[~2015-05-11 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 16:54 Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-16 19:31 [Powertop] [PATCH] Do not exit on MSR read errors Arjan van de Ven
2015-09-16 19:19 Alexandra Yates
2015-05-11 16:49 Jaroslav Skarvada
2015-05-11 14:32
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=5550DEBF.6000207@linux.intel.com \
--to=powertop@lists.01.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.