All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: "Pankaj Vinodrao Joshi" <Pankaj.VJ@exaleapsemi.com>
Cc: Greg KH <greg@kroah.com>,
	"kernelnewbies@kernelnewbies.org"
	<kernelnewbies@kernelnewbies.org>
Subject: Re: /proc/cpuinfo not showing all info
Date: Tue, 19 Jan 2021 04:09:39 -0500	[thread overview]
Message-ID: <114287.1611047379@turing-police> (raw)
In-Reply-To: <MA1PR01MB2283479ADC6DC656E1100877EEA90@MA1PR01MB2283.INDPRD01.PROD.OUTLOOK.COM>

On Tue, 19 Jan 2021 07:38:13 +0000, "Pankaj Vinodrao Joshi" said:

> 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 ?

You may wish to issue this command:

find /sys -name '*freq*'

and then meditate on the relative difficulty of parsing /proc/cpuinfo
and a sysfs file, and ask yourself if you want to to re-think your design.

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      parent reply	other threads:[~2021-01-19  9:09 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
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 [this message]

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=114287.1611047379@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.