qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] hw/misc: applesmc: use host osk as default on macs


From: Gabriel L. Somlo
Subject: Re: [PATCH] hw/misc: applesmc: use host osk as default on macs
Date: Mon, 11 Oct 2021 09:19:10 -0400

FWIW, there's an applesmc driver in the Linux kernel, and it exposes
many of the keys and values stored on the chip under
/sys/devices/platform/applesmc.768 (or at least it *used* to back when
I last checked).

My idea at the time was to get this driver to also expose the value of
OSK0,1, so that userspace programs (like e.g. qemu) could read and use
the values hardcoded in hardware without needing to hardcode them
themselves in software.

It went nowhere at the time (the hwmon maintainer kept insisting that
"since it's a constant why don't you just hardcode it", and round and
round we went until I walked away:

https://lore.kernel.org/lkml/20121210222313.GF2097@hedwig.ini.cmu.edu/

Given *this* conversation, it might be worth someone's effort to try
that approach again. IMO it's really the most efficient: have an
already existing applesmc driver in the hypervisor's kernel expose the
desired key values (it's whole job is to expose key values to
userspace in the first place). Then have userspace read that and use
it for whatever purposes (including populating guest-facing emulated
smc devices). Nobody has to use anyone's copyrighted code or strings
or whatever. If only the hwmon folks could be convinced this time
around :)

HTH,
--Gabriel

On Sun, Oct 10, 2021 at 06:22:04PM -0300, Pedro Tôrres wrote:
> AFAIK there’s no public documentation from Apple on how to read values from
> SMC.
> 
> But Amit Singh wrote a book, Mac OS X Internals, and one of the processes
> described on it is how to read OSK directly from SMC: https://web.archive.org/
> web/20190630050544/http://osxbook.com/book/bonus/chapter7/tpmdrmmyth/
> 
> This is actually referenced on VirtualBox’s source code as the base for their
> implementation: 
> https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Devices/
> EFI/DevSmc.cpp#L520
> 
> Additionally, there is the smcFanControl project, licensed under GPLv2, that
> performs reads and writes on SMC and have all information necessary to
> implement this feature on QEMU: https://github.com/hholtmann/smcFanControl
> 
> This project was used as base for the SMC in-tree driver for Linux and it’s
> referenced there: https://github.com/torvalds/linux/blob/master/drivers/hwmon/
> applesmc.c#L14
> 
> I think we would be safe using these sources as the base for our
> implementation, given that other huge GPL projects like Linux and VirtualBox
> have been using them for years.
> 
> Best regards,
> Pedro Tôrres
> 
> 
>     On Oct 10, 2021, at 4:25 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> 
> 
>     Can you instead provide documentation in English (pseudocode, tables of 
> the
>     structs, etc.)? That's the safest bet.
> 
>     Paolo
> 
>     El sáb., 9 oct. 2021 7:32, Pedro Tôrres <t0rr3sp3dr0@gmail.com> escribió:
> 
>         Hey Paolo and Phil,
> 
>         I understand you concerns regarding the license that Apple open-source
>         code is distributed.
> 
>         If I restart from scratch and implement this feature based only on
>         VirtualBox code, that is distributed under GPLv2, would it be fine?
> 
>         Best regards,
>         Pedro Tôrres
> 
> 
>             On Oct 8, 2021, at 3:54 PM, Paolo Bonzini <pbonzini@redhat.com>
>             wrote:
> 
> 
>             On 08/10/21 14:03, Phil Dennis-Jordan wrote:
> 
>                 1. Licensing
> 
>                 Given that the code it's heavily based on is copyright Apple
>                 Computer Inc., licensed under APSL, is it safe including it in
>                 qemu as is?
> 
>                 If the integrated code is going to be quite so "directly
>                 inspired" (down to the inconsistent struct definition style 
> and
>                 mixing unrelated constants in the same anonymous enum), 
> perhaps
>                 at minimum place it in its own isolated source file with
>                 appropriate notice?
> 
>            
>             Yeah, this should be reverted.
>            
>             Pedro, I understand that you stated it was "based on code from
>             Apple" but you also said (by including Signed-off-by) that
>            
>             ---
>             (a) The contribution was created in whole or in part by me and I
>                have the right to submit it under the open source license
>                indicated in the file; or
>            
>             (b) The contribution is based upon previous work that, to the best
>                of my knowledge, is covered under an appropriate open source
>                license and I have the right under that license to submit that
>                work with modifications, whether created in whole or in part
>                by me, under the same open source license (unless I am
>                permitted to submit under a different license), as indicated
>                in the file; or
>             ---
>            
>             and this is not true.
>            
>             Thanks very much,
>            
>             Paolo
>            
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]