From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
WANG Chao <chao.wang@ucloud.cn>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Vikas Shivappa <vikas.shivappa@linux.intel.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Len Brown <len.brown@intel.com>,
Philippe Ombredanne <pombredanne@nexb.com>,
Mathias Krause <minipli@googlemail.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH] x86: use cpufreq_quick_get() for /proc/cpuinfo "cpu MHz" again
Date: Wed, 15 Nov 2017 08:54:26 +0100 [thread overview]
Message-ID: <20171115075426.GA23018@kroah.com> (raw)
In-Reply-To: <20171115074358.4jf4sjpq4ffmhmpi@gmail.com>
On Wed, Nov 15, 2017 at 08:43:58AM +0100, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
>
> > On Wednesday, November 15, 2017 1:06:12 AM CET Linus Torvalds wrote:
> > > On Tue, Nov 14, 2017 at 4:04 PM, Linus Torvalds
> > > <torvalds@linux-foundation.org> wrote:
> > > > On Tue, Nov 14, 2017 at 3:53 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > > >> Current head + Raphaels patch:
> > > >>
> > > >> real 0m0.029s
> > > >> user 0m0.000s
> > > >> sys 0m0.010s
> > > >>
> > > >> So that patch is actually slower.
> > > >
> > > > Oh it definitely is expected to be slower, because it does the IPI to
> > > > all the cores and actually gets their frequency right.
> > > >
> > > > It was the old one that we had to revert (because it did so
> > > > sequentially) that was really bad, and took something like 2+ seconds
> > > > on Ingo's 160-core thing, iirc.
> > >
> > > Looked it up. Ingo's machine "only" had 120 cores, and he said
> > >
> > > fomalhaut:~> time cat /proc/cpuinfo >/dev/null
> > > real 0m2.689s
> > >
> > > for the bad serial case, so yeah, it looks "a bit" better than it was ;)
> >
> > OK, so may I queue it up?
> >
> > I don't think I can get that to work substantially faster anyway ...
>
> The new version is OK I suppose:
>
> Acked-by: Ingo Molnar <mingo@kernel.org>
>
> I also think that /proc/cpuinfo is a pretty bad interface for many uses - I
> personally only very rarely need the cpuinfo of _all_ CPUs.
>
> We we should eventually have /proc/cpu/N/info or so, so that 99% of the times
> cpuinfo is needed to report bugs we can do:
>
> cat /proc/cpu/0/info
>
> With maybe also the following variants:
>
> /proc/cpu/first/
> /proc/cpu/last/
> /proc/cpu/current/
>
> ... to the first/last/current CPUs.
We started to move this info into /sys/devices/cpu/ in individual files,
but that got stalled due to a lack of review and general "freak out" by
the ARM maintainers :)
Hopefully that patch set will come back soon so people can review it
properly.
thanks,
greg k-h
next prev parent reply other threads:[~2017-11-15 7:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 10:38 [PATCH] x86: use cpufreq_quick_get() for /proc/cpuinfo "cpu MHz" again WANG Chao
2017-11-09 16:06 ` Rafael J. Wysocki
2017-11-09 22:30 ` Rafael J. Wysocki
2017-11-10 0:06 ` Rafael J. Wysocki
2017-11-10 4:04 ` WANG Chao
2017-11-10 4:11 ` WANG Chao
2017-11-10 19:11 ` Linus Torvalds
2017-11-10 23:09 ` Rafael J. Wysocki
2017-11-14 22:47 ` Rafael J. Wysocki
2017-11-14 23:02 ` Linus Torvalds
2017-11-14 23:53 ` Thomas Gleixner
2017-11-15 0:04 ` Linus Torvalds
2017-11-15 0:06 ` Linus Torvalds
2017-11-15 0:30 ` Rafael J. Wysocki
2017-11-15 0:34 ` Linus Torvalds
2017-11-15 1:13 ` [PATCH] x86 / CPU: Always show current CPU frequency in /proc/cpuinfo Rafael J. Wysocki
2017-11-15 8:47 ` Thomas Gleixner
2017-11-15 9:33 ` WANG Chao
2017-11-16 0:24 ` Rafael J. Wysocki
2017-11-16 9:50 ` WANG Chao
2017-11-16 13:54 ` Rafael J. Wysocki
2017-11-17 4:27 ` WANG Chao
2017-11-17 13:33 ` Rafael J. Wysocki
2017-11-15 7:43 ` [PATCH] x86: use cpufreq_quick_get() for /proc/cpuinfo "cpu MHz" again Ingo Molnar
2017-11-15 7:54 ` Greg Kroah-Hartman [this message]
2017-11-15 17:27 ` Linus Torvalds
2017-11-15 18:05 ` Thomas Gleixner
2017-11-15 8:47 ` Thomas Gleixner
2017-11-15 0:06 ` Rafael J. Wysocki
2017-11-10 7:25 ` Ingo Molnar
2017-11-10 9:21 ` WANG Chao
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=20171115075426.GA23018@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chao.wang@ucloud.cn \
--cc=hpa@zytor.com \
--cc=kstewart@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=minipli@googlemail.com \
--cc=pombredanne@nexb.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vikas.shivappa@linux.intel.com \
--cc=x86@kernel.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).