kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Pankaj Vinodrao Joshi <Pankaj.VJ@exaleapsemi.com>
Cc: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Re: /proc/cpuinfo not showing all info
Date: Tue, 19 Jan 2021 08:55:47 +0100	[thread overview]
Message-ID: <YAaQg5P9mTyQ0j9/@kroah.com> (raw)
In-Reply-To: <MA1PR01MB2283479ADC6DC656E1100877EEA90@MA1PR01MB2283.INDPRD01.PROD.OUTLOOK.COM>

On Tue, Jan 19, 2021 at 07:38:13AM +0000, Pankaj  Vinodrao Joshi wrote:
> 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 ?

I am sorry, but I can not parse this very well, can you please explain
exactly what you wish to do and why the "normal" apis that expose the
current frequency of the processor do not work for you?  (hint, it's not
/proc/cpuinfo)

Also, who is demanding this requirement?

thanks,

greg k-h

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

  reply	other threads:[~2021-01-19  7:56 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 [this message]
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=YAaQg5P9mTyQ0j9/@kroah.com \
    --to=greg@kroah.com \
    --cc=Pankaj.VJ@exaleapsemi.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).