All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: tidy e820 output
Date: Wed, 22 Sep 2010 14:07:00 -0700	[thread overview]
Message-ID: <4C9A6FF4.2060201@kernel.org> (raw)
In-Reply-To: <201009221311.19567.bjorn.helgaas@hp.com>

On 09/22/2010 12:11 PM, Bjorn Helgaas wrote:
> On Wednesday, September 22, 2010 12:58:36 pm H. Peter Anvin wrote:
>> On 09/22/2010 11:53 AM, Bjorn Helgaas wrote:
>>>
>>> It's true, they don't (well, everything below 4G still lines up, but
>>> not above that).  Do you like this any better?
>>>
>>
>> That's fine with me.  I don't mind the [mem ] bracket either if you
>> think it's useful.
> 
> I took out "[mem" because it made the "(reserved)" lines wider than
> 80 columns.  But maybe I should just remove the parens around the
> E820 type instead, like this:
> 
> commit d2338b08303439b23d4909eab3744b3f29f09874
> Author: Bjorn Helgaas <bjorn.helgaas@hp.com>
> Date:   Tue Sep 21 12:32:34 2010 -0600
> 
>     x86: tidy e820 output
>     
>     This tidies e820 output by adding an "e820" prefix and printing ranges
>     similarly to the way we print struct resource with %pR, e.g.:
>     
>         - BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
>         + BIOS-e820: [mem 0x0000000000000000-0x000000000009f3ff] usable
>     
>     Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
> 
> diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c
> index 0d6fc71..2bd464f 100644
> --- a/arch/x86/kernel/e820.c
> +++ b/arch/x86/kernel/e820.c
> @@ -108,7 +108,9 @@ static void __init __e820_add_region(struct e820map *e820x, u64 start, u64 size,
>  	int x = e820x->nr_map;
>  
>  	if (x >= ARRAY_SIZE(e820x->map)) {
> -		printk(KERN_ERR "Ooops! Too many entries in the memory map!\n");
> +		printk(KERN_ERR "e820: too many entries; ignoring [mem %#010llx-%#010llx]\n",
> +		       (unsigned long long) start,
> +		       (unsigned long long) (start + size - 1));
>  		return;
>  	}
>  
> @@ -123,29 +125,22 @@ void __init e820_add_region(u64 start, u64 size, int type)
>  	__e820_add_region(&e820, start, size, type);
>  }
>  
> -static void __init e820_print_type(u32 type)
> +static char * __init e820_type_name(u32 type)
>  {
>  	switch (type) {
>  	case E820_RAM:
>  	case E820_RESERVED_KERN:
> -		printk(KERN_CONT "(usable)");
> -		break;
> +		return "usable";
>  	case E820_RESERVED:
> -		printk(KERN_CONT "(reserved)");
> -		break;
> +		return "reserved";
>  	case E820_ACPI:
> -		printk(KERN_CONT "(ACPI data)");
> -		break;
> +		return "ACPI data";
>  	case E820_NVS:
> -		printk(KERN_CONT "(ACPI NVS)");
> -		break;
> +		return "ACPI NVS";
>  	case E820_UNUSABLE:
> -		printk(KERN_CONT "(unusable)");
> -		break;
> -	default:
> -		printk(KERN_CONT "type %u", type);
> -		break;
> +		return "unusable";
>  	}
> +	return "(unknown)";
>  }

type value?

Yinghai

  reply	other threads:[~2010-09-22 21:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 17:27 [PATCH] x86: tidy e820 output Bjorn Helgaas
2010-09-22 17:54 ` H. Peter Anvin
2010-09-22 18:20   ` Bjorn Helgaas
2010-09-22 18:27     ` H. Peter Anvin
2010-09-22 18:53       ` Bjorn Helgaas
2010-09-22 18:58         ` H. Peter Anvin
2010-09-22 19:11           ` Bjorn Helgaas
2010-09-22 21:07             ` Yinghai Lu [this message]
2010-09-22 21:22               ` Bjorn Helgaas
2010-09-22 21:29                 ` Yinghai Lu
2010-09-22 21:34                 ` H. Peter Anvin
2010-09-22 22:05                   ` Bjorn Helgaas
2010-09-22 22:07                     ` H. Peter Anvin
2010-09-22 22:46           ` David Rientjes
2010-09-22 22:50             ` H. Peter Anvin
2010-09-22 23:12               ` David Rientjes
2010-09-22 23:16                 ` H. Peter Anvin
2010-09-22 23:27                   ` David Rientjes

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=4C9A6FF4.2060201@kernel.org \
    --to=yinghai@kernel.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.