public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Prarit Bhargava <prarit@redhat.com>,
	Matt Fleming <matt@console-pimps.org>,
	Colin Ian King <colin.king@canonical.com>,
	linux-kernel@vger.kernel.org, lszubowi@redhat.com,
	Matt Fleming <matt.fleming@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, linux-efi@vger.kernel.org
Subject: Re: [PATCH] x86, efi: print debug values in Kib not MB
Date: Wed, 30 Jul 2014 21:58:21 +0200	[thread overview]
Message-ID: <20140730195821.GE10213@pd.tnic> (raw)
In-Reply-To: <53D92996.1050906@zytor.com>

On Wed, Jul 30, 2014 at 10:21:26AM -0700, H. Peter Anvin wrote:
> Arguably the exactness is available in the range...

... and the size too. FWIW, other region dumps don't even print size:

[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009e7ff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009e800-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
...

If we do that too for UEFI, we can certainly put an end to the
bikeshedding... provided everyone is tired of it by now. :-P

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-07-30 19:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 17:09 [PATCH] x86, efi: print debug values in Kib not MB Prarit Bhargava
2014-07-29 20:29 ` David Rientjes
2014-07-29 22:02   ` Joe Perches
2014-07-29 22:05     ` Prarit Bhargava
2014-07-29 22:05   ` Prarit Bhargava
2014-07-29 22:29 ` Borislav Petkov
2014-07-29 22:32   ` Prarit Bhargava
2014-07-29 22:36     ` Borislav Petkov
2014-07-29 22:42       ` David Rientjes
2014-07-29 23:01         ` Borislav Petkov
2014-07-29 23:03           ` Prarit Bhargava
2014-07-29 23:07         ` Joe Perches
2014-07-29 23:44           ` David Rientjes
2014-07-29 22:54       ` Prarit Bhargava
2014-07-30  3:25         ` Steven Noonan
2014-07-30 14:48   ` Matt Fleming
2014-07-30 15:05     ` Colin Ian King
2014-07-30 17:04       ` Prarit Bhargava
2014-07-30 17:10         ` Randy Dunlap
2014-07-30 17:21           ` H. Peter Anvin
2014-07-30 19:58             ` Borislav Petkov [this message]
2014-07-30 20:43               ` Randy Dunlap

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=20140730195821.GE10213@pd.tnic \
    --to=bp@alien8.de \
    --cc=colin.king@canonical.com \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lszubowi@redhat.com \
    --cc=matt.fleming@intel.com \
    --cc=matt@console-pimps.org \
    --cc=mingo@redhat.com \
    --cc=prarit@redhat.com \
    --cc=rdunlap@infradead.org \
    --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