From: "Michal Suchánek" <msuchanek@suse.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: No Linux logs when doing `ppc64_cpu --smt=off/8`
Date: Mon, 14 Feb 2022 14:56:57 +0100 [thread overview]
Message-ID: <20220214135657.GM3113@kunlun.suse.cz> (raw)
In-Reply-To: <e6701fa9-a51b-3706-5aa5-bb6c7ae76cf0@molgen.mpg.de>
On Mon, Feb 14, 2022 at 01:33:24PM +0100, Paul Menzel wrote:
> Dear Michal,
>
>
> Thank you for your reply.
>
> Am 14.02.22 um 10:43 schrieb Michal Suchánek:
>
> > On Mon, Feb 14, 2022 at 07:08:07AM +0100, Paul Menzel wrote:
> > > Dear PPC folks,
> > >
> > >
> > > On the POWER8 server IBM S822LC running `ppc64_cpu --smt=off` or `ppc64_cpu
> > > --smt=8`, Linux 5.17-rc4 does not log anything. I would have expected a
> > > message about the change in number of processing units.
> >
> > IIRC it was considered too noisy for systems with many CPUs and the
> > message was dropped. You can always check the resulting state with
> > ppc64_cpu or examining sysfs.
>
> Yes, simple `nproc` suffice, but I was more thinking about, that the Linux
> log is often used for debugging and the changes of amount of processing
> units might be good to have. `ppc64_cpu --smt=off` or `=8` seems to block
> for quite some time, and each thread/processing unit seems to powered
> down/on sequentially, so it takes quite some time and it blocks. So 140
> messages would indeed be quite noise. No idea how `ppc64_cpu` works, and if
> it could log a message at the beginning and end.
Yes, it enables/disables threads one by one. AFAICT the kernel cannot know that
ppc64_cpu will enable/disable more threads later, it can either log each
or none. Rate limiting would not show the whole picture so it's not
great solution either.
Thanks
Michal
next prev parent reply other threads:[~2022-02-14 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 6:08 No Linux logs when doing `ppc64_cpu --smt=off/8` Paul Menzel
2022-02-14 9:43 ` Michal Suchánek
2022-02-14 12:33 ` Paul Menzel
2022-02-14 13:56 ` Michal Suchánek [this message]
2022-02-17 1:07 ` Michael Ellerman
2022-02-17 7:10 ` Joel Stanley
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=20220214135657.GM3113@kunlun.suse.cz \
--to=msuchanek@suse.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=pmenzel@molgen.mpg.de \
/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).