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 11:15:22 +0100 [thread overview]
Message-ID: <YAaxOtCEm/KV/dkC@kroah.com> (raw)
In-Reply-To: <MA1PR01MB22838439E85B290E08CCE3F0EEA30@MA1PR01MB2283.INDPRD01.PROD.OUTLOOK.COM>
On Tue, Jan 19, 2021 at 09:08:23AM +0000, Pankaj Vinodrao Joshi wrote:
> sorry for the last mail that i was not able to convey what i was meaning to, i have noticed for almost all ARCH when i will do $ cat /proc/cpuinfo ,it will shows all cpu related info including cpu frequency but for my case i am getting almost everything except cpu frequency in /proc/cpuinfo.
> Now my question is how i can add this cpufreq related info into /proc/cpuinfo ??
Why do you want to add cpu frequency to /proc/cpuinfo?
You can do that, but it will not be the "correct" way to export this
information to userspace so that userspace can properly handle it.
> Also what all other alternatives /methods are there to get cpufreq
> related info from kernel ??
See what Valdis wrote, that's the correct api to use.
Good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-01-19 10:15 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 [this message]
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=YAaxOtCEm/KV/dkC@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 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.