All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Robert Elliott <elliott@hpe.com>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org,
	Brian Norris <computersforpeace@gmail.com>,
	Hariprasad S <hariprasad@chelsio.com>
Subject: Re: [PATCH v2 09/11] lib/vsprintf: use precision field with %pl[From[To]]
Date: Mon, 18 Jan 2016 23:21:07 +0100	[thread overview]
Message-ID: <87egdeedgs.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <1452810221-116505-10-git-send-email-andriy.shevchenko@linux.intel.com> (Andy Shevchenko's message of "Fri, 15 Jan 2016 00:23:39 +0200")

On Thu, Jan 14 2016, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:

> The precision field defines how many digits after period ('.') will be
> printed.

Yuck again.

Didn't you notice gcc barking at you?

warning: precision used with ‘%p’ gnu_printf format [-Wformat=]

So I don't think this will ever be used. 

> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>  Documentation/printk-formats.txt |  7 +++++++
>  lib/test_printf.c                | 29 +++++++++++++++++++++++++++++
>  lib/vsprintf.c                   | 20 +++++++++++++++++++-
>  3 files changed, 55 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/printk-formats.txt b/Documentation/printk-formats.txt
> index 3b41899..534407c 100644
> --- a/Documentation/printk-formats.txt
> +++ b/Documentation/printk-formats.txt
> @@ -295,11 +295,18 @@ unsigned long long value in human-readable form (with IEC binary prefix):
>  	%pl		1048575 B	(1048575)
>  	%plKM		1023 KiB	(1048575)
>  	%pl		1 MiB		(1048576)
> +	%.1plKM		1046527.9 MiB	(1097364144125)
>  	%plG		2 TiB		(2199023255552)
>  
>  	For printing given unsigned long long value in human-readable form with
>  	automatically choosen IEC binary prefix.
>  
> +	Precision, if passed, defines how many digits will be printed after
> +	period ('.'). In this case the biggest possible unit is used in the
> +	given range [From[To]]. The printed value isn't rounded anyhow.
> +
> +	For other use cases consider to call string_get_size().
> +
>  	Passed by reference.
>  
>  bitmap and its derivatives such as cpumask and nodemask:
> diff --git a/lib/test_printf.c b/lib/test_printf.c
> index ae35885..4a2e30b 100644
> --- a/lib/test_printf.c
> +++ b/lib/test_printf.c
> @@ -435,6 +435,30 @@ human_readable(void)
>  		{ .v = 1048575ULL,		.r = "1023 KiB" },
>  		{ .v = 1047552ULL,		.r = "1023 KiB" },
>  	};
> +	struct hr_test_data htdpl0KM[] = {
> +		{ .v = 1097364144128ULL,	.r = "1046528 MiB" },
> +		{ .v = 1097364144125ULL,	.r = "1046527 MiB" },
> +		{ .v = 1048578ULL,		.r = "1 MiB" },
> +		{ .v = 1048576ULL,		.r = "1 MiB" },
> +		{ .v = 1048575ULL,		.r = "1023 KiB" },
> +		{ .v = 1047552ULL,		.r = "1023 KiB" },
> +	};
> +	struct hr_test_data htdpl1KM[] = {
> +		{ .v = 1097364144128ULL,	.r = "1046528.0 MiB" },
> +		{ .v = 1097364144125ULL,	.r = "1046527.9 MiB" },
> +		{ .v = 1048578ULL,		.r = "1.0 MiB" },
> +		{ .v = 1048576ULL,		.r = "1.0 MiB" },
> +		{ .v = 1048575ULL,		.r = "1023.9 KiB" },
> +		{ .v = 1047552ULL,		.r = "1023.0 KiB" },
> +	};
> +	struct hr_test_data htdpl3KM[] = {
> +		{ .v = 1097364144128ULL,	.r = "1046528.000 MiB" },
> +		{ .v = 1097364144125ULL,	.r = "1046527.999 MiB" },
> +		{ .v = 1048578ULL,		.r = "1.000 MiB" },
> +		{ .v = 1048576ULL,		.r = "1.000 MiB" },
> +		{ .v = 1048575ULL,		.r = "1023.999 KiB" },
> +		{ .v = 1047552ULL,		.r = "1023.000 KiB" },
> +	};
>  	struct hr_test_array {
>  		const char *fmt;
>  		struct hr_test_data *data;
> @@ -446,6 +470,11 @@ human_readable(void)
>  		{ "%plKM",	htdplKM,	ARRAY_SIZE(htdplKM) },
>  		/* No reversed %pl[To[From]] order */
>  		{ "%plMK",	htdplM,		ARRAY_SIZE(htdplM) },
> +		{ "%.0plKM",	htdpl0KM,	ARRAY_SIZE(htdpl0KM) },
> +		{ "%.1plKM",	htdpl1KM,	ARRAY_SIZE(htdpl1KM) },
> +		{ "%.3plKM",	htdpl3KM,	ARRAY_SIZE(htdpl3KM) },
> +		/* For now precision is in range [0..3] */
> +		{ "%.4plKM",	htdplKM,	ARRAY_SIZE(htdplKM) },
>  	};
>  	unsigned int i, j;
>  
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
> index fbcb221..2dd86c9 100644
> --- a/lib/vsprintf.c
> +++ b/lib/vsprintf.c
> @@ -1327,7 +1327,9 @@ char *human_readable(char *buf, char *end, const void *addr,
>  			to = i;
>  	}
>  
> -	if (value)
> +	if (spec.precision >= 0 && spec.precision <= 3 && value)
> +		index = (fls64(value) - 1) / 10;
> +	else if (value)
>  		index = __ffs64(value) / 10;
>  	else
>  		index = 0;
> @@ -1336,6 +1338,22 @@ char *human_readable(char *buf, char *end, const void *addr,
>  	/* Print numeric part */
>  	buf = number(buf, end, value >> (index * 10), default_dec_spec);
>  
> +	/* Print precision part if asked */
> +	if (spec.precision > 0 && spec.precision <= 3 && index) {
> +		unsigned int remainder;
> +
> +		remainder = (value >> (index - 1) * 10) % 1024;
> +		for (i = 0; i < spec.precision; i++)
> +			remainder *= 10;
> +		remainder >>= 10;
> +
> +		/* Period... */
> +		buf = put_one_char(buf, end, '.');
> +
> +		/* ...and remainder part */
> +		buf = number(buf, end, remainder, spec);
> +	}
> +
>  	/* Space between numeric part and units */
>  	buf = put_one_char(buf, end, ' ');

  reply	other threads:[~2016-01-18 22:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 22:23 [PATCH v2 00/11] lib/vsprintf: refactor and introduce %pl specifier Andy Shevchenko
2016-01-14 22:23 ` [PATCH v2 01/11] lib/vsprintf: introduce put_one_char() for 3 line idiom Andy Shevchenko
2016-01-18 20:35   ` Rasmus Villemoes
2016-01-14 22:23 ` [PATCH v2 02/11] lib/vsprintf: make default_dec_spec global Andy Shevchenko
2016-01-18 20:38   ` Rasmus Villemoes
2016-01-14 22:23 ` [PATCH v2 03/11] lib/vsprintf: make default_str_spec global Andy Shevchenko
2016-01-14 22:23 ` [PATCH v2 04/11] lib/string_helpers: export string_units_{2,10} for others Andy Shevchenko
2016-01-14 22:23 ` [PATCH v2 05/11] lib/string_helpers: fix indentation in few places Andy Shevchenko
2016-01-14 22:23 ` [PATCH v2 06/11] lib/vsprintf: introduce %pl to print in human-readable form Andy Shevchenko
2016-01-15  3:04   ` Joe Perches
2016-01-18 20:57   ` Rasmus Villemoes
2016-01-21 21:13   ` H. Peter Anvin
2016-01-14 22:23 ` [PATCH v2 07/11] x86/efi: print size and base in binary units in efi_print_memmap Andy Shevchenko
2016-01-14 22:23 ` [PATCH v2 08/11] lib/vsprintf: allow range of prefix for %pl[From[To]] Andy Shevchenko
2016-01-18 21:40   ` Rasmus Villemoes
2016-01-14 22:23 ` [PATCH v2 09/11] lib/vsprintf: use precision field with %pl[From[To]] Andy Shevchenko
2016-01-18 22:21   ` Rasmus Villemoes [this message]
2016-01-14 22:23 ` [PATCH v2 10/11] cxgb4: print value in human-readable form via %.0plKM Andy Shevchenko
2016-01-14 22:23 ` [PATCH v2 11/11] pcmciamtd: " Andy Shevchenko
2016-01-21 12:51 ` [PATCH v2 00/11] lib/vsprintf: refactor and introduce %pl specifier Andy Shevchenko

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=87egdeedgs.fsf@rasmusvillemoes.dk \
    --to=linux@rasmusvillemoes.dk \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=computersforpeace@gmail.com \
    --cc=elliott@hpe.com \
    --cc=hariprasad@chelsio.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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.