From: "H. Peter Anvin" <hpa@zytor.com>
To: David Rientjes <rientjes@google.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Yinghai Lu <yinghai@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: tidy e820 output
Date: Wed, 22 Sep 2010 15:50:03 -0700 [thread overview]
Message-ID: <4C9A881B.9010309@zytor.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1009221541350.22070@chino.kir.corp.google.com>
On 09/22/2010 03:46 PM, David Rientjes wrote:
> On Wed, 22 Sep 2010, H. Peter Anvin 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.
>>
>
> This patch is going to break our userspace parsing scripts if you change
> the output format. Admittedly, we're probably one of the few users who
> actually parses this output, but we do have reasons to do it for our
> firmware. If there was some improvement being introduced here, we'd
> happily handle multiple regexs (we constantly add new patterns when new
> kernels are released), but I'm not seeing how this is better.
Kernel messages are not an ABI or API.
The user space API for this stuff is /sys/firmware/memmap.
-hpa
next prev parent reply other threads:[~2010-09-22 22:50 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
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 [this message]
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=4C9A881B.9010309@zytor.com \
--to=hpa@zytor.com \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@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.