| 1 |
On Fri, Sep 28, 2018 at 5:33 AM Marc Joliet <marcec@×××.de> wrote: |
| 2 |
> |
| 3 |
> Am Freitag, 28. September 2018, 06:04:29 CEST schrieb Walter Dnes: |
| 4 |
> > mmxext does not have its own flag in /proc/cpuinfo. |
| 5 |
> |
| 6 |
> ??? |
| 7 |
> |
| 8 |
> % cat /proc/cpuinfo |
| 9 |
> [...] |
| 10 |
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl cpuid extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch vmmcall |
| 11 |
> ^^^ ^^^^^^ |
| 12 |
> (I hope the formatting doesn't get messed up, the point is that my /proc/cpuinfo *does* show mmxext.) |
| 13 |
|
| 14 |
That cpuid flag only appears on AMD processors. It is never set for |
| 15 |
Intel processors. |
| 16 |
|
| 17 |
cpuid2cpuflags makes a special exception for this case. |
| 18 |
|
| 19 |
https://github.com/mgorny/cpuid2cpuflags/blob/master/src/x86.c#L71 |
Archives