cmdline: Document console=dtuart option

Document the default console= option on Arm and RISC-V that is
"dtuart" indicating a generic UART parsed from a device tree or
ACPI SPCR table. This serial utilizes SERHND_DTUART handle.

Take the opportunity to:
 - fix documented x86 default to vga to match OPT_CONSOLE_STR,
 - mark dtuart option as available on RISC-V,
 - document fall back to /chosen/stdout-path.

Signed-off-by: Michal Orzel <michal.orzel@amd.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
This commit is contained in:
Michal Orzel committed 2026-09-15 17:13:02 +02:00
1 parent 4830ddbee3
commit 422484e55c
1 file changed
+10 -3
+10 -3
View File
@@ -438,9 +438,10 @@ The following are examples of correct specifications:
Specify the size of the console ring buffer.
### console
> `= List of [ vga | com1[H,L] | com2[H,L] | pv | dbgp | ehci | xhci | none ]`
> `= List of [ vga | com1[H,L] | com2[H,L] | pv | dbgp | ehci | xhci | dtuart | none ]`
> Default: `console=com1,vga`
> Default (x86): `console=vga`
> Default (Arm, RISC-V): `console=dtuart`
Specify which console(s) Xen should use.
@@ -462,6 +463,10 @@ compiled with `CONFIG_XEN_GUEST` enabled.
`xhci` indicates that Xen should use a USB3 debug port.
`dtuart` indicates that Xen should use a generic UART (parsed from a device
tree or ACPI SPCR table). Only available if Xen was compiled with
`CONFIG_GENERIC_UART_INIT` enabled.
`none` indicates that Xen should not use a console. This option only
makes sense on its own.
@@ -1077,13 +1082,15 @@ affinities to prefer but be not limited to the specified node(s).
Pin dom0 vcpus to their respective pcpus
### dtuart (ARM)
### dtuart (ARM, RISC-V)
> `= path [:options]`
> Default: `""`
Specify the full path in the device tree for the UART. If the path doesn't
start with `/`, it is assumed to be an alias. The options are device specific.
If the option is left empty, Xen will try to probe the device from the DT
property /chosen/stdout-path if present.
### e820-mtrr-clip (x86)
> `= <boolean>`
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.