SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On 01/26/10 04:52 PM, Huay-Yong Wang wrote: > are only available > for x86 platforms (See PSARC 2008/382 Fast Reboot) > Note that the -e option (boot environments) is not yet > supported on SPARC. This project introduces no > new interface and I believe this qualify as self-review. > I will be marking the case closed approved automatic. > If anyone feels that this need to be promoted to a fast track > please let me know. > > The project team is requesting a patch/micro release binding. > An updated reboot(1M) manpage is included here. > > > Yay! +100! - Garrett
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
> >I am sponsoring this fasttrack for Chris Kiick. > >This project implements fast reboot support >for SPARC. Specifically, the -f and -p options >in reboot(1M) is now supported on SPARC. >Previously these options are only available >for x86 platforms (See PSARC 2008/382 Fast Reboot) >Note that the -e option (boot environments) is not yet >supported on SPARC. This project introduces no >new interface and I believe this qualify as self-review. >I will be marking the case closed approved automatic. >If anyone feels that this need to be promoted to a fast track >please let me know. +1 Casper
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
I am sponsoring this fasttrack for Chris Kiick. This project implements fast reboot support for SPARC. Specifically, the -f and -p options in reboot(1M) is now supported on SPARC. Previously these options are only available for x86 platforms (See PSARC 2008/382 Fast Reboot) Note that the -e option (boot environments) is not yet supported on SPARC. This project introduces no new interface and I believe this qualify as self-review. I will be marking the case closed approved automatic. If anyone feels that this need to be promoted to a fast track please let me know. The project team is requesting a patch/micro release binding. An updated reboot(1M) manpage is included here. --- cut here --- System Administration Commands reboot(1M) NAME reboot - restart the operating system SYNOPSIS /usr/sbin/reboot [-dlnq] [-f | -p] [boot_arguments] /usr/sbin/reboot [-f [-e environment] | -p] [-dlnq] [boot_arguments] DESCRIPTION The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel. On x86 systems, when the -f flag is specified, the running kernel will load the next kernel into memory, then transfer control to the newly loaded kernel. This form of reboot is shown in the second synopsis, above. Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending loss of service. See shutdown(1M) for details. The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On x86 systems, reboot may also update the boot archive as needed to ensure a successful reboot. The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present. Normally, the system reboots itself at power-up or after crashes. OPTIONS The following options are supported: -d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps. SunOS 5.11 Last change: 26 Jan 20101 System Administration Commands reboot(1M) -e If -f is present, reboot to the specified boot environ- ment. This option is currently available only on x86 systems. -f For x86 systems: Fast reboot, bypassing firmware and boot loader. The new kernel will be loaded into memory by the running kernel, and control will be transferred to the newly loaded ker- nel. If disk or kernel arguments are specified, they must be specified before other boot arguments. For SPARC systems: Speeds up rebooting by skipping some POST tests. The service svc:/system/boot-config:default is enabled by default. It requires solaris.system.shutdown as action_authorization and value_authorization. When the config/fastreboot_default property is set to true, reboot will behave as reboot -f. The value of this pro- perty can be changed using svccfg(1M) and svcadm(1M), to control the default reboot behavior. See EXAMPLES for details. -l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot. -n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to sync file systems. -p Reboot to prom. This flag can be used to reboot the sys- tem through firmware without changing the default reboot SunOS 5.11 Last change: 26 Jan 20102 System Administration Commands reboot(1M) behavior as denoted by the config/fastreboot_default property setting in system/boot-config service. The -p and -f options are mutually exclusive. -q Quick. Reboot quickly and ungracefully, without shutting down running processes first. OPERANDS The following operands are supported: boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pa
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
I presume init(1M) will also need to be updated in the "6" section to remove the x86-specific reference to fast reboot: 6 Stop the operating system and reboot to the state defined by the initdefault entry in /etc/inittab. On x86 systems, service svc:/system/boot-config:default is enabled by default. When the config/fastreboot_default property is set to true, init 6 will bypass the firmware. Thanks, Brian On 01/27/10 12:52 AM, Huay-Yong Wang wrote: > I am sponsoring this fasttrack for Chris Kiick. > > This project implements fast reboot support > for SPARC. Specifically, the -f and -p options > in reboot(1M) is now supported on SPARC. > Previously these options are only available > for x86 platforms (See PSARC 2008/382 Fast Reboot) > Note that the -e option (boot environments) is not yet > supported on SPARC. This project introduces no > new interface and I believe this qualify as self-review. > I will be marking the case closed approved automatic. > If anyone feels that this need to be promoted to a fast track > please let me know. > > The project team is requesting a patch/micro release binding. > An updated reboot(1M) manpage is included here. > > > --- cut here --- > > System Administration Commands reboot(1M) > > > > NAME > reboot - restart the operating system > > SYNOPSIS > /usr/sbin/reboot [-dlnq] [-f | -p] [boot_arguments] > > > /usr/sbin/reboot [-f [-e environment] | -p] [-dlnq] [boot_arguments] > > > DESCRIPTION > The reboot utility restarts the kernel. The kernel is loaded > into memory by the PROM monitor, which transfers control to > the loaded kernel. > > > On x86 systems, when the -f flag is specified, the running > kernel will load the next kernel into memory, then transfer > control to the newly loaded kernel. This form of reboot is > shown in the second synopsis, above. > > > Although reboot can be run by the super-user at any time, > shutdown(1M) is normally used first to warn all users logged > in of the impending loss of service. See shutdown(1M) for > details. > > > The reboot utility performs a sync(1M) operation on the > disks, and then a multi-user reboot is initiated. See > init(1M) for details. On x86 systems, reboot may also update > the boot archive as needed to ensure a successful reboot. > > > The reboot utility normally logs the reboot to the system > log daemon, syslogd(1M), and places a shutdown record in the > login accounting file /var/adm/wtmpx. These actions are > inhibited if the -n or -q options are present. > > > Normally, the system reboots itself at power-up or after > crashes. > > OPTIONS > The following options are supported: > > -d > > Force a system crash dump before rebooting. See > dumpadm(1M) for information on configuring system crash > dumps. > > > > > SunOS 5.11 Last change: 26 Jan 20101 > > > > > > > System Administration Commands reboot(1M) > > > > -e > > If -f is present, reboot to the specified boot environ- > ment. > > This option is currently available only on x86 systems. > > > -f > > For x86 systems: > > Fast reboot, bypassing firmware and boot loader. The new > kernel will be loaded into memory by the running kernel, > and control will be transferred to the newly loaded ker- > nel. If disk or kernel arguments are specified, they > must be specified before other boot arguments. > > For SPARC systems: > > Speeds up rebooting by skipping some POST tests. > > The service svc:/system/boot-config:default is enabled > by default. It requires solaris.system.shutdown as > action_authorization and value_authorization. When the > config/fastreboot_default property is set to true, > reboot will behave as reboot -f. The value of this pro- > perty can be changed using svccfg(1M) and svcadm(1M), to > control the default reboot behavior. > > See EXAMPLES for details. > > > -l > > Suppress sending a message to the system log daemon, > syslogd(1M) about who executed reboot. > > > -n > > Avoid calling sync(2) and do not log the reboot to > syslogd(1M) or to /var/adm/wtmpx. The kernel still > attempts to sync filesystems prior to reboot, except if > the -d option is also present. If -d is used with -n, > the kernel does not attempt to sync file systems. > > > -p > > Reboot to prom. This flag can be used to reboot the
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
Thank you guys for the great work! When I filed 2008/382 I requested minor binding only. This case is requesting patch/micro release binding. Will the binding difference need to be reflected in case 2008/382? Will there be compatibility concerns as 2008/382 added devo_quiesce to dev_ops? Sherry On Tue, Jan 26, 2010 at 04:52:48PM -0800, Huay-Yong Wang wrote: > > I am sponsoring this fasttrack for Chris Kiick. > > This project implements fast reboot support > for SPARC. Specifically, the -f and -p options > in reboot(1M) is now supported on SPARC. > Previously these options are only available > for x86 platforms (See PSARC 2008/382 Fast Reboot) > Note that the -e option (boot environments) is not yet > supported on SPARC. This project introduces no > new interface and I believe this qualify as self-review. > I will be marking the case closed approved automatic. > If anyone feels that this need to be promoted to a fast track > please let me know. > > The project team is requesting a patch/micro release binding. > An updated reboot(1M) manpage is included here. > > > --- cut here --- > > System Administration Commands reboot(1M) > > > > NAME > reboot - restart the operating system > > SYNOPSIS > /usr/sbin/reboot [-dlnq] [-f | -p] [boot_arguments] > > > /usr/sbin/reboot [-f [-e environment] | -p] [-dlnq] [boot_arguments] > > > DESCRIPTION > The reboot utility restarts the kernel. The kernel is loaded > into memory by the PROM monitor, which transfers control to > the loaded kernel. > > > On x86 systems, when the -f flag is specified, the running > kernel will load the next kernel into memory, then transfer > control to the newly loaded kernel. This form of reboot is > shown in the second synopsis, above. > > > Although reboot can be run by the super-user at any time, > shutdown(1M) is normally used first to warn all users logged > in of the impending loss of service. See shutdown(1M) for > details. > > > The reboot utility performs a sync(1M) operation on the > disks, and then a multi-user reboot is initiated. See > init(1M) for details. On x86 systems, reboot may also update > the boot archive as needed to ensure a successful reboot. > > > The reboot utility normally logs the reboot to the system > log daemon, syslogd(1M), and places a shutdown record in the > login accounting file /var/adm/wtmpx. These actions are > inhibited if the -n or -q options are present. > > > Normally, the system reboots itself at power-up or after > crashes. > > OPTIONS > The following options are supported: > > -d > > Force a system crash dump before rebooting. See > dumpadm(1M) for information on configuring system crash > dumps. > > > > > SunOS 5.11 Last change: 26 Jan 20101 > > > > > > > System Administration Commands reboot(1M) > > > > -e > > If -f is present, reboot to the specified boot environ- > ment. > > This option is currently available only on x86 systems. > > > -f > > For x86 systems: > > Fast reboot, bypassing firmware and boot loader. The new > kernel will be loaded into memory by the running kernel, > and control will be transferred to the newly loaded ker- > nel. If disk or kernel arguments are specified, they > must be specified before other boot arguments. > > For SPARC systems: > > Speeds up rebooting by skipping some POST tests. > > The service svc:/system/boot-config:default is enabled > by default. It requires solaris.system.shutdown as > action_authorization and value_authorization. When the > config/fastreboot_default property is set to true, > reboot will behave as reboot -f. The value of this pro- > perty can be changed using svccfg(1M) and svcadm(1M), to > control the default reboot behavior. > > See EXAMPLES for details. > > > -l > > Suppress sending a message to the system log daemon, > syslogd(1M) about who executed reboot. > > > -n > > Avoid calling sync(2) and do not log the reboot to > syslogd(1M) or to /var/adm/wtmpx. The kernel still > attempts to sync filesystems prior to reboot, except if > the -d option is also present. If -d is used with -n, > the kernel does not attempt to sync file systems. > > > -p > > Reboot to prom. This flag can be used to reboot the sys- > tem through firmware without changing the default reboot > > > > SunOS 5.11 Last change: 26 Jan 20102 > > > > > > > System Administration Co
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On 01/27/10 11:23 AM, Sherry Moore wrote: > Thank you guys for the great work! > > When I filed 2008/382 I requested minor binding only. This case is > requesting patch/micro release binding. Will the binding difference > need to be reflected in case 2008/382? Will there be compatibility > concerns as 2008/382 added devo_quiesce to dev_ops? > Oh, I didn't see Patch binding. I'd like to retract my +1 if this is Patch. If its *Minor* binding, then I'm very happy. - Garrett > Sherry > > On Tue, Jan 26, 2010 at 04:52:48PM -0800, Huay-Yong Wang wrote: > >> I am sponsoring this fasttrack for Chris Kiick. >> >> This project implements fast reboot support >> for SPARC. Specifically, the -f and -p options >> in reboot(1M) is now supported on SPARC. >> Previously these options are only available >> for x86 platforms (See PSARC 2008/382 Fast Reboot) >> Note that the -e option (boot environments) is not yet >> supported on SPARC. This project introduces no >> new interface and I believe this qualify as self-review. >> I will be marking the case closed approved automatic. >> If anyone feels that this need to be promoted to a fast track >> please let me know. >> >> The project team is requesting a patch/micro release binding. >> An updated reboot(1M) manpage is included here. >> >> >> --- cut here --- >> >> System Administration Commands reboot(1M) >> >> >> >> NAME >> reboot - restart the operating system >> >> SYNOPSIS >> /usr/sbin/reboot [-dlnq] [-f | -p] [boot_arguments] >> >> >> /usr/sbin/reboot [-f [-e environment] | -p] [-dlnq] [boot_arguments] >> >> >> DESCRIPTION >> The reboot utility restarts the kernel. The kernel is loaded >> into memory by the PROM monitor, which transfers control to >> the loaded kernel. >> >> >> On x86 systems, when the -f flag is specified, the running >> kernel will load the next kernel into memory, then transfer >> control to the newly loaded kernel. This form of reboot is >> shown in the second synopsis, above. >> >> >> Although reboot can be run by the super-user at any time, >> shutdown(1M) is normally used first to warn all users logged >> in of the impending loss of service. See shutdown(1M) for >> details. >> >> >> The reboot utility performs a sync(1M) operation on the >> disks, and then a multi-user reboot is initiated. See >> init(1M) for details. On x86 systems, reboot may also update >> the boot archive as needed to ensure a successful reboot. >> >> >> The reboot utility normally logs the reboot to the system >> log daemon, syslogd(1M), and places a shutdown record in the >> login accounting file /var/adm/wtmpx. These actions are >> inhibited if the -n or -q options are present. >> >> >> Normally, the system reboots itself at power-up or after >> crashes. >> >> OPTIONS >> The following options are supported: >> >> -d >> >> Force a system crash dump before rebooting. See >> dumpadm(1M) for information on configuring system crash >> dumps. >> >> >> >> >> SunOS 5.11 Last change: 26 Jan 20101 >> >> >> >> >> >> >> System Administration Commands reboot(1M) >> >> >> >> -e >> >> If -f is present, reboot to the specified boot environ- >> ment. >> >> This option is currently available only on x86 systems. >> >> >> -f >> >> For x86 systems: >> >> Fast reboot, bypassing firmware and boot loader. The new >> kernel will be loaded into memory by the running kernel, >> and control will be transferred to the newly loaded ker- >> nel. If disk or kernel arguments are specified, they >> must be specified before other boot arguments. >> >> For SPARC systems: >> >> Speeds up rebooting by skipping some POST tests. >> >> The service svc:/system/boot-config:default is enabled >> by default. It requires solaris.system.shutdown as >> action_authorization and value_authorization. When the >> config/fastreboot_default property is set to true, >> reboot will behave as reboot -f. The value of this pro- >> perty can be changed using svccfg(1M) and svcadm(1M), to >> control the default reboot behavior. >> >> See EXAMPLES for details. >> >> >> -l >> >> Suppress sending a message to the system log daemon, >> syslogd(1M) about who executed reboot. >> >> >> -n >> >> Avoid calling sync(2) and do not log the reboot to >> syslogd(1M) or to /var/adm/wtmpx. The kernel still >> attempts to sync filesystems prior to reboot, except if >> the -d option is also present. If -d is used
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On 01/27/10 01:44 PM, Huay-Yong Wang wrote: > > I spoke to Chris and the case is amended for > minor binding only. Chris will send > out an update to the init(1M) manpage shortly. > Thanks. Thanks for the clarification. I reaffirm my +1 (or 100). One question: is this (esp. fast-reboot-on-panic) going to be enabled by default? (I have raised concerns about fast-reboot-on-panic and risks associated with it elsewhere. Let me know if you want to hear about them.) - Garrett > > > On 01/27/10 11:39, Garrett D'Amore wrote: >> On 01/27/10 11:23 AM, Sherry Moore wrote: >>> Thank you guys for the great work! >>> >>> When I filed 2008/382 I requested minor binding only. This case is >>> requesting patch/micro release binding. Will the binding difference >>> need to be reflected in case 2008/382? Will there be compatibility >>> concerns as 2008/382 added devo_quiesce to dev_ops? >> >> Oh, I didn't see Patch binding. >> >> I'd like to retract my +1 if this is Patch. If its *Minor* binding, >> then I'm very happy. >> >> - Garrett >> >>> Sherry >>> >>> On Tue, Jan 26, 2010 at 04:52:48PM -0800, Huay-Yong Wang wrote: I am sponsoring this fasttrack for Chris Kiick. This project implements fast reboot support for SPARC. Specifically, the -f and -p options in reboot(1M) is now supported on SPARC. Previously these options are only available for x86 platforms (See PSARC 2008/382 Fast Reboot) Note that the -e option (boot environments) is not yet supported on SPARC. This project introduces no new interface and I believe this qualify as self-review. I will be marking the case closed approved automatic. If anyone feels that this need to be promoted to a fast track please let me know. The project team is requesting a patch/micro release binding. An updated reboot(1M) manpage is included here. --- cut here --- System Administration Commands reboot(1M) NAME reboot - restart the operating system SYNOPSIS /usr/sbin/reboot [-dlnq] [-f | -p] [boot_arguments] /usr/sbin/reboot [-f [-e environment] | -p] [-dlnq] [boot_arguments] DESCRIPTION The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel. On x86 systems, when the -f flag is specified, the running kernel will load the next kernel into memory, then transfer control to the newly loaded kernel. This form of reboot is shown in the second synopsis, above. Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending loss of service. See shutdown(1M) for details. The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On x86 systems, reboot may also update the boot archive as needed to ensure a successful reboot. The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present. Normally, the system reboots itself at power-up or after crashes. OPTIONS The following options are supported: -d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps. SunOS 5.11 Last change: 26 Jan 20101 System Administration Commands reboot(1M) -e If -f is present, reboot to the specified boot environ- ment. This option is currently available only on x86 systems. -f For x86 systems: Fast reboot, bypassing firmware and boot loader. The new kernel will be loaded into memory by the running kernel, and control will be transferred to the newly loaded ker- nel. If disk or kernel arguments are specified, they must be specified before other boot arguments. For SPARC systems: Speeds up rebooting by skipping some POST tests. The service svc:/system/boot-config:default is enabled by default. It requires solaris.system.shutdown as
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
> -f > > For x86 systems: > > Fast reboot, bypassing firmware and boot loader. The new > kernel will be loaded into memory by the running kernel, > and control will be transferred to the newly loaded ker- > nel. If disk or kernel arguments are specified, they > must be specified before other boot arguments. > > For SPARC systems: > > Speeds up rebooting by skipping some POST tests. > Could you elaborate a bit more on what POST tests are skipped for fast reboot on SPARC, and what are not? Thanks, Robin > The service svc:/system/boot-config:default is enabled > by default. It requires solaris.system.shutdown as > action_authorization and value_authorization. When the > config/fastreboot_default property is set to true, > reboot will behave as reboot -f. The value of this pro- > perty can be changed using svccfg(1M) and svcadm(1M), to > control the default reboot behavior. > > See EXAMPLES for details. > >
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On 01/27/10 02:13 PM, Zhijun Fu wrote: > >> -f >> >> For x86 systems: >> >> Fast reboot, bypassing firmware and boot loader. The new >> kernel will be loaded into memory by the running kernel, >> and control will be transferred to the newly loaded ker- >> nel. If disk or kernel arguments are specified, they >> must be specified before other boot arguments. >>For SPARC systems: >> >> Speeds up rebooting by skipping some POST tests. > Could you elaborate a bit more on what POST tests are skipped > for fast reboot on SPARC, and what are not? If it works like x86 fast reboot, I'd expect "all of them" are skipped. In x86, the old kernel directly loads and executes the new one. The system firmware (including POST and BIOS or OBP in the case of SPARC) would never realize that a different kernel was executing. - Garrett
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
>On 01/27/10 01:44 PM, Huay-Yong Wang wrote: >> >> I spoke to Chris and the case is amended for >> minor binding only. Chris will send >> out an update to the init(1M) manpage shortly. >> Thanks. > >Thanks for the clarification. I reaffirm my +1 (or 100). Same here. (Rebooting my SPARC systems often) Cas[er
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
I spoke to Chris and the case is amended for minor binding only. Chris will send out an update to the init(1M) manpage shortly. Thanks. On 01/27/10 11:39, Garrett D'Amore wrote: > On 01/27/10 11:23 AM, Sherry Moore wrote: >> Thank you guys for the great work! >> >> When I filed 2008/382 I requested minor binding only. This case is >> requesting patch/micro release binding. Will the binding difference >> need to be reflected in case 2008/382? Will there be compatibility >> concerns as 2008/382 added devo_quiesce to dev_ops? >> > > Oh, I didn't see Patch binding. > > I'd like to retract my +1 if this is Patch. If its *Minor* binding, > then I'm very happy. > > - Garrett > >> Sherry >> >> On Tue, Jan 26, 2010 at 04:52:48PM -0800, Huay-Yong Wang wrote: >> >>> I am sponsoring this fasttrack for Chris Kiick. >>> >>> This project implements fast reboot support >>> for SPARC. Specifically, the -f and -p options >>> in reboot(1M) is now supported on SPARC. >>> Previously these options are only available >>> for x86 platforms (See PSARC 2008/382 Fast Reboot) >>> Note that the -e option (boot environments) is not yet >>> supported on SPARC. This project introduces no >>> new interface and I believe this qualify as self-review. >>> I will be marking the case closed approved automatic. >>> If anyone feels that this need to be promoted to a fast track >>> please let me know. >>> >>> The project team is requesting a patch/micro release binding. >>> An updated reboot(1M) manpage is included here. >>> >>> >>> --- cut here --- >>> >>> System Administration Commands reboot(1M) >>> >>> >>> >>> NAME >>> reboot - restart the operating system >>> >>> SYNOPSIS >>> /usr/sbin/reboot [-dlnq] [-f | -p] [boot_arguments] >>> >>> >>> /usr/sbin/reboot [-f [-e environment] | -p] [-dlnq] >>> [boot_arguments] >>> >>> >>> DESCRIPTION >>> The reboot utility restarts the kernel. The kernel is loaded >>> into memory by the PROM monitor, which transfers control to >>> the loaded kernel. >>> >>> >>> On x86 systems, when the -f flag is specified, the running >>> kernel will load the next kernel into memory, then transfer >>> control to the newly loaded kernel. This form of reboot is >>> shown in the second synopsis, above. >>> >>> >>> Although reboot can be run by the super-user at any time, >>> shutdown(1M) is normally used first to warn all users logged >>> in of the impending loss of service. See shutdown(1M) for >>> details. >>> >>> >>> The reboot utility performs a sync(1M) operation on the >>> disks, and then a multi-user reboot is initiated. See >>> init(1M) for details. On x86 systems, reboot may also update >>> the boot archive as needed to ensure a successful reboot. >>> >>> >>> The reboot utility normally logs the reboot to the system >>> log daemon, syslogd(1M), and places a shutdown record in the >>> login accounting file /var/adm/wtmpx. These actions are >>> inhibited if the -n or -q options are present. >>> >>> >>> Normally, the system reboots itself at power-up or after >>> crashes. >>> >>> OPTIONS >>> The following options are supported: >>> >>> -d >>> >>> Force a system crash dump before rebooting. See >>> dumpadm(1M) for information on configuring system crash >>> dumps. >>> >>> >>> >>> >>> SunOS 5.11 Last change: 26 Jan 20101 >>> >>> >>> >>> >>> >>> >>> System Administration Commands reboot(1M) >>> >>> >>> >>> -e >>> >>> If -f is present, reboot to the specified boot environ- >>> ment. >>> >>> This option is currently available only on x86 systems. >>> >>> >>> -f >>> >>> For x86 systems: >>> >>> Fast reboot, bypassing firmware and boot loader. The new >>> kernel will be loaded into memory by the running kernel, >>> and control will be transferred to the newly loaded ker- >>> nel. If disk or kernel arguments are specified, they >>> must be specified before other boot arguments. >>> >>> For SPARC systems: >>> >>> Speeds up rebooting by skipping some POST tests. >>> >>> The service svc:/system/boot-config:default is enabled >>> by default. It requires solaris.system.shutdown as >>> action_authorization and value_authorization. When the >>> config/fastreboot_default property is set to true, >>> reboot will behave as reboot -f. The value of this pro- >>> perty can be changed using svccfg(1M) and svcadm(1M), to >>> control the default reboot behavior. >>> >>> See EXAMPLES for details. >>> >>> >>> -l >>> >>> Suppress sending a message to the system log daemon, >>>
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On Wed, Jan 27, 2010 at 01:51:57PM -0800, Garrett D'Amore wrote: > On 01/27/10 01:44 PM, Huay-Yong Wang wrote: > > > > I spoke to Chris and the case is amended for > > minor binding only. Chris will send > > out an update to the init(1M) manpage shortly. > > Thanks. > > Thanks for the clarification. I reaffirm my +1 (or 100). > > One question: is this (esp. fast-reboot-on-panic) going to be enabled by > default? (I have raised concerns about fast-reboot-on-panic and risks > associated with it elsewhere. Let me know if you want to hear about them.) No it will not be enabled by default. > - Garrett > > > > > > > On 01/27/10 11:39, Garrett D'Amore wrote: > >> On 01/27/10 11:23 AM, Sherry Moore wrote: > >>> Thank you guys for the great work! > >>> > >>> When I filed 2008/382 I requested minor binding only. This case is > >>> requesting patch/micro release binding. Will the binding difference > >>> need to be reflected in case 2008/382? Will there be compatibility > >>> concerns as 2008/382 added devo_quiesce to dev_ops? > >> > >> Oh, I didn't see Patch binding. > >> > >> I'd like to retract my +1 if this is Patch. If its *Minor* binding, then > >> I'm very happy. > >> > >> - Garrett > >> > >>> Sherry > >>> > >>> On Tue, Jan 26, 2010 at 04:52:48PM -0800, Huay-Yong Wang wrote: > I am sponsoring this fasttrack for Chris Kiick. > > This project implements fast reboot support > for SPARC. Specifically, the -f and -p options > in reboot(1M) is now supported on SPARC. > Previously these options are only available > for x86 platforms (See PSARC 2008/382 Fast Reboot) > Note that the -e option (boot environments) is not yet > supported on SPARC. This project introduces no > new interface and I believe this qualify as self-review. > I will be marking the case closed approved automatic. > If anyone feels that this need to be promoted to a fast track > please let me know. > > The project team is requesting a patch/micro release binding. > An updated reboot(1M) manpage is included here. > > > --- cut here --- > > System Administration Commands reboot(1M) > > > > NAME > reboot - restart the operating system > > SYNOPSIS > /usr/sbin/reboot [-dlnq] [-f | -p] [boot_arguments] > > > /usr/sbin/reboot [-f [-e environment] | -p] [-dlnq] > [boot_arguments] > > > DESCRIPTION > The reboot utility restarts the kernel. The kernel is loaded > into memory by the PROM monitor, which transfers control to > the loaded kernel. > > > On x86 systems, when the -f flag is specified, the running > kernel will load the next kernel into memory, then transfer > control to the newly loaded kernel. This form of reboot is > shown in the second synopsis, above. > > > Although reboot can be run by the super-user at any time, > shutdown(1M) is normally used first to warn all users logged > in of the impending loss of service. See shutdown(1M) for > details. > > > The reboot utility performs a sync(1M) operation on the > disks, and then a multi-user reboot is initiated. See > init(1M) for details. On x86 systems, reboot may also update > the boot archive as needed to ensure a successful reboot. > > > The reboot utility normally logs the reboot to the system > log daemon, syslogd(1M), and places a shutdown record in the > login accounting file /var/adm/wtmpx. These actions are > inhibited if the -n or -q options are present. > > > Normally, the system reboots itself at power-up or after > crashes. > > OPTIONS > The following options are supported: > > -d > > Force a system crash dump before rebooting. See > dumpadm(1M) for information on configuring system crash > dumps. > > > > > SunOS 5.11 Last change: 26 Jan 20101 > > > > > > > System Administration Commands reboot(1M) > > > > -e > > If -f is present, reboot to the specified boot environ- > ment. > > This option is currently available only on x86 systems. > > > -f > > For x86 systems: > > Fast reboot, bypassing firmware and boot loader. The new > kernel will be loaded into memory by the running kernel, > and control will be transferred to the newly loaded ker- >
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
Here is a diff for the proposed man page change: *** *** 297,307 Stop the operating system and reboot to the state defined by the initdefault entry in /etc/inittab. ! Service svc:/system/boot-config:default is enabled by !default.On x86systems, when the config/fastreboot_default property is set to true, init ! 6 will bypass the firmware. On a SPARC system some POST !tests will be skipped. a,b,c --- 297,306 Stop the operating system and reboot to the state defined by the initdefault entry in /etc/inittab. ! On x86 systems, service svc:/system/boot-config:default ! is enabled by default. When the config/fastreboot_default property is set to true, init ! 6 will bypass the firmware. a,b,c *** On Wed, Jan 27, 2010 at 01:44:29PM -0800, Huay-Yong Wang wrote: > > I spoke to Chris and the case is amended for > minor binding only. Chris will send > out an update to the init(1M) manpage shortly. > Thanks. > -- Chris J. Kiick - Perf Geek and I/O monkey | #include Sun Microsystems: SSG: SPARC Platform Software: Enterprise Workgroup Software Austin TX 512-401-1408Chris.Kiick at sun.com x64408
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
Hi, A clarification about implementation. The initial putback for SPARC fast reboot does NOT implement the full functionality that exists on the x86 side. At this time the scope of the project did not allow a full implementation. SPARC fast reboot shortens boot time by skipping some POST tests (which ones depends on the platform firmware). The interface is the same. If we implement the full functionality (there are plans for that), then it will use the same interface: ie reboot -f. Thanks, > > Could you elaborate a bit more on what POST tests are skipped > > for fast reboot on SPARC, and what are not? > > If it works like x86 fast reboot, I'd expect "all of them" are skipped. > > In x86, the old kernel directly loads and executes the new one. The system > firmware (including POST and BIOS or OBP in the case of SPARC) would never > realize that a different kernel was executing. > > - Garrett > -- Chris J. Kiick - Perf Geek and I/O monkey | #include Sun Microsystems: SSG: SPARC Platform Software: Enterprise Workgroup Software Austin TX 512-401-1408Chris.Kiick at sun.com x64408
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On 1/28/2010 10:55 AM, chris kiick wrote: > Here is a diff for the proposed man page change: > > *** > *** 297,307 > Stop the operating system and reboot to the state > defined by the initdefault entry in /etc/inittab. > > ! Service svc:/system/boot-config:default is enabled by > !default.On x86systems, when the > config/fastreboot_default property is set to true, init > ! 6 will bypass the firmware. On a SPARC system some POST > !tests will be skipped. > Just wondering if it is necessary to say what "-f" option does for SPARC. As Chris mentioned, more changes are in pipe and enhancement will do more than just skipping POST tests. Do we have to change man page for each phase of the fast-boot project? Also, saying SPARC systems implies both CMT and non-CMT SPARC systems. I believe the changes that are coming are only for non-CMT SPARC systems only. Do we need to make that distinction in the man page? > > a,b,c > --- 297,306 > Stop the operating system and reboot to the state > defined by the initdefault entry in /etc/inittab. > > ! On x86 systems, service svc:/system/boot-config:default > ! is enabled by default. When the > config/fastreboot_default property is set to true, init > ! 6 will bypass the firmware. > > > a,b,c > *** > > > On Wed, Jan 27, 2010 at 01:44:29PM -0800, Huay-Yong Wang wrote: > >> I spoke to Chris and the case is amended for >> minor binding only. Chris will send >> out an update to the init(1M) manpage shortly. >> Thanks. >> >> > -- Hitendra Zhangada = SPS Common SW Features Engineering Systems Group, Sun Microsystems, Inc. Work Ph# (858) 625 3757, Ext. x53757 SUN Internal homepage http://esp.west/~hitu
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On 01/29/10 11:46 AM, Hitendra Zhangada wrote: > On 1/28/2010 10:55 AM, chris kiick wrote: >> Here is a diff for the proposed man page change: >> >> *** >> *** 297,307 >> Stop the operating system and reboot to the state >> defined by the initdefault entry in /etc/inittab. >> >> ! Service svc:/system/boot-config:default is enabled by >> !default.On x86systems, when the >> config/fastreboot_default property is set to true, init >> ! 6 will bypass the firmware. On a SPARC system some POST >> !tests will be skipped. > > > Just wondering if it is necessary to say what "-f" option does for SPARC. > As Chris mentioned, more changes are in pipe and enhancement will do > more than just skipping POST tests. Do we have to change man page > for each phase of the fast-boot project? > > Also, saying SPARC systems implies both CMT and non-CMT SPARC > systems. I believe the changes that are coming are only for non-CMT > SPARC systems only. Do we need to make that distinction in the man page? I think I'd rather say something like: "When config/fastreboot_default property is set to true, init 6 will bypass certain firmware initialization and test steps, depending on the specific capabilities of the system." This covers everything, and leaves the door open. - Garrett > > >> >> a,b,c >> --- 297,306 >> Stop the operating system and reboot to the state >> defined by the initdefault entry in /etc/inittab. >> >> ! On x86 systems, service svc:/system/boot-config:default >> ! is enabled by default. When the >> config/fastreboot_default property is set to true, init >> ! 6 will bypass the firmware. more than just skipping POST >> tests. Do we have to change man page >> for each phase of the fast-boot project? >> >> Also, saying SPARC systems implies both CMT and non-CMT SPARC >> systems. I believe the changes that are coming are only for non-CMT >> SPARC systems only. Do we need to make that distinction in the man >> page? >> >> >> a,b,c >> *** >> >> >> On Wed, Jan 27, 2010 at 01:44:29PM -0800, Huay-Yong Wang wrote: >>> I spoke to Chris and the case is amended for >>> minor binding only. Chris will send >>> out an update to the init(1M) manpage shortly. >>> Thanks. >>> > >
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On 01/29/10 14:52, Garrett D'Amore wrote: > On 01/29/10 11:46 AM, Hitendra Zhangada wrote: >> On 1/28/2010 10:55 AM, chris kiick wrote: >>> Here is a diff for the proposed man page change: >>> >>> *** >>> *** 297,307 >>> Stop the operating system and reboot to the state >>> defined by the initdefault entry in /etc/inittab. >>> >>> ! Service svc:/system/boot-config:default is enabled by >>> !default.On x86systems, when the >>> config/fastreboot_default property is set to true, init >>> ! 6 will bypass the firmware. On a SPARC system some POST >>> !tests will be skipped. >> >> >> Just wondering if it is necessary to say what "-f" option does for SPARC. >> As Chris mentioned, more changes are in pipe and enhancement will do >> more than just skipping POST tests. Do we have to change man page >> for each phase of the fast-boot project? >> >> Also, saying SPARC systems implies both CMT and non-CMT SPARC >> systems. I believe the changes that are coming are only for non-CMT >> SPARC systems only. Do we need to make that distinction in the man page? > > I think I'd rather say something like: > > "When config/fastreboot_default property is set to true, init 6 will > bypass certain firmware initialization and test steps, depending on the > specific capabilities of the system." > > This covers everything, and leaves the door open. > > - Garrett Thanks Garrett, I was about to suggest the same. In fact, I think we should unify the description for x86 and sparc, and have the above cover both. - Steve >> >> >>> >>> a,b,c >>> --- 297,306 >>> Stop the operating system and reboot to the state >>> defined by the initdefault entry in /etc/inittab. >>> >>> ! On x86 systems, service svc:/system/boot-config:default >>> ! is enabled by default. When the >>> config/fastreboot_default property is set to true, init >>> ! 6 will bypass the firmware. more than just skipping POST >>> tests. Do we have to change man page >>> for each phase of the fast-boot project? >>> >>> Also, saying SPARC systems implies both CMT and non-CMT SPARC >>> systems. I believe the changes that are coming are only for non-CMT >>> SPARC systems only. Do we need to make that distinction in the man >>> page? >>> >>> >>> a,b,c >>> *** >>> >>> >>> On Wed, Jan 27, 2010 at 01:44:29PM -0800, Huay-Yong Wang wrote: I spoke to Chris and the case is amended for minor binding only. Chris will send out an update to the init(1M) manpage shortly. Thanks. >> >> >
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
Looks good to me (but then the text is basically what I suggested. :-) - Garrett On 02/ 1/10 09:57 AM, chris kiick wrote: > Attached the init.1 man page with suggested edits. > > > On Fri, Jan 29, 2010 at 03:32:53PM -0500, Steve Sistare wrote: > >> On 01/29/10 14:52, Garrett D'Amore wrote: >> >>> On 01/29/10 11:46 AM, Hitendra Zhangada wrote: >>> On 1/28/2010 10:55 AM, chris kiick wrote: > Here is a diff for the proposed man page change: > > *** > *** 297,307 > Stop the operating system and reboot to the state > defined by the initdefault entry in /etc/inittab. > > ! Service svc:/system/boot-config:default is enabled by > !default.On x86systems, when the > config/fastreboot_default property is set to true, init > ! 6 will bypass the firmware. On a SPARC system some POST > !tests will be skipped. > Just wondering if it is necessary to say what "-f" option does for SPARC. As Chris mentioned, more changes are in pipe and enhancement will do more than just skipping POST tests. Do we have to change man page for each phase of the fast-boot project? Also, saying SPARC systems implies both CMT and non-CMT SPARC systems. I believe the changes that are coming are only for non-CMT SPARC systems only. Do we need to make that distinction in the man page? >>> I think I'd rather say something like: >>> "When config/fastreboot_default property is set to true, init 6 will bypass >>> certain firmware initialization and test steps, depending on the specific >>> capabilities of the system." >>> This covers everything, and leaves the door open. >>> - Garrett >>> >> Thanks Garrett, I was about to suggest the same. In fact, I think we >> should unify the description for x86 and sparc, and have the above >> cover both. >> >> - Steve >> >> > a,b,c > --- 297,306 > Stop the operating system and reboot to the state > defined by the initdefault entry in /etc/inittab. > > ! On x86 systems, service svc:/system/boot-config:default > ! is enabled by default. When the > config/fastreboot_default property is set to true, init > ! 6 will bypass the firmware. more than just skipping POST > tests. Do we have to change man page > for each phase of the fast-boot project? > > Also, saying SPARC systems implies both CMT and non-CMT SPARC > systems. I believe the changes that are coming are only for non-CMT > SPARC systems only. Do we need to make that distinction in the man page? > > > a,b,c > *** > > > On Wed, Jan 27, 2010 at 01:44:29PM -0800, Huay-Yong Wang wrote: > >>I spoke to Chris and the case is amended for >>minor binding only. Chris will send >>out an update to the init(1M) manpage shortly. >>Thanks. >> >> >
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
Attached the init.1 man page with suggested edits. On Fri, Jan 29, 2010 at 03:32:53PM -0500, Steve Sistare wrote: > On 01/29/10 14:52, Garrett D'Amore wrote: > > On 01/29/10 11:46 AM, Hitendra Zhangada wrote: > >> On 1/28/2010 10:55 AM, chris kiick wrote: > >>> Here is a diff for the proposed man page change: > >>> > >>> *** > >>> *** 297,307 > >>> Stop the operating system and reboot to the state > >>> defined by the initdefault entry in /etc/inittab. > >>> > >>> ! Service svc:/system/boot-config:default is enabled by > >>> !default.On x86systems, when the > >>> config/fastreboot_default property is set to true, init > >>> ! 6 will bypass the firmware. On a SPARC system some POST > >>> !tests will be skipped. > >> > >> > >> Just wondering if it is necessary to say what "-f" option does for SPARC. > >> As Chris mentioned, more changes are in pipe and enhancement will do > >> more than just skipping POST tests. Do we have to change man page > >> for each phase of the fast-boot project? > >> > >> Also, saying SPARC systems implies both CMT and non-CMT SPARC > >> systems. I believe the changes that are coming are only for non-CMT > >> SPARC systems only. Do we need to make that distinction in the man page? > > I think I'd rather say something like: > > "When config/fastreboot_default property is set to true, init 6 will bypass > > certain firmware initialization and test steps, depending on the specific > > capabilities of the system." > > This covers everything, and leaves the door open. > > - Garrett > > Thanks Garrett, I was about to suggest the same. In fact, I think we > should unify the description for x86 and sparc, and have the above > cover both. > > - Steve > > >> > >> > >>> > >>> a,b,c > >>> --- 297,306 > >>> Stop the operating system and reboot to the state > >>> defined by the initdefault entry in /etc/inittab. > >>> > >>> ! On x86 systems, service svc:/system/boot-config:default > >>> ! is enabled by default. When the > >>> config/fastreboot_default property is set to true, init > >>> ! 6 will bypass the firmware. more than just skipping POST > >>> tests. Do we have to change man page > >>> for each phase of the fast-boot project? > >>> > >>> Also, saying SPARC systems implies both CMT and non-CMT SPARC > >>> systems. I believe the changes that are coming are only for non-CMT > >>> SPARC systems only. Do we need to make that distinction in the man page? > >>> > >>> > >>> a,b,c > >>> *** > >>> > >>> > >>> On Wed, Jan 27, 2010 at 01:44:29PM -0800, Huay-Yong Wang wrote: > I spoke to Chris and the case is amended for > minor binding only. Chris will send > out an update to the init(1M) manpage shortly. > Thanks. > > >> > >> -- Chris J. Kiick - Perf Geek and I/O monkey | #include Sun Microsystems: SSG: SPARC Platform Software: Enterprise Workgroup Software Austin TX 512-401-1408Chris.Kiick at sun.com x64408 -- next part -- System Administration Commands init(1M) NAME init, telinit - process control initialization SYNOPSIS /sbin/init [0123456abcQqSs] /etc/telinit [0123456abcQqSs] DESCRIPTION init is the default primordial user process. (Options given to the kernel during boot may result in the invocation of an alternative primordial user process, as described on kernel(1M)). init initiates the core components of the ser- vicemanagement facility, svc.configd(1M) and svc.startd(1M), and restarts these components if they fail. For backwards compatibility, init also starts and restarts general processes according to /etc/inittab, as desribed below. The run levels and system booting descriptions given below are provided for compatibility purposes only, and otherwise made obsolete by the service management facility, smf(5). init Failure If init exits for any reason other than system shutdown, it will be restarted with process-ID 1. Run Level Defined At any given time, the system is in one of eight possible run levels. A run level is a software configuration under which only a selected group of processes exists. Processes spawned by init for each of these run levels are defined in /etc/inittab. init can be in one of eight run levels, 0-6 and S or s (S and s are identical). The run level changes when a privileged user runs /sbin/init. init and System Booting When the system is booted, init is invoked and the following occurs. First, it reads /etc/default/init to set environment variables. This is typically where TZ (time zone) a
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On 01/29/10 07:52 PM, Garrett D'Amore wrote: > On 01/29/10 11:46 AM, Hitendra Zhangada wrote: >> On 1/28/2010 10:55 AM, chris kiick wrote: >>> Here is a diff for the proposed man page change: >>> >>> *** >>> *** 297,307 >>> Stop the operating system and reboot to the state >>> defined by the initdefault entry in /etc/inittab. >>> >>> ! Service svc:/system/boot-config:default is enabled by >>> !default.On x86systems, when the >>> config/fastreboot_default property is set to true, init >>> ! 6 will bypass the firmware. On a SPARC system some POST >>> !tests will be skipped. >> >> >> Just wondering if it is necessary to say what "-f" option does for >> SPARC. >> As Chris mentioned, more changes are in pipe and enhancement will do >> more than just skipping POST tests. Do we have to change man page >> for each phase of the fast-boot project? >> >> Also, saying SPARC systems implies both CMT and non-CMT SPARC >> systems. I believe the changes that are coming are only for non-CMT >> SPARC systems only. Do we need to make that distinction in the man >> page? > > I think I'd rather say something like: > > "When config/fastreboot_default property is set to true, init 6 will > bypass certain firmware initialization and test steps, depending on > the specific capabilities of the system." > > This covers everything, and leaves the door open. I like the idea of unifying the text for all platforms, but I think there is an obvious question as a consumer: How do I tell if my system has the "specific capabilities" required for fast reboot? Is there a command which can be run, or a particular line in prtconf, prtdiag or the like which tells me whether the system is capable of fast reboot? Regards, Brian > > - Garrett >> >> >>> >>> a,b,c >>> --- 297,306 >>> Stop the operating system and reboot to the state >>> defined by the initdefault entry in /etc/inittab. >>> >>> ! On x86 systems, service svc:/system/boot-config:default >>> ! is enabled by default. When the >>> config/fastreboot_default property is set to true, init >>> ! 6 will bypass the firmware. more than just skipping POST >>> tests. Do we have to change man page >>> for each phase of the fast-boot project? >>> >>> Also, saying SPARC systems implies both CMT and non-CMT SPARC >>> systems. I believe the changes that are coming are only for non-CMT >>> SPARC systems only. Do we need to make that distinction in the man >>> page? >>> >>> >>> a,b,c >>> *** >>> >>> >>> On Wed, Jan 27, 2010 at 01:44:29PM -0800, Huay-Yong Wang wrote: I spoke to Chris and the case is amended for minor binding only. Chris will send out an update to the init(1M) manpage shortly. Thanks. >> >> > -- Brian Ruthven Solaris Revenue Product Engineering Sun Microsystems UK Sparc House, Guillemont Park, Camberley, GU17 9QG
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On 02/ 3/10 02:20 AM, Brian Ruthven - Solaris Network Sustaining - Sun UK wrote: > > > On 01/29/10 07:52 PM, Garrett D'Amore wrote: >> On 01/29/10 11:46 AM, Hitendra Zhangada wrote: >>> On 1/28/2010 10:55 AM, chris kiick wrote: Here is a diff for the proposed man page change: *** *** 297,307 Stop the operating system and reboot to the state defined by the initdefault entry in /etc/inittab. ! Service svc:/system/boot-config:default is enabled by !default.On x86systems, when the config/fastreboot_default property is set to true, init ! 6 will bypass the firmware. On a SPARC system some POST !tests will be skipped. >>> >>> >>> Just wondering if it is necessary to say what "-f" option does for >>> SPARC. >>> As Chris mentioned, more changes are in pipe and enhancement will do >>> more than just skipping POST tests. Do we have to change man page >>> for each phase of the fast-boot project? >>> >>> Also, saying SPARC systems implies both CMT and non-CMT SPARC >>> systems. I believe the changes that are coming are only for non-CMT >>> SPARC systems only. Do we need to make that distinction in the man >>> page? >> >> I think I'd rather say something like: >> >> "When config/fastreboot_default property is set to true, init 6 will >> bypass certain firmware initialization and test steps, depending on >> the specific capabilities of the system." >> >> This covers everything, and leaves the door open. > > I like the idea of unifying the text for all platforms, but I think > there is an obvious question as a consumer: > > How do I tell if my system has the "specific capabilities" required > for fast reboot? Is there a command which can be run, or a particular > line in prtconf, prtdiag or the like which tells me whether the system > is capable of fast reboot? reboot -f dryrun shows whether your system is capable at all. As far as what the precise meaning of of fast reboot is for your platform (how much of POST, firmware, etc, is skipped?) -- the end user simply should not care. - Garrett > > Regards, > Brian > >> >> - Garrett >>> >>> a,b,c --- 297,306 Stop the operating system and reboot to the state defined by the initdefault entry in /etc/inittab. ! On x86 systems, service svc:/system/boot-config:default ! is enabled by default. When the config/fastreboot_default property is set to true, init ! 6 will bypass the firmware. more than just skipping POST tests. Do we have to change man page for each phase of the fast-boot project? Also, saying SPARC systems implies both CMT and non-CMT SPARC systems. I believe the changes that are coming are only for non-CMT SPARC systems only. Do we need to make that distinction in the man page? a,b,c *** On Wed, Jan 27, 2010 at 01:44:29PM -0800, Huay-Yong Wang wrote: > I spoke to Chris and the case is amended for > minor binding only. Chris will send > out an update to the init(1M) manpage shortly. > Thanks. > >>> >>> >> >
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
> > > reboot -f dryrun shows whether your system is capable at all. > > > > Lovely. Is that documented anywhere? I don't see it in the man page for > > reboot(1M). Seems like an ideal extension to the text you proposed along > > the > > lines of "To see if your system is capable of fast reboot, run reboot -f > > dryrun". > > dryrun only works on x86. Nothing prevents "dryrun" from working on SPARC. The implementation is in common code. Sherry
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On 02/ 3/10 03:33 PM, Garrett D'Amore wrote: > On 02/ 3/10 02:20 AM, Brian Ruthven - Solaris Network Sustaining - Sun > UK wrote: >> >> >> On 01/29/10 07:52 PM, Garrett D'Amore wrote: >>> On 01/29/10 11:46 AM, Hitendra Zhangada wrote: On 1/28/2010 10:55 AM, chris kiick wrote: > Here is a diff for the proposed man page change: > > *** > *** 297,307 > Stop the operating system and reboot to the state > defined by the initdefault entry in /etc/inittab. > > ! Service svc:/system/boot-config:default is enabled by > !default.On x86systems, when the > config/fastreboot_default property is set to true, init > ! 6 will bypass the firmware. On a SPARC system some POST > !tests will be skipped. Just wondering if it is necessary to say what "-f" option does for SPARC. As Chris mentioned, more changes are in pipe and enhancement will do more than just skipping POST tests. Do we have to change man page for each phase of the fast-boot project? Also, saying SPARC systems implies both CMT and non-CMT SPARC systems. I believe the changes that are coming are only for non-CMT SPARC systems only. Do we need to make that distinction in the man page? >>> >>> I think I'd rather say something like: >>> >>> "When config/fastreboot_default property is set to true, init 6 will >>> bypass certain firmware initialization and test steps, depending on >>> the specific capabilities of the system." >>> >>> This covers everything, and leaves the door open. >> >> I like the idea of unifying the text for all platforms, but I think >> there is an obvious question as a consumer: >> >> How do I tell if my system has the "specific capabilities" required >> for fast reboot? Is there a command which can be run, or a particular >> line in prtconf, prtdiag or the like which tells me whether the >> system is capable of fast reboot? > > reboot -f dryrun shows whether your system is capable at all. Lovely. Is that documented anywhere? I don't see it in the man page for reboot(1M). Seems like an ideal extension to the text you proposed along the lines of "To see if your system is capable of fast reboot, run reboot -f dryrun". Cheers, Brian > > As far as what the precise meaning of of fast reboot is for your > platform (how much of POST, firmware, etc, is skipped?) -- the end > user simply should not care. > > - Garrett > >> >> Regards, >> Brian >> >>> >>> - Garrett > > a,b,c > --- 297,306 > Stop the operating system and reboot to the state > defined by the initdefault entry in /etc/inittab. > > ! On x86 systems, service svc:/system/boot-config:default > ! is enabled by default. When the > config/fastreboot_default property is set to true, init > ! 6 will bypass the firmware. more than just skipping > POST tests. Do we have to change man page > for each phase of the fast-boot project? > > Also, saying SPARC systems implies both CMT and non-CMT SPARC > systems. I believe the changes that are coming are only for non-CMT > SPARC systems only. Do we need to make that distinction in the > man page? > > > a,b,c > *** > > > On Wed, Jan 27, 2010 at 01:44:29PM -0800, Huay-Yong Wang wrote: >> I spoke to Chris and the case is amended for >> minor binding only. Chris will send >> out an update to the init(1M) manpage shortly. >> Thanks. >> >>> >> > -- Brian Ruthven Solaris Revenue Product Engineering Sun Microsystems UK Sparc House, Guillemont Park, Camberley, GU17 9QG
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On Wed, Feb 03, 2010 at 05:34:17PM +, Brian Ruthven - Solaris Network Sustaining - Sun UK wrote: > > > >> How do I tell if my system has the "specific capabilities" required for > >> fast reboot? Is there a command which can be run, or a particular line in > >> prtconf, prtdiag or the like which tells me whether the system is capable > >> of fast reboot? > > > > reboot -f dryrun shows whether your system is capable at all. > > Lovely. Is that documented anywhere? I don't see it in the man page for > reboot(1M). Seems like an ideal extension to the text you proposed along the > lines of "To see if your system is capable of fast reboot, run reboot -f > dryrun". dryrun only works on x86. > Cheers, > Brian > > > > > > > As far as what the precise meaning of of fast reboot is for your platform > > (how much of POST, firmware, etc, is skipped?) -- the end user simply > > should not care. > > > > - Garrett > > > >> > >> Regards, > >> Brian > >> > >>> > >>> - Garrett > > > > > > a,b,c > > --- 297,306 > > Stop the operating system and reboot to the state > > defined by the initdefault entry in /etc/inittab. > > > > ! On x86 systems, service svc:/system/boot-config:default > > ! is enabled by default. When the > > config/fastreboot_default property is set to true, init > > ! 6 will bypass the firmware. more than just skipping POST > > tests. Do we have to change man page > > for each phase of the fast-boot project? > > > > Also, saying SPARC systems implies both CMT and non-CMT SPARC > > systems. I believe the changes that are coming are only for non-CMT > > SPARC systems only. Do we need to make that distinction in the man > > page? > > > > > > a,b,c > > *** > > > > > > On Wed, Jan 27, 2010 at 01:44:29PM -0800, Huay-Yong Wang wrote: > >> I spoke to Chris and the case is amended for > >> minor binding only. Chris will send > >> out an update to the init(1M) manpage shortly. > >> Thanks. > >> > > > >>> > >> > > > > -- > Brian Ruthven > Solaris Revenue Product Engineering > Sun Microsystems UK > Sparc House, Guillemont Park, Camberley, GU17 9QG -- Chris J. Kiick - Perf Geek and I/O monkey | #include Sun Microsystems: SSG: SPARC Platform Software: Enterprise Workgroup Software Austin TX 512-401-1408Chris.Kiick at sun.com x64408
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On 03/02/10 17:38, chris kiick wrote: How do I tell if my system has the "specific capabilities" required for fast reboot? Is there a command which can be run, or a particular line in prtconf, prtdiag or the like which tells me whether the system is capable of fast reboot? >>> >>> reboot -f dryrun shows whether your system is capable at all. >> >> Lovely. Is that documented anywhere? I don't see it in the man page for >> reboot(1M). Seems like an ideal extension to the text you proposed along >> the >> lines of "To see if your system is capable of fast reboot, run reboot -f >> dryrun". > > dryrun only works on x86. I don't see it mentioned in reboot(1) on an x86 system either. cheers, calum.
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On 02/ 3/10 09:59 AM, Calum Mackay wrote: > On 03/02/10 17:38, chris kiick wrote: > How do I tell if my system has the "specific capabilities" > required for > fast reboot? Is there a command which can be run, or a particular > line in > prtconf, prtdiag or the like which tells me whether the system is > capable > of fast reboot? reboot -f dryrun shows whether your system is capable at all. >>> >>> Lovely. Is that documented anywhere? I don't see it in the man >>> page for >>> reboot(1M). Seems like an ideal extension to the text you proposed >>> along the >>> lines of "To see if your system is capable of fast reboot, run >>> reboot -f >>> dryrun". >> >> dryrun only works on x86. > > I don't see it mentioned in reboot(1) on an x86 system either. Its "undocumented", and IIRC, was not formally ARC'd as an interface. - Garrett > > cheers, > calum.
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
Garrett, It was by your request during PSARC review that "reboot -f dryrun" to be a project private interface and therefore not to be documented in the man pages. Sherry On Wed, Feb 03, 2010 at 10:32:37AM -0800, Garrett D'Amore wrote: > On 02/ 3/10 09:59 AM, Calum Mackay wrote: > >On 03/02/10 17:38, chris kiick wrote: > >How do I tell if my system has the "specific capabilities" > >required for > >fast reboot? Is there a command which can be run, or a > >particular line in > >prtconf, prtdiag or the like which tells me whether the > >system is capable > >of fast reboot? > > reboot -f dryrun shows whether your system is capable at all. > >>> > >>> Lovely. Is that documented anywhere? I don't see it in the > >>>man page for > >>> reboot(1M). Seems like an ideal extension to the text you > >>>proposed along the > >>> lines of "To see if your system is capable of fast reboot, > >>>run reboot -f > >>> dryrun". > >> > >>dryrun only works on x86. > > > >I don't see it mentioned in reboot(1) on an x86 system either. > > Its "undocumented", and IIRC, was not formally ARC'd as an interface. > > - Garrett > > > >cheers, > >calum. -- Sherry Moore, Solaris Core Kernel http://blogs.sun.com/sherrym
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
On 02/ 3/10 11:12 AM, Sherry Moore wrote: > Garrett, > > It was by your request during PSARC review that "reboot -f dryrun" to > be a project private interface and therefore not to be documented in > the man pages. > Hmm.. ok. I don't remember rightly why I would have requested that, but I presume I had a reason for it at the time. Perhaps its a good time to revisit that decision, since there seems to be some desire to have the ability to query this. - Garrett > Sherry > > On Wed, Feb 03, 2010 at 10:32:37AM -0800, Garrett D'Amore wrote: > >> On 02/ 3/10 09:59 AM, Calum Mackay wrote: >> >>> On 03/02/10 17:38, chris kiick wrote: >>> >>> How do I tell if my system has the "specific capabilities" >>> required for >>> fast reboot? Is there a command which can be run, or a >>> particular line in >>> prtconf, prtdiag or the like which tells me whether the >>> system is capable >>> of fast reboot? >>> >> reboot -f dryrun shows whether your system is capable at all. >> > Lovely. Is that documented anywhere? I don't see it in the > man page for > reboot(1M). Seems like an ideal extension to the text you > proposed along the > lines of "To see if your system is capable of fast reboot, > run reboot -f > dryrun". > dryrun only works on x86. >>> I don't see it mentioned in reboot(1) on an x86 system either. >>> >> Its "undocumented", and IIRC, was not formally ARC'd as an interface. >> >> - Garrett >> >>> cheers, >>> calum. >>> >
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
mm14424 at opensolaris:~$ pfexec reboot -f dryrun reboot: not all drivers have implemented quiesce(9E) mm14424 at opensolaris:~$ It would be more customer/system admin friendly to state something like "Fast reboot not supported on this machine" rather than above message which assumes some knowledge of device drivers and driver entry points. Margot Garrett D'Amore wrote: > On 02/ 3/10 11:12 AM, Sherry Moore wrote: >> Garrett, >> >> It was by your request during PSARC review that "reboot -f dryrun" to >> be a project private interface and therefore not to be documented in >> the man pages. >> > > Hmm.. ok. I don't remember rightly why I would have requested that, > but I presume I had a reason for it at the time. > > Perhaps its a good time to revisit that decision, since there seems to > be some desire to have the ability to query this. > > - Garrett > >> Sherry >> >> On Wed, Feb 03, 2010 at 10:32:37AM -0800, Garrett D'Amore wrote: >> >>> On 02/ 3/10 09:59 AM, Calum Mackay wrote: >>> On 03/02/10 17:38, chris kiick wrote: How do I tell if my system has the "specific capabilities" required for fast reboot? Is there a command which can be run, or a particular line in prtconf, prtdiag or the like which tells me whether the system is capable of fast reboot? >>> reboot -f dryrun shows whether your system is capable at all. >>> >> Lovely. Is that documented anywhere? I don't see it in the >> man page for >> reboot(1M). Seems like an ideal extension to the text you >> proposed along the >> lines of "To see if your system is capable of fast reboot, >> run reboot -f >> dryrun". >> > dryrun only works on x86. > I don't see it mentioned in reboot(1) on an x86 system either. >>> Its "undocumented", and IIRC, was not formally ARC'd as an interface. >>> >>> - Garrett >>> cheers, calum. >> >
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
Or even better which drivers aren't supporting quiesce on the system in question. On 2/3/2010 3:38 PM, Margot Miller wrote: > mm14424 at opensolaris:~$ pfexec reboot -f dryrun > reboot: not all drivers have implemented quiesce(9E) > mm14424 at opensolaris:~$ > > It would be more customer/system admin friendly to state something > like "Fast reboot not supported on this machine" rather > than above message which assumes some knowledge > of device drivers and driver entry points. > > Margot > > > Garrett D'Amore wrote: >> On 02/ 3/10 11:12 AM, Sherry Moore wrote: >>> Garrett, >>> >>> It was by your request during PSARC review that "reboot -f dryrun" to >>> be a project private interface and therefore not to be documented in >>> the man pages. >> >> Hmm.. ok. I don't remember rightly why I would have requested that, >> but I presume I had a reason for it at the time. >> >> Perhaps its a good time to revisit that decision, since there seems >> to be some desire to have the ability to query this. >> >> - Garrett >> >>> Sherry >>> >>> On Wed, Feb 03, 2010 at 10:32:37AM -0800, Garrett D'Amore wrote: On 02/ 3/10 09:59 AM, Calum Mackay wrote: > On 03/02/10 17:38, chris kiick wrote: > How do I tell if my system has the "specific capabilities" > required for > fast reboot? Is there a command which can be run, or a > particular line in > prtconf, prtdiag or the like which tells me whether the > system is capable > of fast reboot? reboot -f dryrun shows whether your system is capable at all. >>> Lovely. Is that documented anywhere? I don't see it in the >>> man page for >>> reboot(1M). Seems like an ideal extension to the text you >>> proposed along the >>> lines of "To see if your system is capable of fast reboot, >>> run reboot -f >>> dryrun". >> dryrun only works on x86. > I don't see it mentioned in reboot(1) on an x86 system either. Its "undocumented", and IIRC, was not formally ARC'd as an interface. - Garrett > cheers, > calum. >> >
SPARC support for Fast Reboot [PSARC/2010/030 Self Review]
As I mentioned before, "reboot -f dryrun" is a project private interface therefore the output is meant for developer consumption only. If actual "reboot" is issued, user will see the following output: Jan 27 06:23:27 x39-4 genunix: WARNING: ixgbe has no quiesce() reboot: Not all drivers have implemented quiesce(9E) Please see /var/adm/messages for drivers that haven't implemented quiesce(9E). Before committing to exposing this interface, developers are encouraged to review the possible failure conditions and associated error messages at http://blogs.sun.com/sherrym/date/20090324 and the test matrix which includes verification of these messages at http://jurassic-x4600.sfbay/~sherrym/projects/panic-reboot/test-matrix.txt Sherry On Wed, Feb 03, 2010 at 04:00:14PM -0500, Torrey McMahon wrote: > Or even better which drivers aren't supporting quiesce on the system > in question. > > On 2/3/2010 3:38 PM, Margot Miller wrote: > >mm14424 at opensolaris:~$ pfexec reboot -f dryrun > >reboot: not all drivers have implemented quiesce(9E) > >mm14424 at opensolaris:~$ > > > >It would be more customer/system admin friendly to state something > >like "Fast reboot not supported on this machine" rather > >than above message which assumes some knowledge > >of device drivers and driver entry points. > > > >Margot > > > > > >Garrett D'Amore wrote: > >>On 02/ 3/10 11:12 AM, Sherry Moore wrote: > >>>Garrett, > >>> > >>>It was by your request during PSARC review that "reboot -f dryrun" to > >>>be a project private interface and therefore not to be documented in > >>>the man pages. > >> > >>Hmm.. ok. I don't remember rightly why I would have requested > >>that, but I presume I had a reason for it at the time. > >> > >>Perhaps its a good time to revisit that decision, since there > >>seems to be some desire to have the ability to query this. > >> > >>- Garrett > >> > >>>Sherry > >>> > >>>On Wed, Feb 03, 2010 at 10:32:37AM -0800, Garrett D'Amore wrote: > On 02/ 3/10 09:59 AM, Calum Mackay wrote: > >On 03/02/10 17:38, chris kiick wrote: > >How do I tell if my system has the "specific capabilities" > >required for > >fast reboot? Is there a command which can be run, or a > >particular line in > >prtconf, prtdiag or the like which tells me whether the > >system is capable > >of fast reboot? > reboot -f dryrun shows whether your system is capable at all. > >>> Lovely. Is that documented anywhere? I don't see it in the > >>>man page for > >>> reboot(1M). Seems like an ideal extension to the text you > >>>proposed along the > >>> lines of "To see if your system is capable of fast reboot, > >>>run reboot -f > >>> dryrun". > >>dryrun only works on x86. > >I don't see it mentioned in reboot(1) on an x86 system either. > Its "undocumented", and IIRC, was not formally ARC'd as an interface. > > - Garrett > >cheers, > >calum. > >> > > -- Sherry Moore, Solaris Core Kernel http://blogs.sun.com/sherrym
