From: Prarit Bhargava <prarit@redhat.com>
To: Len Brown <lenb@kernel.org>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] turbostat: Running on virtual machine is not supported
Date: Fri, 28 Jul 2017 07:54:27 -0400 [thread overview]
Message-ID: <8aa1f7ec-1d21-f027-f4c4-7c3d8e88b8d2@redhat.com> (raw)
In-Reply-To: <CAJvTdKmZqPkvUrgEJitYrBv7EJzpemLjN-nfYUnT3b127LNSQA@mail.gmail.com>
On 07/26/2017 11:09 PM, Len Brown wrote:
> Henrique,
>
> I like your suggestion, thanks!
>
> BTW. let's discuss (and patch) turbostat on linux-pm, rather than on lkml.
>
> thanks,
> -Len
>
>
> On Tue, Jul 25, 2017 at 11:59 AM, Henrique de Moraes Holschuh
> <hmh@hmh.eng.br> wrote:
>> On Tue, 25 Jul 2017, Prarit Bhargava wrote:
>>> A common way of determining if the system is a virtual machine is to
>>> search /proc/cpuinfo flags entry for "hypervisor". turbostat must output
>>> a proper error message when found.
>>
>> Maybe you could output that message only if it fails to both use
>> /dev/msr and perf *and* it is under a virtual machine? That would have
>> better forward compatibility, maybe someday /dev/msr or perf will work
>> inside a VM for what turbostat needs...
To answer Len's previous question: I was wrong in my description. perf does
work (mostly) under virt. So this would only be for the msr code. I'll post a
v2 to linux-pm, and take Henrique's suggestion to only trigger on an msr read
failure.
P.
>>
>> --
>> Henrique Holschuh
>
>
>
next parent reply other threads:[~2017-07-28 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1500987324-507-1-git-send-email-prarit@redhat.com>
[not found] ` <20170725155911.ihtjkz5cuwdpwoxp@khazad-dum.debian.net>
[not found] ` <CAJvTdKmZqPkvUrgEJitYrBv7EJzpemLjN-nfYUnT3b127LNSQA@mail.gmail.com>
2017-07-28 11:54 ` Prarit Bhargava [this message]
2017-08-05 6:50 ` [PATCH] turbostat: Running on virtual machine is not supported Len Brown
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=8aa1f7ec-1d21-f027-f4c4-7c3d8e88b8d2@redhat.com \
--to=prarit@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).