From: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
To: Alejandro Vallejo <alejandro.garciavallejo@amd.com>,
<xen-devel@lists.xenproject.org>
Cc: "Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Jason Andryuk" <jason.andryuk@amd.com>,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: Re: [PATCH 0/2] x86/svm: Add support for Bus Lock Threshold
Date: Tue, 20 Jan 2026 12:22:27 +0100 [thread overview]
Message-ID: <DFTDLSLZPN6F.3UC4R81DBXYR8@amd.com> (raw)
In-Reply-To: <20260120095353.2778-1-alejandro.garciavallejo@amd.com>
On Tue Jan 20, 2026 at 10:53 AM CET, Alejandro Vallejo wrote:
> Bus Locks are very costly and a VM left unchecked spamming instructions that
> lock the memory bus (e.g: unaligned atomic CAS) makes system perf take a
> nosedive. This patch is similar to BLD of VMX, but for SVM. It configures all
> VMRUNs so they automatically exit at the first encounter of a buslock event,
> effectively rate-limiting them.
Does this warrant an entry in the CHANGELOG?
Cheers,
Alejandro
>
> Cheers,
> Alejandro
>
> Alejandro Vallejo (2):
> x86/svm: Add infrastructure for Bus Lock Threshold
> x86/svm: Intercept Bus Locks for HVM guests
>
> xen/arch/x86/hvm/svm/svm.c | 5 +++++
> xen/arch/x86/hvm/svm/vmcb.c | 6 ++++++
> xen/arch/x86/hvm/svm/vmcb.h | 15 +++++++++++++--
> xen/arch/x86/include/asm/hvm/svm.h | 2 ++
> xen/arch/x86/include/asm/perfc_defn.h | 2 +-
> 5 files changed, 27 insertions(+), 3 deletions(-)
>
>
> base-commit: 7b3e1b4e848d34c9a5b6634009959a7b9dd42104
next prev parent reply other threads:[~2026-01-20 11:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 9:53 [PATCH 0/2] x86/svm: Add support for Bus Lock Threshold Alejandro Vallejo
2026-01-20 9:53 ` [PATCH 1/2] x86/svm: Add infrastructure " Alejandro Vallejo
2026-01-20 13:12 ` Andrew Cooper
2026-01-20 13:57 ` Alejandro Vallejo
2026-01-20 13:19 ` Teddy Astie
2026-01-20 13:30 ` Jan Beulich
2026-01-21 12:40 ` Alejandro Vallejo
2026-01-21 13:07 ` Jan Beulich
2026-01-21 15:10 ` Alejandro Vallejo
2026-01-20 13:58 ` Alejandro Vallejo
2026-01-20 9:53 ` [PATCH 2/2] x86/svm: Intercept Bus Locks for HVM guests Alejandro Vallejo
2026-01-20 13:11 ` Teddy Astie
2026-01-20 13:29 ` Jan Beulich
2026-01-20 14:41 ` Alejandro Vallejo
2026-01-20 13:18 ` Andrew Cooper
2026-01-20 13:27 ` Jan Beulich
2026-01-20 13:29 ` Andrew Cooper
2026-01-20 13:34 ` Jan Beulich
2026-01-20 14:11 ` Andrew Cooper
2026-01-20 14:16 ` Jan Beulich
2026-01-20 14:26 ` Andrew Cooper
2026-01-20 14:32 ` Jan Beulich
2026-01-20 15:28 ` Alejandro Vallejo
2026-01-20 15:41 ` Alejandro Vallejo
2026-01-20 11:22 ` Alejandro Vallejo [this message]
2026-01-20 13:21 ` [PATCH 0/2] x86/svm: Add support for Bus Lock Threshold Andrew Cooper
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=DFTDLSLZPN6F.3UC4R81DBXYR8@amd.com \
--to=alejandro.garciavallejo@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=jason.andryuk@amd.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.