From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: Robert Elliott <elliott@hpe.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
linux-efi@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] x86/efi: print size and base in binary units in efi_print_memmap
Date: Fri, 8 Jan 2016 18:39:28 +0200 [thread overview]
Message-ID: <CAHp75VcJ_gDs-Y3SO2Z7BRqPCwKXntBiW6UDF38Di5m5_HszWQ@mail.gmail.com> (raw)
In-Reply-To: <20160108121921.GI2532@codeblueprint.co.uk>
On Fri, Jan 8, 2016 at 2:19 PM, Matt Fleming <matt@codeblueprint.co.uk> wrote:
> On Sun, 27 Dec, at 04:35:12PM, Andy Shevchenko wrote:
>> On Mon, Dec 21, 2015 at 6:16 PM, Matt Fleming <matt@codeblueprint.co.uk> wrote:
>> >> diff --git a/arch/x86/platform/efi/efi.c b/arch/x86/platform/efi/efi.c
>> >> index 635a955..030ba91 100644
>> >> --- a/arch/x86/platform/efi/efi.c
>> >> +++ b/arch/x86/platform/efi/efi.c
>> >> @@ -222,6 +222,25 @@ int __init efi_memblock_x86_reserve_range(void)
>> >> return 0;
>> >> }
>> >>
>> >> +char * __init efi_size_format(char *buf, size_t size, u64 bytes)
>> >> +{
>> >> + if (!bytes || (bytes & 0x3ff))
>> >> + snprintf(buf, size, "%llu B", bytes);
>> >> + else if (bytes & 0xfffff)
>> >> + snprintf(buf, size, "%llu KiB", bytes >> 10);
>> >> + else if (bytes & 0x3fffffff)
>> >> + snprintf(buf, size, "%llu MiB", bytes >> 20);
>> >> + else if (bytes & 0xffffffffff)
>> >> + snprintf(buf, size, "%llu GiB", bytes >> 30);
>> >> + else if (bytes & 0x3ffffffffffff)
>> >> + snprintf(buf, size, "%llu TiB", bytes >> 40);
>> >> + else if (bytes & 0xfffffffffffffff)
>> >> + snprintf(buf, size, "%llu PiB", bytes >> 50);
>> >> + else
>> >> + snprintf(buf, size, "%llu EiB", bytes >> 60);
>> >> + return buf;
>>
>> For me it looks like ffs with name in the table can be used.
>
> Could you provide a patch?
I will prepare something this weekend, or latest next week.
I suppose I can apply Robert's one on top of your efi/next and update it, right?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2016-01-08 16:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 1:28 Robert Elliott
2015-12-18 1:28 ` [PATCH 1/4] x86/efi: show actual ending addresses in efi_print_memmap Robert Elliott
2015-12-21 15:50 ` Matt Fleming
2015-12-21 16:06 ` Matt Fleming
2015-12-22 20:08 ` Elliott, Robert (Persistent Memory)
2015-12-23 12:44 ` Matt Fleming
2015-12-21 16:44 ` Elliott, Robert (Persistent Memory)
2015-12-23 12:47 ` Matt Fleming
2015-12-24 1:07 ` [PATCH v2 " Robert Elliott
2016-01-08 12:04 ` Matt Fleming
2015-12-18 1:28 ` [PATCH 2/4] efi: add NV memory attribute Robert Elliott
2015-12-21 15:54 ` Matt Fleming
2015-12-18 1:28 ` [PATCH 3/4] efi: add Persistent Memory type name Robert Elliott
2016-01-08 12:20 ` Matt Fleming
2015-12-18 1:28 ` [PATCH 4/4] x86/efi: print size and base in binary units in efi_print_memmap Robert Elliott
2015-12-21 16:16 ` Matt Fleming
2015-12-23 0:11 ` Elliott, Robert (Persistent Memory)
2015-12-23 15:52 ` Matt Fleming
2015-12-27 14:35 ` Andy Shevchenko
2016-01-08 12:19 ` Matt Fleming
2016-01-08 16:38 ` Elliott, Robert (Persistent Memory)
2016-01-08 16:44 ` Andy Shevchenko
2016-01-08 16:39 ` Andy Shevchenko [this message]
2016-01-11 14:09 ` Matt Fleming
2016-01-12 13:17 ` 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=CAHp75VcJ_gDs-Y3SO2Z7BRqPCwKXntBiW6UDF38Di5m5_HszWQ@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=elliott@hpe.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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).