From: "Pankaj Vinodrao Joshi" <Pankaj.VJ@exaleapsemi.com>
To: Greg KH <greg@kroah.com>
Cc: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Re: /proc/cpuinfo not showing all info
Date: Tue, 19 Jan 2021 07:38:13 +0000 [thread overview]
Message-ID: <MA1PR01MB2283479ADC6DC656E1100877EEA90@MA1PR01MB2283.INDPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <X/7AaTeTc1NfFbZm@kroah.com>
[-- Attachment #1.1: Type: text/plain, Size: 1947 bytes --]
i agree each processor type exports different information but i need to pop up information while i do /proc/cpu also i have observed that almost every arch display information w.r.t frequency. Can you suggest how i can add info related to cpufreq into /proc ?
Thanks
________________________________
From: Greg KH <greg@kroah.com>
Sent: Wednesday, January 13, 2021 3:12 PM
To: Pankaj Vinodrao Joshi <Pankaj.VJ@exaleapsemi.com>
Cc: kernelnewbies@kernelnewbies.org <kernelnewbies@kernelnewbies.org>
Subject: Re: /proc/cpuinfo not showing all info
On Wed, Jan 13, 2021 at 09:21:31AM +0000, Pankaj Vinodrao Joshi wrote:
> Hi,
> i am using sifive's u540, RISCV64 with custom kernel 5.10.2 and i am trying to get all hardware information with the help of /proc/cpuinfo but i am not able get all information i need.
>
> i am attaching current /proc/cpuinfo
>
>
> rocessor : 0
> hart : 2
> isa : rv64imafdc
> mmu : sv39
> uarch : sifive,u54-mc
>
>
> but i am expecting following kind of output
>
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 142
> model name : Intel(R) Core(TM) i3-7020U CPU @ 2.30GHz
> stepping : 9
> microcode : 0xde
> cpu MHz : 700.027
> cache size : 3072 KB
> physical id : 0
> siblings : 4
> core id : 0
> cpu cores : 2
> apicid : 0
> initial apicid : 0
> fpu : yes
> fpu_exception : yes
> cpuid level : 22
> wp : yes
>
> Can someone suggest me how i can print all info with /proc/cpuinfo ??
Each processor type exports different information in /proc/cpuinfo. How
would a riscv cpu have the same types as an x86 cpu?
You have to treat each cpu type individually, there is no common format
for all different CPUs out there, sorry.
Hope this helps,
greg k-h
[EXT]
[-- Attachment #1.2: Type: text/html, Size: 4292 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-01-19 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 9:21 /proc/cpuinfo not showing all info Pankaj Vinodrao Joshi
2021-01-13 9:42 ` Greg KH
2021-01-19 7:38 ` Pankaj Vinodrao Joshi [this message]
2021-01-19 7:55 ` Greg KH
2021-01-19 9:08 ` Pankaj Vinodrao Joshi
2021-01-19 10:15 ` Greg KH
2021-01-19 9:09 ` Valdis Klētnieks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MA1PR01MB2283479ADC6DC656E1100877EEA90@MA1PR01MB2283.INDPRD01.PROD.OUTLOOK.COM \
--to=pankaj.vj@exaleapsemi.com \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).