Add TSC as another clocksource that can be used, plus a mention to the maxcpus parameter and that it requires being explicitly set.
Signed-off-by: Joao Martins <joao.m.mart...@oracle.com> --- Cc: Andrew Cooper <andrew.coop...@citrix.com> Cc: Jan Beulich <jbeul...@suse.com> New in v3. --- docs/misc/xen-command-line.markdown | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/misc/xen-command-line.markdown b/docs/misc/xen-command-line.markdown index 3a250cb..210927f 100644 --- a/docs/misc/xen-command-line.markdown +++ b/docs/misc/xen-command-line.markdown @@ -264,9 +264,13 @@ minimum of 32M, subject to a suitably aligned and sized contiguous region of memory being available. ### clocksource -> `= pit | hpet | acpi` +> `= pit | hpet | acpi | tsc` If set, override Xen's default choice for the platform timer. +Having TSC as platform timer requires being explicitly set. +This is because TSC can only be safely used if CPU hotplug isn't performed on +the system. In some platforms, "maxcpus" parameter may require further +adjustment to the number of online cpus. ### cmci-threshold > `= <integer>` -- 2.1.4 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
