From: Chao Gao <chao.gao@intel.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH v5 6/8] microcode: delete microcode pointer and size from microcode_info
Date: Tue, 29 Jan 2019 22:11:22 +0800 [thread overview]
Message-ID: <20190129141120.GA9218@gao-cwp> (raw)
In-Reply-To: <20190129101051.uoqvzsphjouwwyz2@mac>
On Tue, Jan 29, 2019 at 11:10:51AM +0100, Roger Pau Monné wrote:
>On Mon, Jan 28, 2019 at 03:06:48PM +0800, Chao Gao wrote:
>> microcode pointer and size were passed to other CPUs to parse
>> microcode locally. Now, parsing microcode is done on one CPU.
>> Other CPUs needn't parse the microcode blob; the pointer and
>> size can be removed.
>>
>> Signed-off-by: Chao Gao <chao.gao@intel.com>
>> ---
>> xen/arch/x86/microcode.c | 33 +++++++++++++++++----------------
>> 1 file changed, 17 insertions(+), 16 deletions(-)
>>
>> diff --git a/xen/arch/x86/microcode.c b/xen/arch/x86/microcode.c
>> index 936f0b8..3c2274f 100644
>> --- a/xen/arch/x86/microcode.c
>> +++ b/xen/arch/x86/microcode.c
>> @@ -190,9 +190,7 @@ DEFINE_PER_CPU(struct ucode_cpu_info, ucode_cpu_info);
>>
>> struct microcode_info {
>> unsigned int cpu;
>
>I think cpu can also be removed as my previous reply to patch 5, at
>which point you only need to store an error? In which case you should
>also remove this struct then.
I agree to all your comments on this patch. Will correct them.
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-01-29 14:07 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 7:06 [PATCH v5 0/8] improve late microcode loading Chao Gao
2019-01-28 7:06 ` [PATCH v5 1/8] microcode/intel: remove redundent check against ucode size Chao Gao
2019-01-28 16:40 ` Roger Pau Monné
2019-01-29 10:26 ` Jan Beulich
2019-01-29 13:34 ` Chao Gao
2019-01-28 7:06 ` [PATCH v5 2/8] microcode/intel: extend microcode_update_match() Chao Gao
2019-01-28 16:55 ` Roger Pau Monné
2019-01-28 17:00 ` Jan Beulich
2019-01-29 10:41 ` Jan Beulich
2019-01-29 13:52 ` Chao Gao
2019-01-28 7:06 ` [PATCH v5 3/8] microcode: introduce the global microcode cache Chao Gao
2019-01-28 17:39 ` Roger Pau Monné
2019-01-29 4:41 ` Chao Gao
2019-01-29 8:56 ` Roger Pau Monné
2019-02-08 11:41 ` Jan Beulich
2019-02-11 3:59 ` Chao Gao
2019-02-11 13:16 ` Jan Beulich
2019-01-28 7:06 ` [PATCH v5 4/8] microcode: delete 'mc' field from struct ucode_cpu_info Chao Gao
2019-01-29 9:25 ` Roger Pau Monné
2019-01-29 13:27 ` Chao Gao
2019-01-28 7:06 ` [PATCH v5 5/8] microcode: split out apply_microcode() from cpu_request_microcode() Chao Gao
2019-01-29 9:58 ` Roger Pau Monné
2019-01-29 12:47 ` Chao Gao
2019-02-08 15:58 ` Jan Beulich
2019-01-28 7:06 ` [PATCH v5 6/8] microcode: delete microcode pointer and size from microcode_info Chao Gao
2019-01-29 10:10 ` Roger Pau Monné
2019-01-29 14:11 ` Chao Gao [this message]
2019-01-28 7:06 ` [PATCH v5 7/8] x86/microcode: Synchronize late microcode loading Chao Gao
2019-01-29 10:37 ` Roger Pau Monné
2019-01-29 10:45 ` Jan Beulich
2019-01-30 13:44 ` Chao Gao
2019-02-08 16:29 ` Jan Beulich
2019-02-11 5:40 ` Chao Gao
2019-02-11 13:23 ` Jan Beulich
2019-02-11 13:35 ` Juergen Gross
2019-02-11 15:28 ` Raj, Ashok
2019-02-11 16:49 ` Jan Beulich
2019-01-28 7:06 ` [PATCH v5 8/8] microcode: update microcode on cores in parallel Chao Gao
2019-01-29 11:27 ` Roger Pau Monné
2019-01-30 13:36 ` Chao Gao
2019-02-12 12:51 ` Jan Beulich
2019-02-12 13:25 ` Roger Pau Monné
2019-02-12 13:55 ` Jan Beulich
2019-02-13 2:30 ` Chao Gao
2019-02-13 7:20 ` Jan Beulich
2019-02-13 8:50 ` Chao Gao
2019-02-13 10:05 ` Jan Beulich
2019-01-29 11:31 ` [PATCH v5 0/8] improve late microcode loading Roger Pau Monné
2019-01-29 12:11 ` Chao Gao
2019-01-29 14:17 ` 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=20190129141120.GA9218@gao-cwp \
--to=chao.gao@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--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.