From: Chen Yu <yu.c.chen@intel.com>
To: Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>
Cc: <x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Arnd Bergmann <arnd@arndb.de>, <virtualization@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, Juergen Gross <jgross@suse.com>,
"Nikolay Borisov" <nik.borisov@suse.com>,
Chen Yu <yu.chen.surf@gmail.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
Prem Nath Dey <prem.nath.dey@intel.com>,
"Xiaoping Zhou" <xiaoping.zhou@intel.com>
Subject: Re: [PATCH v3] x86/paravirt: Disable virt spinlock on bare metal
Date: Mon, 15 Jul 2024 14:42:03 +0800 [thread overview]
Message-ID: <ZpTEu6H14Y0GFg13@chenyu5-mobl2> (raw)
In-Reply-To: <20240625125403.187110-1-yu.c.chen@intel.com>
On 2024-06-25 at 20:54:03 +0800, Chen Yu wrote:
> The kernel can change spinlock behavior when running as a guest. But
> this guest-friendly behavior causes performance problems on bare metal.
> So there's a 'virt_spin_lock_key' static key to switch between the two
> modes.
>
> The static key is always enabled by default (run in guest mode) and
> should be disabled for bare metal (and in some guests that want native
> behavior).
>
> Performance drop is reported when running encode/decode workload and
> BenchSEE cache sub-workload.
> Bisect points to commit ce0a1b608bfc ("x86/paravirt: Silence unused
> native_pv_lock_init() function warning"). When CONFIG_PARAVIRT_SPINLOCKS
> is disabled the virt_spin_lock_key is incorrectly set to true on bare
> metal. The qspinlock degenerates to test-and-set spinlock, which
> decrease the performance on bare metal.
>
> Set the default value of virt_spin_lock_key to false. If booting in a VM,
> enable this key. Later during the VM initialization, if other
> high-efficient spinlock is preferred(paravirt-spinlock eg), the
> virt_spin_lock_key is disabled accordingly. The relation is described as
> below:
>
> X86_FEATURE_HYPERVISOR Y Y Y N
> CONFIG_PARAVIRT_SPINLOCKS Y Y N Y/N
> PV spinlock Y N N Y/N
>
> virt_spin_lock_key N N Y N
>
> Fixes: ce0a1b608bfc ("x86/paravirt: Silence unused native_pv_lock_init() function warning")
> Suggested-by: Dave Hansen <dave.hansen@linux.intel.com>
> Suggested-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
> Suggested-by: Nikolay Borisov <nik.borisov@suse.com>
> Reported-by: Prem Nath Dey <prem.nath.dey@intel.com>
> Reported-by: Xiaoping Zhou <xiaoping.zhou@intel.com>
> Signed-off-by: Chen Yu <yu.c.chen@intel.com>
>
Hi,
A gentle ping of this patch. Or should I need to send a new version with updated
Reviewed-by tag from Nikolay?
thanks,
Chenyu
prev parent reply other threads:[~2024-07-15 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 12:54 [PATCH v3] x86/paravirt: Disable virt spinlock on bare metal Chen Yu
2024-06-25 13:42 ` Nikolay Borisov
2024-06-25 14:50 ` Chen Yu
2024-06-25 15:08 ` Nikolay Borisov
2024-06-26 3:31 ` Zhuo, Qiuxu
2024-06-26 4:38 ` Nikolay Borisov
2024-07-15 6:42 ` Chen Yu [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=ZpTEu6H14Y0GFg13@chenyu5-mobl2 \
--to=yu.c.chen@intel.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nik.borisov@suse.com \
--cc=prem.nath.dey@intel.com \
--cc=qiuxu.zhuo@intel.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux.dev \
--cc=x86@kernel.org \
--cc=xiaoping.zhou@intel.com \
--cc=yu.chen.surf@gmail.com \
/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