From: "Raj, Ashok" <ashok.raj@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Kevin Tian <kevin.tian@intel.com>, Wei Liu <wei.liu2@citrix.com>,
Ashok Raj <ashok.raj@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Jun Nakajima <jun.nakajima@intel.com>,
xen-devel <xen-devel@lists.xenproject.org>,
tglx@linutronix.de, Borislav Petkov <bp@suse.de>,
Chao Gao <chao.gao@intel.com>
Subject: Re: [PATCH v4 6/6] x86/microcode: Synchronize late microcode loading
Date: Tue, 11 Dec 2018 10:16:53 -0800 [thread overview]
Message-ID: <20181211181652.GC25566@otc-nc-03> (raw)
In-Reply-To: <5C0FED5702000078002053C6@prv1-mh.provo.novell.com>
On Tue, Dec 11, 2018 at 10:01:11AM -0700, Jan Beulich wrote:
> >>> On 28.11.18 at 06:34, <chao.gao@intel.com> wrote:
> > This patch ports microcode improvement patches from linux kernel.
> >
> > Before you read any further: the early loading method is still the
> > preferred one and you should always do that. The following patch is
> > improving the late loading mechanism for long running jobs and cloud use
> > cases.
> >
> > Gather all cores and serialize the microcode update on them by doing it
> > one-by-one to make the late update process as reliable as possible and
> > avoid potential issues caused by the microcode update.
>
> So you still didn't switch to process cores or at the very least
> sockets in parallel?
Let me sync with Gao on this.. we did do a patch for upstream kernel
but Boris wasn't interested in talking any patches to improve
live microcode update because there is no report of breakage with what we do
today with the big hammer approach. Plus the preferred path should be BIOS,
next is early load and 3rd option is live update.
But since this is xen a different source base you are free to make
those changes.
BTW: Apart from the fact its ugly and take a loooong time to complete, do you
have any practical isssues you want to highlight? maybe that can
help upstream as well.
Cheers,
Ashok
>
> Jan
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-12-11 18:16 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 5:34 [PATCH v4 0/6] improve late microcode loading Chao Gao
2018-11-28 5:34 ` [PATCH v4 1/6] microcode/intel: extend microcode_update_match() Chao Gao
2018-11-28 10:58 ` Roger Pau Monné
2018-11-29 2:00 ` Chao Gao
2018-11-29 9:14 ` Roger Pau Monné
2018-11-28 5:34 ` [PATCH v4 2/6] microcode: save all microcodes which pass sanity check Chao Gao
2018-11-28 12:00 ` Roger Pau Monné
2018-11-29 2:40 ` Chao Gao
2018-11-29 9:22 ` Roger Pau Monné
2018-11-30 7:55 ` Chao Gao
2018-11-30 9:32 ` Jan Beulich
2019-01-15 15:07 ` Andrew Cooper
2018-12-04 22:39 ` Woods, Brian
2018-12-05 7:38 ` Chao Gao
2018-11-29 10:19 ` Jan Beulich
2019-01-15 15:15 ` Andrew Cooper
2018-11-28 5:34 ` [PATCH v4 3/6] microcode: delete 'mc' field from struct ucode_cpu_info Chao Gao
2018-11-28 12:32 ` Roger Pau Monné
2018-11-28 5:34 ` [PATCH v4 4/6] microcode: don't call apply_microcode() in cpu_request_microcode() Chao Gao
2018-11-28 15:02 ` Roger Pau Monné
2018-11-29 4:28 ` Chao Gao
2018-11-29 9:46 ` Roger Pau Monné
2018-11-30 8:57 ` Chao Gao
2018-11-30 9:38 ` Jan Beulich
2018-11-28 5:34 ` [PATCH v4 5/6] microcode: delete microcode pointer and size from microcode_info Chao Gao
2018-11-28 15:04 ` Roger Pau Monné
2018-11-28 5:34 ` [PATCH v4 6/6] x86/microcode: Synchronize late microcode loading Chao Gao
2018-11-28 15:22 ` Roger Pau Monné
2018-11-29 4:43 ` Chao Gao
2018-11-29 9:56 ` Roger Pau Monné
2018-11-29 22:43 ` Boris Ostrovsky
2018-11-30 9:46 ` Jan Beulich
2018-11-30 16:49 ` Boris Ostrovsky
2018-11-30 9:01 ` Chao Gao
2019-01-15 15:24 ` Andrew Cooper
2019-01-15 16:24 ` Roger Pau Monné
2018-12-11 17:01 ` Jan Beulich
2018-12-11 18:16 ` Raj, Ashok [this message]
2018-12-12 7:26 ` Jan Beulich
2018-12-13 2:10 ` Boris Ostrovsky
2018-12-12 4:53 ` Chao Gao
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=20181211181652.GC25566@otc-nc-03 \
--to=ashok.raj@intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@suse.de \
--cc=chao.gao@intel.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=tglx@linutronix.de \
--cc=wei.liu2@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.