On Thu, 8 Jan 2015, Russell King - ARM Linux wrote: > It's not a regression - yet. No one has shown that userspace has broken > according to the definition of the first quote above, and that's the > whole point.
How much does one have to regress before it is a problem? I have two projects I've worked on that "broke" due to this issue. They were minor breakages though. The "linux_logo" userspace sysinfo tool broke to the extent that it was parsing for the bogomips string in /proc/cpuinfo and printed poorly formatted and/or corrupted text info to screen when it couldn't find it. The "PAPI" library had some really ancient (and poorly thought-out) fallback code that would try to estimate MHz from bogomips if a MHz value was not available via the traditional methods. This failed after the change too, but not many people use PAPI on ARM so it wasn't that big an issue. I noticed these problems early, even before the change hit mainline. But when I complained I was told in no uncertain terms that the ARM maintainers were tired of hearing about bogomips issues and nothing could be done to stop the change from getting in. Vince -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
