AMD Plumbing Linux Support For Reading The CPU's Protected Processor Identification Number (PPIN)

[carewolf]

Randomizing what features the processor reports as "supported" is a great idea, totally not going to cause random breakage.

Devuan: doing useless and potential harmful shit because we don't know what stuff means.

What does what the processor supports have to do with its unique identifier? We are not talking about fingerprinting the CPU, but a specific unique fingerprint.

[starshipeleven]

What does what the processor supports have to do with its unique identifier? We are not talking about fingerprinting the CPU, but a specific unique fingerprint.

The guy I quoted said Devuan is randomizing CPUID, which is not an unique identifier, and reports model and features of the CPU.

[willmore]

The guy I quoted said Devuan is randomizing CPUID, which is not an unique identifier, and reports model and features of the CPU.

There is already a front door way of getting approved information like that in the form of /proc/cpuinfo. This back door attempt is not appreciated.

[starshipeleven]

There is already a front door way of getting approved information like that in the form of /proc/cpuinfo.

What the fuck? Where do you think /proc/cpuinfo takes most of that information? It comes from reading the result of CPUID instruction from the CPU, which as I said is NOT an unique identifier. See here for what CPUID reports https://en.wikipedia.org/wiki/CPUID
Doing without it is retarded, it means the programs have to run tests to identify the CPU model and supported features by trial and error, or target absolute bullshit lowest common denominator CPU feature set to avoid random crashing on systems that don't support a specific CPU instruction/feature.

[agd5f]

This feature is a benefit for datacenters as it allows techs to easily identify what component is needs to be replaced when it fails.

[willmore]

This feature is a benefit for datacenters as it allows techs to easily identify what component is needs to be replaced when it fails.

Yeah, because asset tagging has never been a thing, ever, so they needed this to solve an unsolved problem. No, wait....

[agd5f]

Yeah, because asset tagging has never been a thing, ever, so they needed this to solve an unsolved problem. No, wait....

Same difference, just built in.

[carewolf]

The guy I quoted said Devuan is randomizing CPUID, which is not an unique identifier, and reports model and features of the CPU.

You are thinking of the CPUID instruction which as you say does a lot more than just report the ID of the CPU (the "CPUID"). I assumed the person you replied to didn't know there is a CPUID instruction and thus thought you could combine CPU and ID into CPUID and not end up with an ambigious statement likely to confuse people with more x86 specific knowledge.

[starshipeleven]

the person you replied to didn't know there is a CPUID instruction and thus thought you could combine CPU and ID into CPUID and not end up with an ambigious statement likely to confuse people with more x86 specific knowledge.

Typical Devuan user.

[tuxd3v]

(...)
Doing without it is retarded, it means the programs have to run tests to identify the CPU model and supported features by trial and error, or target absolute bullshit lowest common denominator CPU feature set to avoid random crashing on systems that don't support a specific CPU instruction/feature.

You are the only retarded here, at least learn something first, before call retarded to someone more qualified than you.

Since Pentium III that a --> PSN( Processor Serial Number) is being integrated into Intel CPUS <--,
And yes that is what people usually call a CPUID, because its a Unique Identifier..