Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

um: Indent time-travel help messages

Indent the help messages for time-travel to make them consistent
with the format of other help messages.

Signed-off-by: Tiwei Bie <tiwei.btw@antgroup.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>

authored by

Tiwei Bie and committed by
Johannes Berg
4c134c2a 725e9d81

+18 -18
+18 -18
arch/um/kernel/time.c
··· 986 986 __setup("time-travel", setup_time_travel); 987 987 __uml_help(setup_time_travel, 988 988 "time-travel\n" 989 - "This option just enables basic time travel mode, in which the clock/timers\n" 990 - "inside the UML instance skip forward when there's nothing to do, rather than\n" 991 - "waiting for real time to elapse. However, instance CPU speed is limited by\n" 992 - "the real CPU speed, so e.g. a 10ms timer will always fire after ~10ms wall\n" 993 - "clock (but quicker when there's nothing to do).\n" 989 + " This option just enables basic time travel mode, in which the clock/timers\n" 990 + " inside the UML instance skip forward when there's nothing to do, rather than\n" 991 + " waiting for real time to elapse. However, instance CPU speed is limited by\n" 992 + " the real CPU speed, so e.g. a 10ms timer will always fire after ~10ms wall\n" 993 + " clock (but quicker when there's nothing to do).\n" 994 994 "\n" 995 995 "time-travel=inf-cpu\n" 996 - "This enables time travel mode with infinite processing power, in which there\n" 997 - "are no wall clock timers, and any CPU processing happens - as seen from the\n" 998 - "guest - instantly. This can be useful for accurate simulation regardless of\n" 999 - "debug overhead, physical CPU speed, etc. but is somewhat dangerous as it can\n" 1000 - "easily lead to getting stuck (e.g. if anything in the system busy loops).\n" 996 + " This enables time travel mode with infinite processing power, in which there\n" 997 + " are no wall clock timers, and any CPU processing happens - as seen from the\n" 998 + " guest - instantly. This can be useful for accurate simulation regardless of\n" 999 + " debug overhead, physical CPU speed, etc. but is somewhat dangerous as it can\n" 1000 + " easily lead to getting stuck (e.g. if anything in the system busy loops).\n" 1001 1001 "\n" 1002 1002 "time-travel=ext:[ID:]/path/to/socket\n" 1003 - "This enables time travel mode similar to =inf-cpu, except the system will\n" 1004 - "use the given socket to coordinate with a central scheduler, in order to\n" 1005 - "have more than one system simultaneously be on simulated time. The virtio\n" 1006 - "driver code in UML knows about this so you can also simulate networks and\n" 1007 - "devices using it, assuming the device has the right capabilities.\n" 1008 - "The optional ID is a 64-bit integer that's sent to the central scheduler.\n\n"); 1003 + " This enables time travel mode similar to =inf-cpu, except the system will\n" 1004 + " use the given socket to coordinate with a central scheduler, in order to\n" 1005 + " have more than one system simultaneously be on simulated time. The virtio\n" 1006 + " driver code in UML knows about this so you can also simulate networks and\n" 1007 + " devices using it, assuming the device has the right capabilities.\n" 1008 + " The optional ID is a 64-bit integer that's sent to the central scheduler.\n\n"); 1009 1009 1010 1010 static int setup_time_travel_start(char *str) 1011 1011 { ··· 1022 1022 __setup("time-travel-start=", setup_time_travel_start); 1023 1023 __uml_help(setup_time_travel_start, 1024 1024 "time-travel-start=<nanoseconds>\n" 1025 - "Configure the UML instance's wall clock to start at this value rather than\n" 1026 - "the host's wall clock at the time of UML boot.\n\n"); 1025 + " Configure the UML instance's wall clock to start at this value rather than\n" 1026 + " the host's wall clock at the time of UML boot.\n\n"); 1027 1027 1028 1028 static struct kobject *bc_time_kobject; 1029 1029