[Xen-changelog] [xen-4.2-testing] docs: document "ucode=" hypervisor command line option

[Xen patchbot-4.2-testing <patchbot@xxxxxxx>]

# HG changeset patch
# User Jan Beulich <jbeulich@xxxxxxxx>
# Date 1347359647 -7200
# Node ID 8c67e5358efa8c7f4cb25f9dc1eb8c83c9dc5889
# Parent  5103702932b772a264ecd6c312b64aeb8fb55c92
docs: document "ucode=" hypervisor command line option

Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
xen-unstable changeset: 25841:7d770de90b7f
xen-unstable date: Mon Sep 10 10:13:56 UTC 2012
---


diff -r 5103702932b7 -r 8c67e5358efa docs/misc/xen-command-line.markdown
--- a/docs/misc/xen-command-line.markdown       Tue Sep 11 12:33:31 2012 +0200
+++ b/docs/misc/xen-command-line.markdown       Tue Sep 11 12:34:07 2012 +0200
@@ -785,6 +785,19 @@ pages) must also be specified via the tb
 > `= unstable | skewed`
 
 ### ucode
+> `= <integer>`
+
+Specify the CPU microcode update blob module index. When positive, this
+specifies the n-th module (in the GrUB entry, zero based) to be used
+for updating CPU micrcode. When negative, counting starts at the end of
+the modules in the GrUB entry (so with the blob commonly being last,
+one could specify `ucode=-1`). Note that the value of zero is not valid
+here (entry zero, i.e. the first module, is always the Dom0 kernel
+image). Note further that use of this option has an unspecified effect
+when used with xen.efi (there the concept of modules doesn't exist, and
+the blob gets specified via the `ucode=<filename>` config file/section
+entry; see [EFI configuration file description](efi.html)).
+
 ### unrestricted\_guest
 > `= <boolean>`
 

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog