linux-kernel - Re: [PATCH 01/34] System Firmware Interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 19 Jul 2011 10:05:44 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Prarit Bhargava <prarit@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/34] System Firmware Interface

On Mon, 18 Jul 2011 17:43:08 -0700
Andi Kleen <andi@...stfloor.org> wrote:

> Prarit Bhargava <prarit@...hat.com> writes:
> 
> Wow that's a cc list from hell. Cut down to linux-kernel.

Which meant I very nearly missed it so you very nearly missed your answer
8)

> > This patch introduces a general System Firmware interface to the kernel, called
> > sysfw.
> 
> Could you expand somewhat WHY you want this. What is wrong with the
> current code?

See the previous discussions

> As for user space access on x86 "dmidecode"/libdmi works for nearly everyone,
> doesn't it?

"on x86" (and on PC only generally)

There are three core problems

1.	DMI in this sense is basically an x86 PC class device hack
2.	It is obsoleted and at some point it'll vanish even on PC
3.	Every other platform without DMI would benefit from the
	interface being generic

So either we carry on hacking other interfaces (often more informative
ones) into our dmi glue, and trying to keep up the fakery for every case,
or we do what I should have done originally and made the interface a
generic way to query firmware/board information that can be extended
nicely.

We'll still need a spot of fakery for userspace I suspect.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/