From: Jan Beulich <jbeulich@suse.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: text-tsx fails on Intel core 8th gen system
Date: Wed, 3 Apr 2024 17:04:20 +0200 [thread overview]
Message-ID: <8c7ffed8-4faa-4dd3-8a41-d436ba49898b@suse.com> (raw)
In-Reply-To: <Zg1stUacaDBkyDOn@mail-itl>
On 03.04.2024 16:50, Marek Marczykowski-Górecki wrote:
> Hi,
>
> I've noticed that tools/tests/tsx/test-tsx fails on a system with Intel
> Core i7-8750H. Specific error I get:
>
> [user@dom0 tsx]$ ./test-tsx
> TSX tests
> Got 16 CPUs
> Testing MSR_TSX_FORCE_ABORT consistency
> CPU0 val 0
> Testing MSR_TSX_CTRL consistency
> Testing MSR_MCU_OPT_CTRL consistency
> CPU0 val 0
> Testing RTM behaviour
> Got #UD
> Host reports RTM, but appears unavailable
Isn't this ...
> Testing PV default/max policies
> Max: RTM 1, HLE 1, TSX_FORCE_ABORT 0, RTM_ALWAYS_ABORT 0, TSX_CTRL 0
> Def: RTM 0, HLE 0, TSX_FORCE_ABORT 0, RTM_ALWAYS_ABORT 0, TSX_CTRL 0
> HLE/RTM offered to guests despite not being available
> Testing HVM default/max policies
> Max: RTM 1, HLE 1, TSX_FORCE_ABORT 0, RTM_ALWAYS_ABORT 0, TSX_CTRL 0
> Def: RTM 0, HLE 0, TSX_FORCE_ABORT 0, RTM_ALWAYS_ABORT 0, TSX_CTRL 0
> HLE/RTM offered to guests despite not being available
> Testing PV guest
> Created d8
> Cur: RTM 0, HLE 0, TSX_FORCE_ABORT 0, RTM_ALWAYS_ABORT 0, TSX_CTRL 0
> Cur: RTM 1, HLE 1, TSX_FORCE_ABORT 0, RTM_ALWAYS_ABORT 0, TSX_CTRL 0
> Testing HVM guest
> Created d9
> Cur: RTM 0, HLE 0, TSX_FORCE_ABORT 0, RTM_ALWAYS_ABORT 0, TSX_CTRL 0
> Cur: RTM 1, HLE 1, TSX_FORCE_ABORT 0, RTM_ALWAYS_ABORT 0, TSX_CTRL 0
> [user@dom0 tsx]$ echo $?
> 1
... the reason for this?
Jan
next prev parent reply other threads:[~2024-04-03 15:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 14:50 text-tsx fails on Intel core 8th gen system Marek Marczykowski-Górecki
2024-04-03 15:04 ` Jan Beulich [this message]
2024-04-03 16:41 ` Marek Marczykowski-Górecki
2024-04-04 6:07 ` Jan Beulich
2024-04-03 17:09 ` Andrew Cooper
2024-04-04 10:41 ` [PATCH] x86/tsx: Cope with RTM_ALWAYS_ABORT vs RTM mismatch Andrew Cooper
2024-04-04 11:02 ` Marek Marczykowski-Górecki
2024-04-04 12:45 ` Jan Beulich
2024-04-04 13:22 ` Andrew Cooper
2024-04-04 13:32 ` Jan Beulich
2024-04-05 13:01 ` Andrew Cooper
2024-04-05 13:25 ` Jan Beulich
2024-04-05 13:07 ` [PATCH v2] " Andrew Cooper
2024-04-05 13:40 ` Jan Beulich
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=8c7ffed8-4faa-4dd3-8a41-d436ba49898b@suse.com \
--to=jbeulich@suse.com \
--cc=marmarek@invisiblethingslab.com \
--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.