JP2015512535A - Method and system for confirming proper operation of computing device after system change - Google Patents

Abstract

A method and system for automatically applying a system change and verifying the correct operation of the computing device after the system change is provided by the computing device using the operating system and the BIOS component, at least temporarily. , Determining the success or failure of the system change, and giving an opportunity to discard the system change in case of failure.

Description

  Sometimes a computing device may require system level changes to maintain proper and / or efficient operation. Examples of such changes may include changes to BIOS, patches for processor microcode, firmware updates, security patches, configuration changes, and the like. However, performing a system change may cause the computing device to enter an inappropriate state. Consequently, performing system level changes automatically (eg, unattended) is risky. In fact, when a computing device receives an automatic system change request, the request is ignored or rejected to avoid the risk of system failure, despite the expected benefits of setting up the system change. There is a case.

  The invention described herein is illustrated by way of example and not limitation in the accompanying drawings. For simplicity and clarity of illustration, elements in the drawings are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference signs have been used repeatedly among the drawings to indicate corresponding or analogous elements.

FIG. 1 is a simplified block diagram of at least one embodiment of a computing device.

FIG. 2 is a simplified modular diagram of at least one embodiment of operational phases and modes of operation of the computing device shown in FIG.

FIG. 3 is a simplified flow diagram of at least one embodiment of a method for determining which to apply among at least two system configurations applicable during pre-boot processing.

FIG. 4 is a simplified flow diagram of at least one embodiment of a method for initiating system changes.

FIG. 5 is a simplified flow diagram of at least one embodiment of a method for handling communications related to pending system changes.

FIG. 6 is a simplified flow diagram of at least one embodiment of a method for confirming pending system changes.

  While the concepts of the disclosure may take various modifications and alternative forms, examples of specific embodiments thereof are shown by way of example in the drawings and are described in detail herein. However, it is not intended to limit the concept of the present disclosure to the specific forms disclosed, but on the contrary, all modifications and equivalents belonging to the spirit and scope of the invention as defined by the appended claims And it is intended to cover alternatives.

  In the following description, a number of specific descriptions of logic execution, opcodes, operand specification means, resource distribution / share / copy execution, system component types and relationships, and logic distribution / integration selection, etc. Are set forth for a fuller understanding of the present disclosure. However, it should be understood by those skilled in the art that the disclosed embodiments may be practiced without such specific details. In other instances, control structures, gate level circuits, and all software instruction sequences have not been shown in detail so as not to interfere with the understanding of the invention. A person skilled in the art can execute an appropriate function without undue experimentation according to the description included in the present disclosure.

  References herein to “one embodiment”, “embodiments”, “examples of embodiments”, and the like may include specific features, structures, or characteristics of each described embodiment. Does not necessarily include that particular feature, structure or property. Moreover, such descriptions are not necessarily referring to the same embodiment. Furthermore, where specific features, structures or characteristics are described in connection with certain embodiments, such features in relation to other embodiments explicitly or implicitly within the knowledge of those skilled in the art, Provide structure or properties.

  Embodiments of the invention can be implemented in hardware, firmware, software, or any combination thereof. Embodiments of the invention implemented in a computer system may include one or more bus-based interconnections between components and / or one or more point-to-point interconnections between components. Embodiments of the present invention may also be performed according to instructions transmitted or stored on a provisional or non-provisional machine-readable medium that can be read or executed by one or more processors. A machine-readable medium may be embodied as any device, mechanism, or physical structure for storing or transmitting information in a form readable by a machine (eg, a computing device). For example, machine-readable media is embodied as read-only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, mini or micro SD cards, memory sticks, electrical signals, and the like. Also good.

  In the drawings, specific arrangements and sequences of graphic elements such as devices, modules, instruction blocks, and data elements may be shown for simplicity of description. However, one of ordinary skill in the art understands that the specific order or arrangement of the graphical elements in the drawings is not intended to imply that a particular order or sequence of processes or separation of processes is required. Should be done. In addition, the inclusion of certain graphical elements in the drawings does not require such elements in all embodiments, or the features they represent are not included in some embodiments, or Nor is it intended to suggest that it may not be combined with other elements.

  In general, the graphical elements used to represent instruction blocks are any suitable machine-readable instructions such as software or firmware applications, programs, functions, modules, routines, processes, procedures, plug-ins, applets, widgets, code fragments, etc. Each of these instructions may be executed using any suitable programming language, library, application programming interface (API), and / or other software development tool. For example, some embodiments may be implemented using machine level instructions, C, C ++, and / or other programming languages.

  Similarly, graphical elements used to represent data or information are: registers, data stores, tables, records, arrays, indexes, hashes, maps, trees, lists, graphs, files (of any file type), It may be implemented using any suitable electronic arrangement or structure such as folders, directories, databases, etc.

  Further, in the drawings, when a connection element such as a solid or broken line or arrow is used to indicate a connection, relationship or relationship between two or more other graphical elements, none of such connection elements are present. Does not imply that there is no connection, relationship or association. In other words, connections, relationships or associations between several elements may not be shown in the drawings so as not to obscure an understanding of the present disclosure. Also, for simplicity of illustration, one connection element may be used to represent multiple connections, relationships or associations between elements. For example, where a connection element represents communication of a signal, data or command, such element may represent one or more signal paths (eg, buses) to communicate as needed. Will be understood by those skilled in the art.

  Referring now to FIG. 1, an exemplary system for confirming proper operation of the computing device 100 after performing a system change is implemented as an O / S agent 130 and BIOS / SMI logic 134. As will be described in detail below, the O / S agent 130 communicates with the BIOS / SMI logic 134 to automatically (eg, with human intervention) in the computing device 100 at least temporarily. None) System changes can be set. If the system change setting fails, the O / S agent 130 and BIOS / SMI logic 134 allow the operating system 128 to safely return to the previous (pre-system change) configuration. In this way, system level changes are automatically performed while reducing the risk of system failure.

  The computing device 100 includes, but is not limited to, a mobile device, a personal digital assistant, a mobile computing device, a smartphone, a mobile phone, a handset, a unidirectional pager, a bidirectional pager, a messaging device, a computer, a personal computer (PC). ), Desktop computers, laptop computers, notebook computers, handheld computers, tablet computers, servers, server arrays or server farms, web servers, network servers, Internet servers, workstations, minicomputers, mainframe computers, Supercomputer, network device, web device, distributed computing system, multiprocessor system Processor-based systems, home appliances, programmable home appliances, TVs, digital TVs, configuration top boxes, wireless access points, base stations, subscriber stations, mobile subscriber centers, wireless network controllers, routers, hubs, It may be embodied as any type of electronic device including a gateway, bridge, switch, machine or any combination of any of the foregoing. The exemplary computing device 100 includes at least one processor 110 communicatively coupled to at least one memory 112 and an input / output (I / O) subsystem 114. The computing device 100 can be any type of computing device, such as a desktop computer, laptop or tablet computer, server, enterprise computer system, computer network, mobile or handheld computing device, depending on the particular application. Or it may be embodied as an electronic device (of any size form factor) with other computing capabilities.

  The exemplary processor 110 includes at least one processor core 126. In addition to the amount of cache memory, the memory 112 may be a dynamic random access memory device (DRAM), a synchronous dynamic random access memory device (SDRAM), a double data rate dynamic random access memory device (DDR SDRAM), and / or other volatiles. It may be embodied as any type of suitable memory device such as a volatile memory device.

  In some embodiments, the I / O subsystem 114 may include a memory controller (eg, memory controller subsystem or north bridge) and / or an input / output controller (eg, input / output controller or subsystem or south bridge) (not shown). May be included. In other embodiments, I / O subsystems having other configurations may be used. For example, in some embodiments, the I / O subsystem 114 may form part of a system on chip (SoC) and together with the processor 110 and other components of the computing device 100, an integrated circuit. It may be integrated on the chip. It should be understood that in some embodiments, each component of the I / O subsystem 114 may itself be located on a common integrated circuit chip.

  Exemplary I / O subsystem 114 communicates with memory 112, at least one data storage device 116, at least one firmware device 118, interrupt controller 120, timer 122, and optionally one or more peripherals 124. Combined as possible. A portion of data storage device 116 may be embodied as any suitable device for storing data and / or computer instructions, such as a disk storage device (eg, hard disk), a network of physical and / or logical storage devices, etc. May be. In the exemplary embodiment, operating system (O / S) 128, O / S agent 130, and one or more software applications 136 reside in data storage device 116. In some embodiments, the operating system 128 is, for example, a MICROSOFT WINDOWS®, LINUX®, APPLE iOS or other operating system, or a separate, handheld or portable electronic device, etc. Other similar command settings specifically for a particular type of computing device may be used. Examples of operating systems as described above are or may be registered trademarks or trademarks of their respective owners. In some embodiments, the software application 136 is optionally run on the computing device 100, or a specific type of computing device, such as a discrete, handheld, or portable electronic device. It can be any software application intended for a storage device. A portion of operating system 128, O / S agent 130, and / or software application 136 may be copied to memory 112 during operation for rapid processing or other reasons.

  The exemplary firmware device 118 is implemented as a non-volatile memory such as flash memory or a read only memory (ROM) device. In the exemplary embodiment, firmware device 118 stores a routine setting commonly known as basic input / output system (BIOS) 132, which stores BIOS / SMI logic 134, data, instructions, and / or other information. Including. The BIOS / SMI logic 134 includes a BIOS initial activation logic 222 and a BIOS / SMI runtime logic 232, which will be described later, shown in FIG.

  The exemplary BIOS 132 allows the computing device 100 to start the operating system 128 and communicate with various other devices coupled to the I / O subsystem 114. Depending on the particular processor architecture, Unified Extensible Firmware Interface (UEFI) or other instructions may be used in place of BIOS, but for simplicity of explanation, the term BIOS is More generally, it may be used to represent BIOS, UEFI, or any similar mechanism. In operation, portions of BIOS 132 and / or BIOS / SMI logic 134 may be copied to memory 112 for rapid execution or other reasons.

  Although shown separately for simplicity of illustration, in various embodiments, each or any of interrupt controller 120 and / or timer 122 may be within I / O subsystem 114, firmware 118, and / or processor 110. It may be embodied. The interrupt controller 120 and timer 122 are configured to facilitate communication between the O / S agent 130 and the BIOS / SMI logic 134 and to perform some function or processing in a special purpose mode of operation. Is done. In some computing environments, a special purpose mode of operation is known as a system management mode (SMM), which is referred to herein as such a special purpose mode of operation more generally. May be used to represent The SMM may be used to handle system-wide functions, such as power management, hardware control, and / or error handling, for example.

  In general, SMM is a platform service that is typically hidden from the operating system 128. Use of the system management mode may be initiated by the occurrence of a management interrupt event, such as a system management interrupt (SMI) or a platform management interrupt (PMI), depending on the particular processor architecture. These interrupt events usually take precedence over maskable interrupts and other events because they are not maskable. Typically, a management interrupt initiates an asynchronous process that is executed concurrently with any operating system process that can be executed. As will be described later, the exemplary interrupt controller 120 generates a management interrupt (such as SMI or PMI) in response to the occurrence of a certain event. The exemplary timer 122 can be used to count down over a defined or programmable period (eg, a range of 5 minutes) such that a management interrupt begins upon expiration of the period.

  The I / O subsystem 114 can communicate with one or more other peripheral devices 124 such as a network interface, graphics driver, audio driver, etc. (not shown), for example, depending on the intended use of the computing device 100. May be combined. Further, it should be understood that computing device 100 may include other components, subcomponents, and devices not shown in FIG. 1 for clarity of explanation.

  In general, the components of computing device 100 are communicatively coupled by one or more signal paths, generally represented by double-headed arrows, as shown in FIG. Such a signal path may be embodied as any type of wired or wireless signal path that can facilitate communication between individual devices. For example, the signal path may be embodied as any number of wires, printed circuit board traces, vias, buses, point-to-point interconnects, intervening devices, and the like.

  In operation, the operating system 128 may receive a system level change execution request at any time (eg, runtime) after the start of execution on the computing device 100. Such a request may relate to, for example, a software or firmware update, a patch to a central processing unit (CPU) or processor microcode, a change to a BIOS, a security patch and / or a configuration change. For ease of explanation, each or any of such changes and / or updates or combinations thereof may be referred to herein as a “system change” and may include one or more system changes. A system configuration including the above may be referred to as a “hold configuration”.

  By way of example, in some cases, the processor 110, operating system 128, or software application 136, when initiated, is a system that has not yet been configured on the computing device 100 (eg, by going to an Internet website or remote server). You may automatically check for changes. If there is a configurable system change in the computing device 100, the O / S agent 130 communicates with the BIOS / SMI logic 134 to make one attempt to "operate" the operating system 128 with a pending system change. Do it once. If the O / S agent 130 determines that the trial startup has failed, the operating system 128 restarts with the previous configuration (eg, no system change).

  Referring now to FIG. 2, the module diagram illustrates a phase of operation of the computing device 100 after the computing device 100 is powered on. Since at least one embodiment of the computing device 100 can operate in a standard (eg, CPU) operating mode 210 and a special purpose (eg, SMM) operating mode 200, FIG. 2 illustrates each of these modes. Also, instructions, routines, processes, etc. are shown.

  The operational phases of the computing device 100 include a firmware initialization or “BIOS” phase 212, an operating system startup phase 214, and an operating system execution phase 216. The BIOS phase 212 and the O / S startup phase 214 may be more generally referred to as the “before startup” phase, and the O / S execution phase 216 may be referred to as the “runtime” phase. The phases 212, 214, 216 generally occur sequentially. For example, the O / S startup phase 214 typically does not begin until the BIOS phase 212 is complete. Similarly, the O / S execution phase 216 typically does not begin until the O / S activation phase 214 is complete. The operating modes 200, 210 may be performed simultaneously in any of the phases 212, 214, 216.

  In the BIOS phase 212, the computing device 100 accomplishes the tasks identified by blocks 220 and 222 by executing computer-controlled logic. These tasks are accomplished in standard operating mode 210. At block 220, the BIOS 132 and SMM 200 are initialized. At block 222, the BIOS 132 determines which system configuration to use when booting the operating system 128 (eg, whether to boot with a known “good” configuration, or with a new or “pending” configuration that includes a system change. Execute initial startup logic configured to determine whether or not to start. An exemplary method 300 for accomplishing the task of block 222 described below is shown in FIG. At block 224, the BIOS 132 loads and boots the operating system 128 with the configuration defined by the BIOS 132 at block 222. The computing device 100 is in the O / S startup phase 214 and the standard operating mode 210 when the computer controlled logic is executed at block 224.

  Once the operating system 128 is booted or restarted (eg, step (1) or step (3) of FIG. 2), the computing device 100 operates in the O / S execution phase 216 and the standard operating mode 210. . As indicated by block 226, in the O / S execution phase 216, the computing device 100 may execute the software application 136 and may interact with the user via one or more peripheral devices 124. And / or other actions or operations may be performed. At any time during the O / S execution phase 216, the O / S agent 230 may receive the system change request 228 as described above. Request 228 may be generated, for example, by another process running on computing device 100 or by a user of computing device 100. In response to the request 228, the O / S agent 130 starts executing the requested system change in step (2) of FIG. An exemplary method 400 for accomplishing the task of step (2) of FIG. 2 described below is shown in FIG. Using the SMI message, for example, the O / S agent 130 applies the requested system change at least tentatively by calling the BIOS / SMI logic 134. The BIOS / SMI logic 134 is executed in a special purpose mode of operation (eg, SMM 200), as indicated by block 232; An exemplary method 500 for accomplishing the task of block 232 described below is shown in FIG. The O / S agent 130 then restarts the operating system 128 with a system change (step (3) of FIG. 2), and in step (4) of FIG. 2, for example, one or more system levels Confirm system changes by running the test. An exemplary method 600 for accomplishing the task of step (4) of FIG. 2 described below is shown in FIG.

  Referring now to FIG. 3, an exemplary method 300 (eg, determining which configuration to use when booting the operating system 128) for accomplishing the task of block 222 of FIG. 2 is shown. The method 300 may be embodied as computer controlled logic configured to be executed by the BIOS 132 (eg, the BIOS initial boot logic 222). At block 310, the computing device 100 is powered on or otherwise activated (or restarted). Block 310 is shown as a dashed line, so that in the exemplary embodiment, block 310 simply occurs before the next block of method 300 (eg, 312, 314, 316, 318, 320, 322). It is only an event and indicates that it does not need to be included in any computer-controlled logic of method 300.

  At block 312, the BIOS initial activation logic 222 determines whether the “activation pending” flag is set. In an exemplary embodiment, the activation pending flag is only turned on when the system change is pending (eg, when the O / S agent 130 receives a new configuration setting request that includes the system change) (eg, , Or a value of “1”) or a bit to which a value of “0” is assigned when there is no system change waiting for setting. In the exemplary embodiment, the activation pending flag is stored in a BIOS storage device (eg, flash memory). If there are no pending system changes, then at block 314, the BIOS initial boot logic 222 applies a known “good” configuration (eg, a system configuration that existed before the system change).

  If the system change is pending, then at block 316, the BIOS initial activation logic 222 clears the activation pending flag (eg, changing the activation pending flag from a value of “1” to a value of “0” and vice versa). Also change the same). In an exemplary embodiment, unless the pending configuration activation is successfully completed, the activation pending flag is used to ensure that the operating system 128 is only made one attempt to boot with a configuration that includes a pending system change. Used.

  In block 318, the timer 122 is configured to count down the period so that the operating system 128 is automatically shut down and restarted when the period expires. In the exemplary embodiment, the time period is set to allow sufficient time for the computing device 100 to attempt to wake up successfully in a pending configuration before the end of time. The BIOS initial activation logic 222 then applies the pending configuration at block 320. At block 322, the BIOS initial boot logic 222 initiates booting of the operating system 128, possibly using either the known configuration established at block 314 or the pending configuration applied at block 320. If the pending configuration is successful, the tasks of blocks 320 and 322 are successfully completed before timer 122 expires. If timer 122 expires before the tasks of blocks 320 and 322 are completed, the pending configuration is considered to have failed.

  Referring now to FIG. 4, an example method 400 for accomplishing the task of step (2) of FIG. The method 400 may be embodied as computer-controlled logic configured to be executed by the O / S agent 230. At block 410, the O / S agent 230 receives a request to apply (eg, set) a pending system configuration that includes a system change (eg, request 228 shown in FIG. 2). As described above, the request may be generated by other processes or by a user, for example. Block 410 is shown as a dashed line, so that in the exemplary embodiment, block 410 is merely an event that occurs before the next block of method 400 (eg, 412, 414, 416), and the method Indicates that it does not need to be included in all 400 computer-controlled logic.

  In block 412, the O / S agent sends a message (eg, SMI) to the BIOS / SMI runtime logic 232 that instructs the BIOS / SMI runtime logic 232 to upload the pending configuration included in the message. Further processing of the pending configuration is performed by the BIOS / SMI runtime logic 232 in a special purpose mode of operation 200 starting at block 528 of FIG. Meanwhile, at block 414, the O / S agent 230 waits for a message from the BIOS / SMI runtime logic 232 indicating that the processing in blocks 528, 530, 532, 538 of FIG. At block 416, the O / S agent 230 initiates a restart of the operating system 128 in a pending configuration that includes a system change (shown as step (3) in FIG. 2).

  Now referring to FIG. 5, an exemplary method 500 for accomplishing the task of block 232 is illustrated. Method 500 may be embodied as computer-controlled logic configured to be executed by BIOS 132 (eg, as BIOS runtime logic 232). The example method 500 is configured to receive a number of different messages (eg, SMI) from the O / S agent 230 during the pending configuration process. In the exemplary embodiment, method 500 is performed each time BIOS / SMI runtime logic 232 receives a message from O / S agent 230.

  At block 510, the BIOS / SMI runtime logic 232 receives a message (eg, SMI) from the O / S agent 230. In the exemplary embodiment, at block 510, a message received by the BIOS / SMI runtime logic 232 is received at block 412 of FIG. 4, block 612 of FIG. 6, block 618 of FIG. 6, or block 624 of FIG. / S agent 230. Block 510 is indicated by a dashed line so that in the exemplary embodiment, block 510 is simply the event of the next block of method 500 (eg, blocks 512, 518, 528, 534 and the next block). It only occurs before and indicates that it does not need to be included in any computer-controlled logic of method 500. As shown in FIG. 2, the BIOS / SMI runtime logic 232 is implemented using a special purpose operating mode 200.

  At block 512, the method 500 determines whether the message from the O / S agent 230 indicates that the pending configuration was successfully applied and passed all applicable tests (eg, “pending commit” messages). to decide. In the exemplary embodiment, a “pending commit” message is sent by the O / S agent 230 to the BIOS / SMI runtime logic 232 in block 624 of FIG. If the message received by the BIOS / SMI runtime logic 232 is a “pending commit” message at block 512, then at block 514, the method 500 changes the known “good” configuration to a pending configuration that indicates a system change. In block 516, a status message indicating the successful completion of the task is returned to the O / S agent 230. In the exemplary embodiment, the “success” message of block 516 is received by O / S agent 230 and control is returned to standard operating mode 210 in block 626 of FIG.

  If the message from the O / S agent 230 is not a “pending commit” message, the method 500 proceeds to block 518. At block 518, the method 500 determines whether the message from the O / S agent 230 indicates that the O / S agent 230 is requesting status information for the current configuration, that is, a known “good”. Determine whether a pending configuration including a configuration or system change is currently in use (eg, “which configuration” message). In the exemplary embodiment, the “what configuration” message is sent by the O / S agent 230 to the BIOS / SMI runtime logic 232 in block 612 of FIG.

  If at block 518 the message received by the BIOS / SMI runtime logic 232 is a “what configuration” message, then at block 520, the method 500 uses the pending configuration when the operating system 128 was last booted. Determine whether or not In the exemplary embodiment, this is determined with reference to the activation pending flag described above. If the previous activation used a pending configuration, then at block 522, the timer 122 is disabled, and at block 524 a status message indicating that the pending configuration should be used is received by the BIOS / SMI runtime logic 232 by the O / It is transmitted to the S agent 230. Based on the activation pending flag, the BIOS / SMI runtime logic 232 has concluded that the pending configuration has been successfully applied, so the timer 122 is disabled at block 522. If the previous activation did not use a pending configuration, then in block 526 a status message indicating that a known “good” configuration should be used is sent by the BIOS / SMI runtime logic 232 by the O / S agent. 230. In the exemplary embodiment, the “Use Pending Configuration” message at block 524 or the “Use Known Configuration” message at block 526 is optionally received by the O / S agent 230 and control is illustrated in FIG. At block 614, the standard operating mode 210 is restored.

  If the message from O / S agent 230 is not a “what configuration” message, method 500 proceeds to block 528. At block 528, the method 500 determines whether the message from the O / S agent 230 includes a pending configuration that includes a system change (eg, a “new configuration” message). In the exemplary embodiment, the “new configuration” message is sent by the O / S agent 230 to the BIOS / SMI runtime logic 232 in block 412 of FIG. 4 described above.

  If the message received by the BIOS / SMI runtime logic 232 is a “new configuration” message at block 528, then at block 530, the method 500 generates a pending configuration that includes the data contained in the “new configuration” message. Then, as described above in block 532, the activation hold flag is set, and in block 538, a message indicating that the hold configuration has been successfully generated is transmitted to the O / S agent 230. As described above, block 528 is invoked whenever O / S agent 230 receives a system change request 228. In the exemplary embodiment, the “success” message at block 538 is received by the O / S agent 230 and control is returned to the standard operating mode 210 at block 414 of FIG.

  If the message from the O / S agent 230 is not a “new configuration” message, the method 500 proceeds to block 534 in at least some embodiments. At block 534, the method 500 determines whether the message from the O / S agent 230 indicates that the pending configuration should be discarded because it did not pass all applicable tests (eg, “pending discarded” ”Message or not). In the exemplary embodiment, the “pending discard” message is sent by the O / S agent 230 to the BIOS / SMI runtime logic 232 in block 618 of FIG.

  If the message received by the BIOS / SMI runtime logic 232 is a “pending discard” message at block 534, then at block 536, the method 500 deletes the pending configuration and indicates that the pending configuration has been deleted successfully. A status message is sent to the O / S agent 230. As described above, the method 500 is performed in the special purpose operating mode 200 and control is returned to the standard CPU operating mode 210 in blocks 516, 524, 526, 528 and 536 of FIG.

  Referring now to FIG. 6, an exemplary method 600 for accomplishing the task of step (4) of FIG. 2 (eg, confirmation that the pending configuration has been successfully set) is shown. Method 600 may be embodied as computer controlled logic configured to be executed by O / S agent 230. The method 600 is invoked at block 416 of FIG. 4 once the operating system 128 is restarted in a pending configuration. Thus, block 610 is indicated by a dashed line, so that in the exemplary embodiment, block 610 is simply an event that occurs before the next block of method 600 (eg, block 612 and the next block). Without the need to be included in any computer-controlled logic of the method 600.

  In block 612, the O / S agent 230 determines whether a known “good” configuration or pending configuration is being used by sending the “what configuration” message described above to the BIOS / SMI runtime logic 232. To do. At block 614, the O / S agent 230 receives the message generated by the BIOS / SMI runtime logic 232 in either block 524 or block 526 of FIG. If at block 614 the message from the BIOS / SMI runtime logic 232 received by the O / S agent 230 indicates that a known “good” configuration is being used, then the O / S agent 230 One trial start-up in the configuration failed (eg, timer 122 expired before start-up completed, so restart started with known “good” configuration, or user pressed power or reset button ) Can be concluded. In such an event, the O / S agent 230 initiates computer-controlled error handling logic at block 616 in response to the failed attempt, and in at least some embodiments, at block 618, the “pending” described above. Send a “discard” message to the BIOS / SMI runtime logic 232. Some examples of error handling logic include maintaining a log of failed attempts to activate the pending configuration and / or other data related thereto, generating a report of one or more such failed attempts, computing device 100 May include sending one or more alerts to other users, output devices (such as displays or speakers), network or remote computing devices and / or other remedies. The rescue means or means performed by the O / S agent 230 in block 616 may vary depending on the unique system design or configuration requirements of the computing device 100.

  In block 614, if the message from the BIOS / SMI runtime logic 232 received by the O / S agent 230 indicates that the pending configuration is being used, then the O / S agent 230 is activated with the pending configuration. Can be concluded and block 620 can be reached. However, even if the pending configuration activation is successfully completed, there is still a risk that the system has instability or other operational challenges. Thus, at block 620, the O / S agent 230 performs one or more diagnostics, system tests, operating system tests, built-in self-tests (BIST) and / or other functional tests or series of tests. Thus, it is determined whether or not the computing device 100 is operating properly after activation in the hold configuration. The tests or tests performed by the O / S agent 230 in block 620 may vary depending on the unique system design or configuration requirements of the computing device 100.

  If the pending configuration has successfully completed one or more tests and / or diagnostics performed by the O / S agent 230 at block 620, then at block 624, the O / S agent 230 may receive the “pending commit” described above. A message is sent to the BIOS / SMI runtime logic 232 to instruct the BIOS / SMI runtime logic 232 to replace the known “good” configuration with the pending configuration. At block 626, the O / S agent 230 receives the “success” status message generated by the BIOS / SMI runtime logic 232 at block 516 of FIG. 5 and initiates event logic regarding the successful execution of the pending configuration. To do. Some examples of such event logic include successful attempts to activate the pending configuration and / or logging of other data related thereto, generating reports on one or more such successful attempts, one or more It may include sending one or more alerts to a user of computing device 100, an output device (such as a display or speaker), a network, or a remote computing device and / or other event reporting means. The event reporting means or means performed by the O / S agent 230 at block 626 may vary depending on the unique system design or configuration requirements of the computing device 100.

  If the pending configuration does not complete one or more tests and / or diagnostics performed by the O / S agent 230 at block 620, then at block 618, the O / S agent 230 sends the “pending discard” message described above. By sending to the BIOS / SMI runtime logic 232, the BIOS / SMI runtime logic 232 is instructed to delete the pending configuration and maintain the known “good” configuration. In various embodiments, the O / S agent 230 approves the pending configuration based on the unique system design or configuration requirements of the computing device 100 by using any criteria or any number of criteria. It may be determined whether or not. In other embodiments, for example, in some embodiments, all performed tests and / or diagnostic passes may be 100%, even though passage of performed tests and / or diagnoses may be required. It may be regarded as “passing” that it is less than the value.

  Illustrative examples of the devices, systems and methods disclosed herein are set forth below. Device, system, and method embodiments may include any one or more of the following examples and any combination thereof.

  In one embodiment, a computing device configured to perform system level changes may include at least one processor core and a memory device coupled to the at least one processor core, wherein the memory device includes a plurality of memory devices. A plurality of instructions, when executed by at least one processor core, sends a message to the BIOS to the at least one processor core while the operating system and BIOS are running on the computing device Start the system change by the operating system. In an embodiment, at least one processor may cause the BIOS to start a timer configured to restart the operating system after the period expires. In an embodiment, at least one processor may activate the operating system with a system change. In an embodiment, the at least one processor may determine the success or failure of the startup with a system change by an operating system that communicates with the BIOS. In the embodiment, at least one processor may process the system change according to the determination of success or failure of the system change by the BIOS. In an embodiment, the operating system may be configured to receive a system change request. In an embodiment, the BIOS may be configured to set a flag indicating that the system change is pending. In an embodiment, the BIOS may be configured to determine whether a flag has been set and to start the operating system with a system change in response to the flag being set. In an embodiment, the BIOS may be configured to determine whether a flag has been set and to start the operating system without system change in response to the flag not being set. In an embodiment, the BIOS may be configured to invalidate the timer in response to a determination that activation with system change was successful. In an embodiment, the computing device may be configured to restart the operating system upon expiration of the period. In an embodiment, the operating system may be configured to perform at least one test configured to verify proper operation of the computing device in response to booting of the operating system with a system change. In an embodiment, the operating system may be configured to send a message to the BIOS indicating the success or failure of the system change. In an embodiment, the operating system and the BIOS may be executed in a first configuration on the computing device, and the BIOS may be configured in response to the operating system determining that the system change was successful. May be replaced with a second configuration including a system change. In an embodiment, the operating system and BIOS may be executed in a first configuration on the computing device, and the BIOS deletes the system change in response to the operating system determining that the system change has failed. In addition, the first configuration may be maintained. In an embodiment, the operating system may be configured to report the status of the system change to at least one of a user, an output device, a network, and a remote computing device in response to a system change success / failure determination. .

  In another embodiment, a method is provided for a computing device that executes an operating system and a BIOS that communicates with the operating system by the operating system while the operating system is running on the computing device. It may include initiating a change. In an embodiment, the method may include a BIOS that applies system changes at least temporarily. In an embodiment, the method may include an operating system that determines success or failure of the system change. In an embodiment, the method may include a BIOS that processes the system change in response to determining whether the system change is successful. In an embodiment, the method may include a BIOS that configures a timer that attempts to start with a system change by the operating system and performs a restart without system change in response to a determination that the system change has failed. In an embodiment, the method may include an operating system that performs at least one diagnosis in response to at least provisional application of system changes.

  In other examples, the computing device may include at least one processor and a computer circuit coupled to the at least one processor, the computer circuit performing any of the methods described above with the at least one processor. To be arranged. In other embodiments, the at least one computer-accessible medium may include a plurality of instructions that, when executed, cause the computing device to perform any of the methods described above.

  In other embodiments, a method for performing a system change may include a BIOS that receives a system change request for a computing device from the operating system while the operating system and BIOS are running on the computing device. . The method may include a BIOS that initiates booting of the operating system with the requested system change. The method may include a BIOS that receives an indication of the success or failure of the system change from the operating system. The method may include a system change process in response to an indication of the success or failure of the system change.

  In an embodiment, a computing device configured to perform system changes may include at least one processor and a computer circuit coupled with the at least one processor, the computer circuit being configured by at least one processor. It may be arranged to perform the method described above. In an embodiment, the at least one computer-accessible medium may include a plurality of instructions that, when executed, cause the computing device to perform the method described above.

  In another embodiment, a method for performing a system change is a second configuration of an operating system that includes a first configuration of the operating system and a system change while the operating system and BIOS are running on the computing device. An operating system may be included that receives a message from the BIOS indicating which of the configurations is being performed. The method may include performing at least one test to determine whether the computing device is operating properly in response to a message from the BIOS indicating that the second configuration is being performed. The method may include sending a message to the BIOS indicating whether the computing device operates properly in the second configuration.

  In other examples, a computing device configured to perform system changes may include at least one processor and a computer circuit coupled to the at least one processor, the computer circuit comprising at least one processor The processor may be arranged to perform the method described above. In other embodiments, the at least one computer-accessible medium configured to perform system changes may include a plurality of instructions that, when executed, cause the computing device to perform the method described above. .

  While this disclosure is illustrated and described in detail in the drawings and foregoing description, such illustration and description are to be considered illustrative and not restrictive in nature and are exemplary implementations. It should be understood that only the form is shown and described, and that all changes and modifications falling within the spirit of the disclosure are desired to be protected. Further, although aspects of this disclosure are described in the context of computing devices, various aspects have other uses, for example, any application that desires system level changes or automatic initiation of updates. Please understand that. Such applications may include any device having one or more computer controlled features, such as, for example, electronic devices, “smart” equipment and / or other products.

Claims (23)

A computing device that performs system level changes,
At least one processor core;
A memory device coupled to the at least one processor core,
The memory device stores a plurality of instructions, and when the plurality of instructions are executed by the at least one processor core, the at least one processor core includes:
Initiating a system change by the operating system that sends a message to the BIOS while an operating system and BIOS are running on the computing device;
Causing the BIOS to start a timer to restart the operating system after the end of the period;
Starting the operating system with the system change;
By the operating system that communicates with the BIOS, the success or failure of the activation with the system change is determined,
A computing device that causes the system change to be processed by the BIOS in response to a determination of success or failure of the system change.   The computing device of claim 1, wherein the operating system receives a system change request.   The computing device according to claim 1, wherein the BIOS sets a flag indicating that the system change is pending.   The computing device according to claim 3, wherein the BIOS determines whether or not the flag has been set, and starts the operating system with the system change in response to the flag being set.   4. The computing according to claim 3, wherein the BIOS determines whether or not the flag is set, and boots the operating system without changing the system in response to the flag not being set. apparatus.   The computing device according to claim 1, wherein the BIOS invalidates the timer in response to a determination that the activation with the system change is successful.   The computing device according to claim 1, wherein the computing device restarts the operating system in response to the end of the period.   The computing device of claim 1, wherein the operating system performs at least one test that confirms proper operation of the computing device in response to activation of the operating system with the system change.   The computing device according to claim 1, wherein the operating system transmits a message indicating success or failure of the system change to the BIOS.   The operating system and the BIOS are executed in a first configuration on the computing device, and the BIOS responds to the first configuration in response to the operating system determining that the system change is successful. The computing device according to claim 1, wherein the computing device is replaced with a second configuration including the system change.   The operating system and the BIOS are executed in a first configuration on the computing device, and the BIOS deletes the system change in response to the operating system determining that the system change has failed. The computing device according to claim 1, wherein the first configuration is maintained.   The computing according to claim 1, wherein the operating system reports the status of the system change to at least one of a user, an output device, a network, and a remote computing device in response to determining whether the system change is successful. apparatus. A method for performing a system change, comprising:
Executing on the computing device an operating system and a BIOS communicating with the operating system;
Initiating a system change to the computing device by the operating system while the operating system is running on the computing device;
Applying the system change at least temporarily by the BIOS;
Determining the success or failure of the system change by the operating system;
Processing the system change by the BIOS in response to a determination of success or failure of the system change.   The system includes a step of configuring a timer that attempts to start with the system change by the BIOS and performs a restart without the system change in response to a determination that the system change has failed. 14. The method according to 13.   14. The method of claim 13, comprising performing at least one diagnostic by the operating system in response to at least a provisional application of the system change. A computing device that performs system changes,
At least one processor;
Computer circuitry coupled to the at least one processor,
16. A computing device, wherein the computer circuit is arranged to perform a method according to any one of claims 13 to 15 by the at least one processor. At least one program for performing system changes,
16. A program comprising a plurality of instructions for performing the method according to any one of claims 13 to 15 by the computing device in response to being executed. A method for performing a system change, comprising:
While the operating system and BIOS are running on the computing device, the BIOS
Receiving a system change request for the computing device from the operating system;
Initiating booting of the operating system with the requested system change;
Receiving from the operating system an indication of success or failure of the system change;
Processing the system change in response to an indication of success or failure of the system change. A computing device that performs system changes,
At least one processor;
Computer circuitry coupled to the at least one processor,
19. A computing device, wherein the computer circuit is arranged to perform the method of claim 18 by the at least one processor. At least one program for performing system changes,
19. A program comprising a plurality of instructions for performing the method of claim 18 by the computing device in response to being executed. A method for performing a system change, comprising:
While the operating system and BIOS are running on the computing device, the operating system comprises:
Receiving from the BIOS a message indicating which of the first configuration of the operating system and the second configuration of the operating system including a system change is being performed;
Performing at least one test to determine whether the computing device is operating properly in response to a message from the BIOS indicating that the second configuration is being performed; ,
Sending the message to the BIOS indicating whether the computing device is operating properly in the second configuration. A computing device that performs system changes,
At least one processor;
Computer circuitry coupled to the at least one processor,
22. A computing device, wherein the computer circuit is arranged to perform the method of claim 21 by the at least one processor. At least one program for performing system changes,
23. A program comprising a plurality of instructions that, when executed, cause the computing device to perform the method of claim 21.

Images