From: Matt Keenan <tank.en.mate@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Yinghai Lu <yhlu.kernel@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
mingo@elte.hu, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] apci: dump slit
Date: Fri, 12 Sep 2008 22:41:56 +0100 [thread overview]
Message-ID: <1221255716.11711.42.camel@bazbox> (raw)
In-Reply-To: <20080912213053.GR7714@one.firstfloor.org>
On Fri, 2008-09-12 at 23:30 +0200, Andi Kleen wrote:
> > 1.) what guarantees that we reach user space ?
>
> Broken SLITs don't prevent booting.
>
> > 2) If it is _valuable_ information which we can gather via kernel
> > output, then it is much more conveniant than asking the user to type
> > whatevercryptictoolcommandline and provide the output.
>
> Yes excellent point. Should we dump the complete ACPI tables?
> Do you prefer hexdump or do we need a ASL disassembler?
> Also complete SMBIOS? Also the legacy mptables of course too.
> And all the EFI methods. Ideally a disassembly of the complete BIOS.
> Did I miss anything?
>
Harsh... but harsh.
Matt
next prev parent reply other threads:[~2008-09-12 21:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 18:17 [PATCH] apci: dump slit Yinghai Lu
2008-09-12 19:20 ` Andrew Morton
2008-09-12 19:29 ` Yinghai Lu
2008-09-12 20:13 ` H. Peter Anvin
2008-09-12 21:17 ` Andi Kleen
2008-09-12 21:44 ` Thomas Gleixner
2008-09-12 21:11 ` Andi Kleen
2008-09-12 21:19 ` Thomas Gleixner
2008-09-12 21:30 ` Andi Kleen
2008-09-12 21:41 ` Matt Keenan [this message]
2008-09-12 21:49 ` Thomas Gleixner
2008-09-12 22:14 ` Andi Kleen
2008-09-12 21:54 ` Yinghai Lu
2008-09-12 22:29 ` Andi Kleen
2008-09-14 11:22 ` Pavel Machek
2008-09-14 12:26 ` Ingo Molnar
2008-09-14 15:59 ` Pavel Machek
2008-09-14 16:00 ` Pavel Machek
2008-09-14 16:04 ` Ingo Molnar
2008-09-14 18:13 ` Yinghai Lu
2008-09-18 18:26 ` Andi Kleen
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=1221255716.11711.42.camel@bazbox \
--to=tank.en.mate@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/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