From: Pavel Machek <pavel@suse.cz>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <andi@firstfloor.org>,
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: Sun, 14 Sep 2008 13:22:22 +0200 [thread overview]
Message-ID: <20080914112222.GA3956@ucw.cz> (raw)
In-Reply-To: <alpine.LFD.1.10.0809122313440.13819@apollo.tec.linutronix.de>
On Fri 2008-09-12 23:19:21, Thomas Gleixner wrote:
> On Fri, 12 Sep 2008, Andi Kleen wrote:
> > "Yinghai Lu" <yhlu.kernel@gmail.com> writes:
> > >
> > > to see how wrong could be set by BIOS.
> >
> > Just dump it from user space then. There are plenty of tools
> > to access ACPI tables.
>
> 1.) what guarantees that we reach user space ?
We can dump in *any* kernel.
> 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.
Ooh, 'lets dump more junk at everyone, typing commands is hard' :-(.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-09-14 11:41 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
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 [this message]
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=20080914112222.GA3956@ucw.cz \
--to=pavel@suse.cz \
--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