linux-kernel - Re: [GIT PULL] iBFT features for v2.6.36

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]

Message-ID: <4C572A13.4010303@zytor.com>
Date:	Mon, 02 Aug 2010 13:26:59 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Konrad Rzeszutek Wilk <konrad@...nel.org>
CC:	Konrad Rzeszutek <konrad@...a.kernel.org>,
	torvalds@...ux-foundation.org, James.Bottomley@...e.de,
	linux-kernel@...r.kernel.org, pjones@...hat.com, lenb@...nel.org,
	michaelc@...wisc.edu
Subject: Re: [GIT PULL] iBFT features for v2.6.36

On 08/02/2010 12:52 PM, Konrad Rzeszutek Wilk wrote:
>>
>> Unfortunately, we're increasingly seeing a proliferation of this kind of
>> nonstandard ACPI tables, because it is difficult to add data to ACPI at
> 
> Keep in mind that iBFT is now a standard (woot!)
> 

Yes, but the discovery method is ad hoc, as opposed to the standard ACPI
mechanisms.

>> runtime.  gPXE creates an aBFT table for AoE and sBFT for SRP, and
>> memdisk uses mBFT for MEMDISK at the moment.
> 
> Oh man, didn't know those existed at all.
>>
>> It would be good to have some kind of common structure framework for these.
> 
> I need to grok those tables some more to figure out what they all do.

More or less the same thing as iBFT, but for AoE, SRP, or in-memory disk.

	-hpa
--
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/