From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <longman@redhat.com>
Cc: 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>,
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>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v5 4/4] intel_idle: Add ibrs_off module parameter to force disable IBRS
Date: Wed, 26 Jul 2023 12:25:12 +0200 [thread overview]
Message-ID: <20230726102512.GD3802077@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <f5f25279-bbb5-e040-aeaa-dd3d8686c670@redhat.com>
On Tue, Jul 25, 2023 at 04:45:49PM -0400, Waiman Long wrote:
> On 7/10/23 15:48, Waiman Long wrote:
> > Commit bf5835bcdb96 ("intel_idle: Disable IBRS during long idle")
> > disables IBRS when the cstate is 6 or lower. However, there are
> > some use cases where a customer may want to use max_cstate=1 to
> > lower latency. Such use cases will suffer from the performance
> > degradation caused by the enabling of IBRS in the sibling idle thread.
> > Add a "ibrs_off" module parameter to force disable IBRS and the
> > CPUIDLE_FLAG_IRQ_ENABLE flag if set.
> >
> > In the case of a Skylake server with max_cstate=1, this new ibrs_off
> > option will likely increase the IRQ response latency as IRQ will now
> > be disabled.
> >
> > When running SPECjbb2015 with cstates set to C1 on a Skylake system.
> >
> > First test when the kernel is booted with: "intel_idle.ibrs_off"
> > max-jOPS = 117828, critical-jOPS = 66047
> >
> > Then retest when the kernel is booted without the "intel_idle.ibrs_off"
> > added.
> > max-jOPS = 116408, critical-jOPS = 58958
> >
> > That means booting with "intel_idle.ibrs_off" improves performance by:
> > max-jOPS: 1.2%, which could be considered noise range.
> > critical-jOPS: 12%, which is definitely a solid improvement.
> >
> > The admin-guide/pm/intel_idle.rst file is updated to add a description
> > about the new "ibrs_off" module parameter.
> >
> > Signed-off-by: Waiman Long <longman@redhat.com>
> > Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > ---
> > Documentation/admin-guide/pm/intel_idle.rst | 17 ++++++++++++++++-
> > drivers/idle/intel_idle.c | 11 ++++++++++-
> > 2 files changed, 26 insertions(+), 2 deletions(-)
>
> Ping! Is there further suggested changes for this patch series or is it good
> enough to be merged?
I suppose I'll go stick it in x86/core unless someone objects.
next prev parent reply other threads:[~2023-07-26 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 19:48 [PATCH v5 0/4] x86/speculation: Disable IBRS when idle Waiman Long
2023-07-10 19:48 ` [PATCH v5 1/4] x86/speculation: Add __update_spec_ctrl() helper Waiman Long
2023-07-10 19:48 ` [PATCH v5 2/4] x86/idle: Disable IBRS when cpu is offline Waiman Long
2023-07-10 19:48 ` [PATCH v5 3/4] intel_idle: Use __update_spec_ctrl() in intel_idle_ibrs() Waiman Long
2023-07-10 19:48 ` [PATCH v5 4/4] intel_idle: Add ibrs_off module parameter to force disable IBRS Waiman Long
2023-07-25 20:45 ` Waiman Long
2023-07-26 10:25 ` Peter Zijlstra [this message]
2023-07-26 10:44 ` Robin Jarry
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=20230726102512.GD3802077@hirez.programming.kicks-ass.net \
--to=peterz@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=rafael.j.wysocki@intel.com \
--cc=rdunlap@infradead.org \
--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
Powered by JetHome