From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 3/4] x86/tsx: Remove opencoded MSR_ARCH_CAPS check
Date: Wed, 17 May 2023 16:38:20 +0200 [thread overview]
Message-ID: <d4e44806-098b-13f6-7ccd-0119a8a2d06e@suse.com> (raw)
In-Reply-To: <20230516145334.1271347-4-andrew.cooper3@citrix.com>
On 16.05.2023 16:53, Andrew Cooper wrote:
> The current cpu_has_tsx_ctrl tristate is serving double pupose; to signal the
> first pass through tsx_init(), and the availability of MSR_TSX_CTRL.
>
> Drop the variable, replacing it with a once boolean, and altering
> cpu_has_tsx_ctrl to come out of the feature information.
>
> No functional change.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
next prev parent reply other threads:[~2023-05-17 14:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 14:53 [PATCH 0/4] x86: Feature check cleanup Andrew Cooper
2023-05-16 14:53 ` [PATCH 1/4] x86/cpufeature: Rework {boot_,}cpu_has() Andrew Cooper
2023-05-17 14:01 ` Jan Beulich
2023-05-19 15:24 ` Andrew Cooper
2023-05-22 6:58 ` Jan Beulich
2023-05-16 14:53 ` [PATCH 2/4] x86/vtx: Remove opencoded MSR_ARCH_CAPS check Andrew Cooper
2023-05-17 14:36 ` Jan Beulich
2023-05-17 14:38 ` Jan Beulich
2023-05-26 4:56 ` Tian, Kevin
2023-05-16 14:53 ` [PATCH 3/4] x86/tsx: " Andrew Cooper
2023-05-17 14:38 ` Jan Beulich [this message]
2023-05-16 14:53 ` [PATCH 4/4] x86/spec-ctrl: " Andrew Cooper
2023-05-17 14:47 ` Jan Beulich
2023-05-17 16:35 ` Andrew Cooper
2023-05-19 6:00 ` Jan Beulich
2023-05-19 14:38 ` Andrew Cooper
2023-05-22 7:10 ` Jan Beulich
2023-05-22 14:14 ` Andrew Cooper
2023-05-22 14:30 ` 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=d4e44806-098b-13f6-7ccd-0119a8a2d06e@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.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.