From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Eslam Elnikety <elnikety@amazon.com>, Jan Beulich <jbeulich@suse.com>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
"Julien Grall" <julien@xen.org>, "Wei Liu" <wl@xen.org>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"George Dunlap" <George.Dunlap@eu.citrix.com>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"Paul Durrant" <pdurrant@amazon.co.uk>,
xen-devel@lists.xenproject.org,
"David Woodhouse" <dwmw@amazon.co.uk>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH] x86/microcode: Support builtin CPU microcode
Date: Fri, 13 Dec 2019 13:57:52 +0000 [thread overview]
Message-ID: <2d23e5e7-fe5d-3446-57e5-6559cd8e7258@citrix.com> (raw)
In-Reply-To: <ff5b0699-5010-fabc-f7fd-2d40f8c56644@amazon.com>
On 12/12/2019 22:13, Eslam Elnikety wrote:
>>> Second, there is often need to couple a Xen build with a minimum
>>> microcode patch level. Having the microcode built within the Xen image
>>> itself is a streamlined, natural way of achieving that.
>>
>> Okay, I can accept this as a reason, to some degree at least. Yet
>> as said elsewhere, I don't think you want then to override a
>> possible "external" ucode module with the builtin blobs. Instead
>> the newest of everything that's available should then be loaded.
>
> Extending Xen to work around tools shortcomings is absolutely not what
> I have in mind. I should have started with the second reason. Read
> this as: Xen relies on a minimum microcode feature set, and it makes
> sense to couple both in one binary. This coupling just happens to
> provide an added benefit in the face of tools shortcoming.
Do we have anything which strictly relies on a minimum version?
I can definitely see the value of bundling the ucode and saying "this is
the minimum we will tolerate" from a supportability point of view.
There is also value when it comes to easier SRTM/DRTM measurements of
the system in question, including cases where Xen sits on a boot ROM
rather than on disk.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-12-13 21:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 8:41 [Xen-devel] [PATCH] x86/microcode: Support builtin CPU microcode Eslam Elnikety
2019-12-09 15:19 ` Andrew Cooper
2019-12-09 21:49 ` Eslam Elnikety
2019-12-10 9:21 ` Jan Beulich
2019-12-10 22:40 ` Eslam Elnikety
2019-12-11 9:47 ` Jan Beulich
2019-12-12 22:13 ` Eslam Elnikety
2019-12-13 13:57 ` Andrew Cooper [this message]
2019-12-13 20:15 ` Tamas K Lengyel
2019-12-14 0:37 ` Andrew Cooper
2019-12-15 16:10 ` Tamas K Lengyel
2019-12-17 22:41 ` Eslam Elnikety
2019-12-17 22:44 ` Andrew Cooper
2019-12-13 13:40 ` Andrew Cooper
2019-12-18 0:29 ` Eslam Elnikety
2019-12-10 9:37 ` Jan Beulich
2019-12-10 23:18 ` Eslam Elnikety
2019-12-11 9:54 ` Jan Beulich
2019-12-12 22:17 ` Eslam Elnikety
2019-12-13 9:58 ` Jan Beulich
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=2d23e5e7-fe5d-3446-57e5-6559cd8e7258@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=dwmw@amazon.co.uk \
--cc=elnikety@amazon.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=pdurrant@amazon.co.uk \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--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.