From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Joel Stanley <joel@jms.id.au>
Cc: "Gautham R . Shenoy" <ego@linux.vnet.ibm.com>
Subject: Re: [PATCH v3] powerpc: Warn about use of smt_snooze_delay
Date: Wed, 9 Sep 2020 23:27:45 +1000 (AEST) [thread overview]
Message-ID: <159965717503.808686.10527215455301576220.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20200902000012.3440389-1-joel@jms.id.au>
On Wed, 2 Sep 2020 09:30:11 +0930, Joel Stanley wrote:
> It's not done anything for a long time. Save the percpu variable, and
> emit a warning to remind users to not expect it to do anything.
>
> This uses pr_warn_once instead of pr_warn_ratelimit as testing
> 'ppc64_cpu --smt=off' on a 24 core / 4 SMT system showed the warning to
> be noisy, as the online/offline loop is slow.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc: Warn about use of smt_snooze_delay
https://git.kernel.org/powerpc/c/a02f6d42357acf6e5de6ffc728e6e77faf3ad217
cheers
prev parent reply other threads:[~2020-09-09 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 0:00 [PATCH v3] powerpc: Warn about use of smt_snooze_delay Joel Stanley
2020-09-09 13:27 ` Michael Ellerman [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=159965717503.808686.10527215455301576220.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=ego@linux.vnet.ibm.com \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@lists.ozlabs.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.