From: Alejandro Vallejo <alejandro.vallejo@cloud.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v5 4/4] x86/microcode: Disable microcode update handler if DIS_MCU_UPDATE is set
Date: Wed, 5 Jul 2023 16:04:47 +0100 [thread overview]
Message-ID: <64a58691.170a0220.ef84.9a1c@mx.google.com> (raw)
In-Reply-To: <b5d551ed-6523-0ead-9c83-a7fae10eee67@suse.com>
On Wed, Jul 05, 2023 at 04:30:02PM +0200, Jan Beulich wrote:
> (maybe with an adjustment to the comment, as mentioned in the
> earlier reply)
>
> Jan
Yes, that sounds good to me. Thanks.
Alejandro
prev parent reply other threads:[~2023-07-05 15:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 15:26 [PATCH v5 0/4] Prevent attempting updates known to fail Alejandro Vallejo
2023-06-29 15:26 ` [PATCH v5 1/4] x86/microcode: Allow reading microcode revision even if it can't be updated Alejandro Vallejo
2023-07-05 14:00 ` Andrew Cooper
2023-06-29 15:26 ` [PATCH v5 2/4] x86/microcode: Ignore microcode loading interface for revision = -1 Alejandro Vallejo
2023-07-05 14:13 ` Andrew Cooper
2023-07-05 14:24 ` Jan Beulich
2023-07-05 14:28 ` Andrew Cooper
2023-07-05 14:34 ` Jan Beulich
2023-06-29 15:26 ` [PATCH v5 3/4] x86: Read MSR_ARCH_CAPS immediately after early_microcode_init() Alejandro Vallejo
2023-07-05 10:43 ` Jan Beulich
2023-07-05 13:12 ` Alejandro Vallejo
2023-07-05 13:19 ` Alejandro Vallejo
2023-06-29 15:26 ` [PATCH v5 4/4] x86/microcode: Disable microcode update handler if DIS_MCU_UPDATE is set Alejandro Vallejo
2023-07-05 10:51 ` Jan Beulich
2023-07-05 14:03 ` Alejandro Vallejo
2023-07-05 14:30 ` Jan Beulich
2023-07-05 15:04 ` Alejandro Vallejo [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=64a58691.170a0220.ef84.9a1c@mx.google.com \
--to=alejandro.vallejo@cloud.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.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.