Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 Jul 2009 13:42:45 +0200
From:      Roman Divacky <rdivacky@freebsd.org>
To:        Peter Jeremy <peterjeremy@optushome.com.au>
Cc:        freebsd-emulation@freebsd.org
Subject:   Re: Linuxolator proc/cpuinfo
Message-ID:  <20090711114245.GA37763@freebsd.org>
In-Reply-To: <20090711005130.GB43362@server.vk2pj.dyndns.org>
References:  <20090711005130.GB43362@server.vk2pj.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 11, 2009 at 10:51:30AM +1000, Peter Jeremy wrote:
> I've recently noticed that the 'flags' output from cpuinfo is
> incomplete.  As an example, my Atom N270 reports:
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat b19 b21 mmxext mmx fxsr xmm sse2 b27 b28 b29 3dnow
> 
> Whereas dmesg reports:
>   Features=0xbfe9fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
>   Features2=0x40c39d<SSE3,DTES64,MON,DS_CPL,EST,TM2,SSSE3,xTPR,PDCM,<b22>>
>   AMD Features2=0x1<LAHF>
> 
> Is there a particular reason why the flags output isn't complete?
> 
> As an example, I recently tried to run a binary Sage package
> (www.sagemath.org) in FreeBSD -current.  During startup, it verifies
> that the target CPU supports the instructions used and, on my Atom,
> complained that 'ssse3', 'pni' and 'sse' are missing - whilst they
> are missing from cpuinfo flags, they are present in the Atom.

feel free to submit patch :) it should be pretty trivial. I am willing
to review/commit



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090711114245.GA37763>