From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Prarit Bhargava <prarit@redhat.com>,
platform-driver-x86@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] intel-speed-select: Convert output to tables
Date: Mon, 23 Sep 2019 11:18:30 -0700 [thread overview]
Message-ID: <44b6fd7a71d9e9f7dd82ac51473f45b48fa4679d.camel@linux.intel.com> (raw)
In-Reply-To: <20190923131638.6668-1-prarit@redhat.com>
On Mon, 2019-09-23 at 09:16 -0400, Prarit Bhargava wrote:
> The turbo ratio limits and turbo frequencies add a large amount of
> lines to the output. The output can be truncated into human and
> machine readable tables to reduce the number of lines of output.
>
Unfortunately this breaks json output. The idea is that the software
should be able to parse json output using available json libraries and
consume information, without developing complex parser.
For example:
#intel-speed-select -o out.json -f json perf-profile info
Copy paste contents of out.json in any online json editor/tools, itshouldn't give error.
Thanks,
Srinivas
> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
> Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
>
> Prarit Bhargava (2):
> intel-speed-select: Display turbo-ratio-limits as a table
> intel-speed-select: Display turbo frequencies in a table
>
> .../x86/intel-speed-select/isst-display.c | 196 +++++++++-------
> --
> 1 file changed, 94 insertions(+), 102 deletions(-)
>
prev parent reply other threads:[~2019-09-23 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 13:16 Prarit Bhargava
2019-09-23 13:16 ` [PATCH 1/2] intel-speed-select: Display turbo-ratio-limits as a table Prarit Bhargava
2019-09-23 13:16 ` [PATCH 2/2] intel-speed-select: Display turbo frequencies in " Prarit Bhargava
2019-09-23 18:18 ` Srinivas Pandruvada [this message]
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=44b6fd7a71d9e9f7dd82ac51473f45b48fa4679d.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=prarit@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome