From: Chao Gao <chao.gao@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Ashok Raj" <ashok.raj@intel.com>, "Wei Liu" <wl@xen.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>
Subject: Re: [Xen-devel] [PATCH v8 12/16] microcode: split out apply_microcode() from cpu_request_microcode()
Date: Mon, 5 Aug 2019 15:36:43 +0800 [thread overview]
Message-ID: <20190805073643.GD19492@gao-cwp> (raw)
In-Reply-To: <2c758b76-8f01-f8d0-1fc9-95b164e111b3@suse.com>
On Fri, Aug 02, 2019 at 03:40:55PM +0000, Jan Beulich wrote:
>On 01.08.2019 12:22, Chao Gao wrote:
>> --- a/xen/arch/x86/microcode.c
>> +++ b/xen/arch/x86/microcode.c
>> @@ -189,12 +189,20 @@ static DEFINE_SPINLOCK(microcode_mutex);
>>
>> DEFINE_PER_CPU(struct cpu_signature, cpu_sig);
>>
>> -struct microcode_info {
>> - unsigned int cpu;
>> - uint32_t buffer_size;
>> - int error;
>> - char buffer[1];
>> -};
>> +/*
>> + * Return a patch that covers current CPU. If there are multiple patches,
>> + * return the one with the highest revision number. Return error If no
>> + * patch is found and an error occurs during the parsing process. Otherwise
>> + * return NULL.
>> + */
>> +static struct microcode_patch *microcode_parse_blob(const char *buf,
>> + uint32_t len)
>
>Btw - you'd have less issues with line length if you omitted the
>"microcode_" prefix from static functions.
>
>> @@ -250,49 +251,88 @@ bool microcode_update_cache(struct microcode_patch *patch)
>> return true;
>> }
>>
>> -static int microcode_update_cpu(const void *buf, size_t size)
>> +/*
>> + * Load a microcode update to current CPU.
>> + *
>> + * If no patch is provided, the cached patch will be loaded. Microcode update
>> + * during APs bringup and CPU resuming falls into this case.
>> + */
>> +static int microcode_update_cpu(const struct microcode_patch *patch)
>> {
>> - int err;
>> - unsigned int cpu = smp_processor_id();
>> - struct cpu_signature *sig = &per_cpu(cpu_sig, cpu);
>> + int err = microcode_ops->collect_cpu_info(&this_cpu(cpu_sig));
>> +
>> + if ( unlikely(err) )
>> + return err;
>>
>> spin_lock(µcode_mutex);
>>
>> - err = microcode_ops->collect_cpu_info(sig);
>> - if ( likely(!err) )
>> - err = microcode_ops->cpu_request_microcode(buf, size);
>> + if ( patch )
>> + {
>> + /*
>> + * If a patch is specified, it should has newer revision than
>> + * that of the patch cached.
>> + */
>> + if ( microcode_cache &&
>> + microcode_ops->compare_patch(patch, microcode_cache) != NEW_UCODE )
>
>While I see that you've taken care of the one case in Intel specific
>code, this is again a case where I don't think you can validly call
>this hook in the Intel case. Albeit maybe it is okay, provided that
>the caller has already verified it against the CPU signature. Then
>again I wonder why this check gets done here rather than in the
>caller (next to that other check) anyway. Afaics this way you'd
>also avoid re-checking on every CPU a CPU-independent property.
As said in an earlier reply to patch 6, ->compare_patch can
be simplified a lot. Do you think it is fine to call it here
with that change?
About avoiding re-checking, we should check it with "microcode_mutex"
held otherwise we cannot ensure nobody is updating the cache. If we want
to avoid re-checking, then this lock is held for a long time from loading
on the first core to the last core. And also for early loading and late
loading, we pass 'NULL' to this function on following CPUs after the
first successful loading. I am afraid that there is no redundant checking.
Thanks
Chao
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-08-05 7:33 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 10:22 [Xen-devel] [PATCH v8 00/16] improve late microcode loading Chao Gao
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 01/16] misc/xen-ucode: Upload a microcode blob to the hypervisor Chao Gao
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 02/16] x86/microcode: always collect_cpu_info() during boot Chao Gao
2019-08-01 10:35 ` Andrew Cooper
2019-08-02 13:23 ` Jan Beulich
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 03/16] microcode/intel: extend microcode_update_match() Chao Gao
2019-08-02 13:29 ` Jan Beulich
2019-08-05 5:58 ` Chao Gao
2019-08-05 9:27 ` Jan Beulich
2019-08-05 11:51 ` Chao Gao
2019-08-05 11:50 ` Jan Beulich
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 04/16] microcode/amd: fix memory leak Chao Gao
2019-08-02 13:39 ` Jan Beulich
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 05/16] microcode/amd: distinguish old and mismatched ucode in microcode_fits() Chao Gao
2019-08-02 13:41 ` Jan Beulich
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 06/16] microcode: introduce a global cache of ucode patch Chao Gao
2019-08-02 14:46 ` Jan Beulich
2019-08-05 7:02 ` Chao Gao
2019-08-05 9:31 ` Jan Beulich
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 07/16] microcode: clean up microcode_resume_cpu Chao Gao
2019-08-02 14:57 ` Jan Beulich
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 08/16] microcode: remove struct ucode_cpu_info Chao Gao
2019-08-02 15:03 ` Jan Beulich
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 09/16] microcode: remove pointless 'cpu' parameter Chao Gao
2019-08-02 15:15 ` Jan Beulich
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 10/16] microcode/amd: call svm_host_osvw_init() in common code Chao Gao
2019-08-02 15:21 ` Jan Beulich
2019-08-05 7:05 ` Chao Gao
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 11/16] microcode: pass a patch pointer to apply_microcode() Chao Gao
2019-08-02 15:25 ` Jan Beulich
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 12/16] microcode: split out apply_microcode() from cpu_request_microcode() Chao Gao
2019-08-02 15:40 ` Jan Beulich
2019-08-05 7:36 ` Chao Gao [this message]
2019-08-05 9:38 ` Jan Beulich
2019-08-05 12:09 ` Chao Gao
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 13/16] microcode: unify loading update during CPU resuming and AP wakeup Chao Gao
2019-08-05 10:19 ` Jan Beulich
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 14/16] x86/microcode: Synchronize late microcode loading Chao Gao
2019-08-05 10:43 ` Jan Beulich
2019-08-05 13:16 ` Chao Gao
2019-08-05 13:28 ` Jan Beulich
2019-08-05 12:07 ` Jan Beulich
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 15/16] microcode: remove microcode_update_lock Chao Gao
2019-08-01 10:22 ` [Xen-devel] [PATCH v8 16/16] microcode: block #NMI handling when loading an ucode Chao Gao
2019-08-05 12:11 ` Jan Beulich
2019-08-07 7:59 ` Chao Gao
2019-08-07 8:44 ` Jan Beulich
2019-08-01 18:15 ` [Xen-devel] [PATCH v8 00/16] improve late microcode loading Andrew Cooper
2019-08-02 10:59 ` Roger Pau Monné
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=20190805073643.GD19492@gao-cwp \
--to=chao.gao@intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ashok.raj@intel.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.