All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: kan.liang@linux.intel.com
Cc: acme@redhat.com, mingo@redhat.com, linux-kernel@vger.kernel.org,
	jolsa@redhat.com, namhyung@gmail.com, lgoncalv@redhat.com,
	ak@linux.intel.com
Subject: Re: [PATCH] perf stat: Add hint for SMI cost measurement
Date: Thu, 25 Apr 2019 08:39:10 +0200	[thread overview]
Message-ID: <20190425063910.GA85646@gmail.com> (raw)
In-Reply-To: <1556120792-35415-1-git-send-email-kan.liang@linux.intel.com>


* kan.liang@linux.intel.com <kan.liang@linux.intel.com> wrote:

> +static void smi_env_check(void)
> +{
> +	char *name;
> +	size_t len;
> +
> +	if (sysfs__read_str(CPUIDLE_CUR_DRV, &name, &len)) {
> +		pr_warning("Failed to check cstate status.\n");

What a meaningless message. What did we want to do, what happened, and 
why did it fail?

> +		return;
> +	}
> +
> +	if (strncmp(name, "none", 4)) {
> +		pr_warning("Cstate may cause drift between aperf and cycles. "
> +			   "Please completely disable cstate, "
> +			   "E.g. set idle=poll in grub\n");

Please keep user-visible strings in the same form that the user sees 
them, i.e. in a single line.

By doing that you'll also note a capitalization error.

Also what does 'Cstate may cause drift' mean? What aspect of cstates 
causes the drift - entering/exiting deeper cstates that are not C0? If so 
then say so.

Thanks,

	Ingo

  reply	other threads:[~2019-04-25  6:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 15:46 [PATCH] perf stat: Add hint for SMI cost measurement kan.liang
2019-04-25  6:39 ` Ingo Molnar [this message]
2019-04-25 13:14   ` Liang, Kan
2019-04-25 17:47     ` Ingo Molnar
2019-04-25 19:05       ` Liang, Kan

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=20190425063910.GA85646@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@linux.intel.com \
    --cc=lgoncalv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@gmail.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 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.