[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <94D0CD8314A33A4D9D801C0FE68B40295BF3BBD3@G9W0745.americas.hpqcorp.net>
Date: Mon, 25 Jan 2016 20:37:58 +0000
From: "Elliott, Robert (Persistent Memory)" <elliott@....com>
To: Andy Shevchenko <andy.shevchenko@...il.com>,
James Bottomley <James.Bottomley@...senpartnership.com>
CC: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Matt Fleming <matt@...eblueprint.co.uk>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H . Peter Anvin" <hpa@...or.com>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel @ vger . kernel . org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v3 3/4] x86/efi: print size in binary units in
efi_print_memmap
---
Robert Elliott, HPE Persistent Memory
> -----Original Message-----
> From: Andy Shevchenko [mailto:andy.shevchenko@...il.com]
> Sent: Monday, January 25, 2016 2:01 PM
> To: James Bottomley <James.Bottomley@...senpartnership.com>
> Cc: Elliott, Robert (Persistent Memory) <elliott@....com>; Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com>; Matt Fleming
> <matt@...eblueprint.co.uk>; Thomas Gleixner <tglx@...utronix.de>; Ingo
> Molnar <mingo@...hat.com>; H . Peter Anvin <hpa@...or.com>; linux-
> efi@...r.kernel.org; Rasmus Villemoes <linux@...musvillemoes.dk>; Andrew
> Morton <akpm@...ux-foundation.org>; linux-kernel @ vger . kernel . org
> <linux-kernel@...r.kernel.org>
> Subject: Re: [PATCH v3 3/4] x86/efi: print size in binary units in
> efi_print_memmap
>
> On Mon, Jan 25, 2016 at 9:45 PM, James Bottomley
> <James.Bottomley@...senpartnership.com> wrote:
> > On Mon, 2016-01-25 at 21:28 +0200, Andy Shevchenko wrote:
> >> On Mon, Jan 25, 2016 at 8:56 PM, James Bottomley
> >> <James.Bottomley@...senpartnership.com> wrote:
> >> > On Mon, 2016-01-25 at 18:02 +0000, Elliott, Robert (Persistent
> >> > Memory)
> >> > wrote:
> >>
> >> > Using ffs leads to precision runaway
> >>
> >> How exactly?!
> >
> > Off by one. A size of 0xffffffffffffffff prints 18446744073709551615 B
> > rather than 20 GiB.
>
> Because it's not a 20 GiB. It's exactly 20 GiB - 1 B.
>
> AFAIU, the intention was to show _exact_ size.
For the UEFI memory map, that was indeed my intention. I
don't want it silently round to "20 GiB". Even rounding
to "19.999 GiB" is imprecise.
Another option could be to use a "~" prefix for imperfect
values, like "~20 GiB". That would serve as a warning
that something's not quite right.
Powered by blists - more mailing lists