From: Randy Dunlap <rdunlap@infradead.org>
To: Waiman Long <longman@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Len Brown <lenb@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
x86@kernel.org, linux-pm@vger.kernel.org,
Robin Jarry <rjarry@redhat.com>, Joe Mario <jmario@redhat.com>
Subject: Re: [PATCH v4 4/4] intel_idle: Add ibrs_off module parameter to force disable IBRS
Date: Tue, 27 Jun 2023 19:58:15 -0700 [thread overview]
Message-ID: <24b34b27-d2eb-e287-ffbb-29ffde66790d@infradead.org> (raw)
In-Reply-To: <20230628022554.1638318-5-longman@redhat.com>
Hi,
On 6/27/23 19:25, Waiman Long wrote:
> Documentation/admin-guide/pm/intel_idle.rst | 17 ++++++++++++++++-
> drivers/idle/intel_idle.c | 14 ++++++++++++--
> 2 files changed, 28 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/admin-guide/pm/intel_idle.rst b/Documentation/admin-guide/pm/intel_idle.rst
> index b799a43da62e..8604e6d1fe2c 100644
> --- a/Documentation/admin-guide/pm/intel_idle.rst
> +++ b/Documentation/admin-guide/pm/intel_idle.rst
You may take or leave these comments as you choose.
> @@ -216,6 +216,21 @@ are ignored).
> The idle states disabled this way can be enabled (on a per-CPU basis) from user
> space via ``sysfs``.
>
> +The ``ibrs_off`` module parameter is a boolean flag (default to false). It is
(default false).
or
(defaults to false).
Then I think it reads better if the next sentence begins with: "If set,"
instead of having it in the middle of the sentence.
> +used to control if IBRS (Indirect Branch Restricted Speculation) should be
> +turned off, if set, when the CPU enters an idle state. This flag will not
> +affect CPUs that are using Enhanced IBRS which can remain on with little
> +performance impact.
> +
> +For some CPUs, IBRS will be selected as mitigation for Spectre v2 and Retbleed
> +security vulnerabilities by default. Leaving the IBRS mode on while idling may
> +have a performance impact on its sibling CPU. The IBRS mode will be turned off
> +by default when the CPU enters into a deep idle state, but not in some
> +shallower ones. Setting the ``ibrs_off`` module parameter will force the IBRS
> +mode to off when the CPU is in any one of the available idle states. This may
> +help performance of a sibling CPU at the expense of a slightly higher wakeup
> +latency for the idle CPU.
thanks.
--
~Randy
next prev parent reply other threads:[~2023-06-28 2:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 2:25 [PATCH v4 0/4] x86/speculation: Disable IBRS when idle Waiman Long
2023-06-28 2:25 ` [PATCH v4 1/4] x86/speculation: Add __update_spec_ctrl() helper Waiman Long
2023-07-03 10:28 ` Peter Zijlstra
2023-07-03 15:08 ` Waiman Long
2023-06-28 2:25 ` [PATCH v4 2/4] x86/idle: Disable IBRS when cpu is offline Waiman Long
2023-06-28 2:25 ` [PATCH v4 3/4] intel_idle: Use __update_spec_ctrl() in intel_idle_ibrs() Waiman Long
2023-06-28 2:25 ` [PATCH v4 4/4] intel_idle: Add ibrs_off module parameter to force disable IBRS Waiman Long
2023-06-28 2:58 ` Randy Dunlap [this message]
2023-06-29 3:03 ` Waiman Long
2023-07-03 10:32 ` Peter Zijlstra
2023-07-03 15:09 ` Waiman Long
2023-06-28 17:13 ` [PATCH v4 0/4] x86/speculation: Disable IBRS when idle Rafael J. Wysocki
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=24b34b27-d2eb-e287-ffbb-29ffde66790d@infradead.org \
--to=rdunlap@infradead.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jmario@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjarry@redhat.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®