On Fri, Nov 11, 2016 at 7:59 AM, Andreas Tobler wrote:
> On 11.11.16 11:06, Richard Earnshaw wrote:
>>
>> On 11/11/16 02:56, Andrew Pinski wrote:
>>>
>>> As I mentioned in my other emails, parsing /proc/cpuinfo has one issue
>>> is that the current parsing assumes many different things about the
>
On 11.11.16 11:06, Richard Earnshaw wrote:
On 11/11/16 02:56, Andrew Pinski wrote:
As I mentioned in my other emails, parsing /proc/cpuinfo has one issue
is that the current parsing assumes many different things about the
format. So the best way to do this is to parse
/sys/devices/system/cpu/cp
On 11/11/16 02:56, Andrew Pinski wrote:
> As I mentioned in my other emails, parsing /proc/cpuinfo has one issue
> is that the current parsing assumes many different things about the
> format. So the best way to do this is to parse
> /sys/devices/system/cpu/cpuN/regs/identification/midr_el1 files
As I mentioned in my other emails, parsing /proc/cpuinfo has one issue
is that the current parsing assumes many different things about the
format. So the best way to do this is to parse
/sys/devices/system/cpu/cpuN/regs/identification/midr_el1 files
instead. To get which cpu are present (though n
