lkml.org 
[lkml]   [2020]   [Jun]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH] Ability to read the MKTME status from userspace
Date

> On Jun 19, 2020, at 9:17 AM, Borislav Petkov <bp@alien8.de> wrote:
>
> On Fri, Jun 19, 2020 at 08:48:47AM -0700, Andy Lutomirski wrote:
>> Boris, it wouldn’t be totally crazy for cpuinfo to learn to
>> distinguish between “your platform has this feature but Linux
>> isn’t using it” and “your platform doesn’t have this feature
>> in the first place”. And I suppose there’s this extra silly state
>> “your platform has this feature, but your firmware didn’t enable
>> it”. This would be a big job.
>
> Well, I believe all the kernel can do is supply bits of information -
> just like MSRs - and depending on the settings of those bits, userspace
> can decide what the situation is. For example:
>
> bit 0 - CPUID support
> bit 1 - BIOS enabled
> bit 2 - quirk applied
> bit 3 - microcode fixes present
> ...
>
> and so on.
>

Indeed.

> It needs a proper definition though and userspace to say, yes, we want
> that and that is useful for us.

Maybe the right approach is to just keep this kind of use in mind for when we inevitably redo cpu features when Intel ships their hybrid Atom/Core machines.

>
> Where it ends up is then beside the point - /proc/cpuinfo,
> /sys/devices/system/cpu, whatever...
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette

\
 
 \ /
  Last update: 2020-06-19 18:29    [W:0.791 / U:0.408 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site