The CPU features reported by /proc/cpuinfo should be logged to the event log.
----- Rom -----Original Message----- From: boinc_dev [mailto:[email protected]] On Behalf Of Carl Christensen Sent: Thursday, August 22, 2013 1:53 PM To: [email protected] Subject: [boinc_dev] android -- boinc not storing cpu features(/proc/cpuinfo features) Hi, I may be late to this party, but am I right in thinking boinc isn't parsing out the cpu features on Android? for example my phone supports vfp, vfpv3, and neon, but on my Einstein@home record it says "No coprocessor" should this be a trac item? it seems easy to implement, in the boinc/client/hostinfo_unix.cpp (I assume that's what android is using), add to the kFeatures e.g. static const char *kFeatures[35] = { "fpu", "vme", "de", "pse", "tsc", "msr", "pae", "mce", "cx8", "apic", NULL, "sep", "mtrr", "pge", "mca", "cmov", "pat", "pse36", "psnum", "clflush", NULL, "ds", "acpi", "mmx", "fxsr", "sse", "sse2", "ss", "htt", "tm", "ia64", "pbe", "neon", "vfpv3", "vfp", }; (and bump up the loops to 35, or maybe have a constant we can just change once) I would like to know these features at runtime (of course I can just grep /proc/cpuinfo) as I am working on the benchmarks with vfp & neon (if the device supports it) I guess an odd thing is "fpu" should be set on boinc, but you also need vfp, vfpv3, and neon to figure out which fpu you have! _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
