On Wed, Jan 07, 2015 at 05:27:41PM +0000, Mark Brown wrote: > On Wed, Jan 07, 2015 at 02:06:28PM +0100, Arnd Bergmann wrote: > > On Wednesday 07 January 2015 11:50:39 Catalin Marinas wrote: > > > > From what I gathered so far, the main reason for _some_ vendors is not > > > support for "other" OS but actually features that ACPI has and DT > > > doesn't (like AML; I deliberately ignore statements like "industry > > > standard"). _If_ such reasons are sound, maybe they have a case for > > > ACPI-only machines targeted primarily at Linux. > > > What I got from the replies from HP, Huawei and from earlier discussions > > with Jon is that they all hope to get to the point of relying on AML > > alone to bridge the differences between SoC families. However, I don't > > see that happening with the limited hardware compatibility that the > > existing SBSA provides: > > I tend to agree with you that it's an overreach to think that this is > going to completely abstract away the differences between SoCs from > different vendors without substantial further standardization work. > However it does seem reasonable to expect that features like AML are > going to be more successful in handling board differences and > incremental revisions of SoCs - things like interactions with system > power controllers for example. That seems like a useful win in and of > itself, and one that's worth supporting. This piqued my interest, so I did a little research and found the following to describe AML (second para under "What does this mean?") http://community.arm.com/groups/processors/blog/2014/05/01/let-s-talk-acpi-for-servers iiuc, AML are basically drivers for some low-level functions provided as binary blobs via the ACPI tables. How does this work in a trusted boot scenario? Can the ACPI tables, and these binary blobs with it, be updated from userspace? If so, is there an authentication mechanism (including for non-secure boot scenarios)? One of the reasons I've really enjoyed working with ARM platforms and DT is the absence of this type of 'feature'. I honestly don't care whether the kernel gets the board configuration info from DT or ACPI or FOO, as long as we can avoid the security mistakes of the past: http://www.spiegel.de/international/world/catalog-reveals-nsa-has-back-doors-for-numerous-devices-a-940994.html """ ... The ANT developers have a clear preference for planting their malicious code in so-called BIOS, software located on a computer's motherboard that is the first thing to load when a computer is turned on. This has a number of valuable advantages: an infected PC or server appears to be functioning normally, so the infection remains invisible to virus protection and other security programs. And even if the hard drive of an infected computer has been completely erased and a new operating system is installed, the ANT malware can continue to function and ensures that new spyware can once again be loaded onto what is presumed to be a clean computer. ... """ I'm not advocating "throw out AML and ACPI with it!", rather I'd like to see a serious, open, discussion about the security implications of a convenience feature such as AML. And wrt the kernel, we should ensure we can always provide a fallback for users who prefer not to trust the binary blobs. Which shouldn't be too difficult as we aren't dependent on AML or similar atm. thx, Jason. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
