From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Jan Beulich" <JBeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH 0/3] x86/ucode: Simplify/fix loading paths further
Date: Thu, 7 Nov 2024 12:21:14 +0000 [thread overview]
Message-ID: <20241107122117.4073266-1-andrew.cooper3@citrix.com> (raw)
collect_cpu_info() is fairly expensive and called excessively. Rationalise
this substantially.
Except I found yet another bug when testing this. Notes in patch 3.
Andrew Cooper (3):
x86/ucode: Don't use microcode_update_cpu() in early_microcode_load()
x86/ucode: Fold microcode_update_cpu() and fix error handling
x86/ucode: Remove the collect_cpu_info() call from parse_blob()
xen/arch/x86/cpu/microcode/core.c | 53 +++++++++----------------------
1 file changed, 15 insertions(+), 38 deletions(-)
--
2.39.5
next reply other threads:[~2024-11-07 12:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 12:21 Andrew Cooper [this message]
2024-11-07 12:21 ` [PATCH 1/3] x86/ucode: Don't use microcode_update_cpu() in early_microcode_load() Andrew Cooper
2024-11-12 10:34 ` Jan Beulich
2024-11-07 12:21 ` [PATCH 2/3] x86/ucode: Fold microcode_update_cpu() and fix error handling Andrew Cooper
2024-11-12 10:45 ` Jan Beulich
2024-11-12 12:55 ` Andrew Cooper
2024-11-12 14:24 ` Jan Beulich
2024-11-07 12:21 ` [PATCH 3/3] x86/ucode: Remove the collect_cpu_info() call from parse_blob() Andrew Cooper
2024-11-07 21:58 ` Andrew Cooper
2024-11-12 10:36 ` Andrew Cooper
2024-11-12 10:49 ` Jan Beulich
2024-11-12 10:57 ` Andrew Cooper
2024-11-12 11:00 ` Jan Beulich
2024-11-08 12:12 ` [PATCH 4/3] x86/ucode: Fix cache handling in microcode_update_helper() 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=20241107122117.4073266-1-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=roger.pau@citrix.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.