JP2019200686A - Control device and program - Google Patents

Abstract

To shorten a time until a process for a device that has caused reboot can be started when a processor is rebooted by a notice from the device.SOLUTION: When an interruption signal is output from a device, a command issuing unit 56 accesses the device that has output the interruption signal, and a first OS 20 energizes second control means 200. In the second control means 200, drivers 7, 8, 9 are activated after a second OS 23 is activated. When the drivers 7, 8, 9 are activated, the command issuing unit 56 first reissues an open command and an ioctl command to a communication path corresponding to the device that has output the interruption signal, and then reissues an open command and an ioctl command to communication paths corresponding to other devices.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a control device and a program.

  As an invention for preventing malfunction when one processor is restarted in a multiprocessor system, for example, there is an electronic device disclosed in Patent Document 1. In this electronic apparatus, a process is executed on the first OS that operates on the first CPU, and a device driver is executed on the second OS that operates on the second CPU to which the device is connected. When the electronic device transitions to the power saving mode, the power supply to the second CPU is stopped and the second OS is terminated. When an instruction to return from the power saving mode to the normal mode is given, the power supply to the second CPU is resumed, the second OS is restarted, and the device driver is restarted by the restarted second OS. When transitioning to the power saving mode, the file descriptor is lost when the second OS is terminated, and the system call is also lost. In order to solve this problem, the electronic device disclosed in Patent Document 1 has a command rewriting function, and rewrites a command written before transitioning to the power saving mode.

Japanese Patent No. 6098389

  For example, in the case of an electronic device having a FAX function, when returning from the power saving mode to the normal mode, an incoming call from an external device is notified from the device to the first OS, and the first OS returns to the normal mode in response to this notification. To start. Here, if the timing at which the device driver of the device that has caused the return to the normal mode completes the return is delayed, the communication processing for the external device will not be in time.

  An object of the present invention is to shorten the time until processing for a device that has caused a restart can be started when the processor is restarted by a notification from the device.

  The control apparatus according to claim 1 of the present invention includes a second control unit that executes the second operating system, and a plurality of device drivers provided for each of a plurality of devices to be controlled operate on the second operating system. When the first operating system is executed and a process corresponding to the device operates on the first operating system, and a notification for returning the second control unit from the power saving state is acquired from the device. , Reissue the commands issued before entering the power saving state for the device driver corresponding to the device that output the notification, and set the reissue order of the commands issued to other device drivers. First control means for making the order earlier than the reissue order.

  In the control apparatus according to claim 2 of the present invention, the second control unit obtains a response to access to the device that has output the notification, supplies the response to the first control unit, and the first control unit The control means supplies the response to the process before the response is supplied from the second control means.

In the control device according to claim 3 of the present invention, the first control means sends the response before reissuing the command to a device driver other than the device driver corresponding to the device that has output the notification. Supply to the process.

  In the control device according to claim 4 of the present invention, the first control means discards the response supplied from the second control means.

  In the control device according to claim 5 of the present invention, when the first control unit acquires the notification, the first control unit accesses the device that has output the notification before restarting the second operating system.

  In the control device according to claim 6 of the present invention, when the first control means acquires the notification, the first control means accesses the device without going through the second operating system and the device driver.

  A program according to claim 7 of the present invention is a means for executing a first operating system on a computer, a process corresponding to a device operating on the first operating system, and a device driver corresponding to the device. When a notification for returning the second control means to be executed from the power saving state is acquired from the device, a command issued before entering the power saving state to the device driver corresponding to the device that has output the notification is reissued This is a program for functioning as a control means for making the reissue order earlier than the reissue order of commands issued to other device drivers.

According to the control device of the first aspect of the present invention, when the processor is restarted by a notification from the device, it is possible to shorten the time until processing for the device that has caused the restart can be started. it can.
According to the control device of the second aspect of the present invention, the response to the access to the device is acquired earlier than the case where the response to the access to the device is supplied from the second control means, and It is possible to shorten the time until the processing for the device that has caused the factor can be started.
According to the control device of the third aspect of the present invention, the restart is performed in comparison with the configuration supplied after the reissue of the command to the device driver other than the device whose response to the access to the device is a return factor. It is possible to shorten the time until the processing for the device that has caused the problem can be started.
According to the control apparatus of the fourth aspect of the present invention, it is possible to prevent a response to access to the device from being supplied to the process a plurality of times.
According to the control device of the fifth aspect of the present invention, the device returns from the power saving state as compared with the configuration in which the device driver is accessed after the device driver is restarted to cause the device to return from the power saving state. It is possible to speed up access to the device that caused the problem.
According to the control apparatus of the sixth aspect of the present invention, the device that has caused the return from the power saving state as compared with the configuration in which the device that has caused the return from the power saving state is accessed from the device driver. Access to can be made faster.
According to the program according to claim 7 of the present invention, when the processor is restarted by a notification from the device, it is possible to shorten the time until processing for the device that causes the restart can be started. .

The figure which shows the hardware constitutions of one Embodiment of this invention. The figure which shows the software structure of embodiment. The sequence diagram for demonstrating the operation example of embodiment. The sequence diagram for demonstrating the operation example of embodiment.

[Embodiment]
Next, the configuration of the embodiment will be described. FIG. 1 is a diagram illustrating a hardware configuration of the embodiment. The main components of the image forming apparatus 1000 are a first control unit 100, a second control unit 200, and a device 300. The first control means 100 is an example of the first control means according to the present invention, and controls the second control means 200. The second control means 200, which is an example of the second control means according to the present invention, controls the device 300.

  The first control means 100 includes a CPU (Central Processing Unit) 101, a RAM (Random Access Memory) 102, a ROM (Read Only Memory) 103, a communication I / F (Interface) 104, and an HDD (Hard Disk Drive) as a storage device. 105 and a LAN (Local Area Network) terminal 106, and these components are connected to the bus 110. The CPU 101 executes a program using the RAM 102 as a work area. The ROM 103 stores a boot loader and the like. The communication I / F 104 is, for example, an interface of PCI (Peripheral Component Interconnect) Express (registered trademark, hereinafter abbreviated as PCIe), and is connected to the communication I / F 204 which is an interface of PCIe included in the second control unit 200 through a signal line. Is done. The HDD 105 stores a first OS 20 (Operating System) program, an application program, and the like. When the image forming apparatus 1000 is turned on, the CPU 101 reads the boot loader from the ROM 103, and reads and executes the program of the first OS 20 from the HDD 105 according to the boot loader. The first OS 20 is, for example, Linux (registered trademark). A signal line is connected to the LAN terminal 106, and the CPU 101 communicates with an external information processing apparatus or the like via the LAN.

  The second control unit 200 includes a CPU 201, a RAM 202, a ROM 203, and a communication I / F 204, and these components are connected to the bus 210. The CPU 201 is an example of a processor according to the present invention, and executes a program using the RAM 202 as a work area. The ROM 203 stores a second OS 23. The CPU 201 reads the second OS 23 from the ROM 203 and executes it. The second OS 23 is an RTOS (Real Time OS), for example, and has a driver function for controlling the device 300.

  The device 300 is, for example, a FAX unit 301, an image forming unit 302, a UI (User Interface) 303, or the like. The device 300 is not limited to these, and may be configured to include other devices such as an image scanner. The FAX unit 301 is connected to a communication line, and transmits and receives image data via the communication line. The image forming unit 302 includes, for example, a storage unit that stores a recording medium such as paper, a transport mechanism that transports the recording medium along a transport path, and forms an image indicated by image data on the transported recording medium with toner. An image forming engine, a fixing device for fixing an image formed on the recording medium to the recording medium, and the like (not shown) are provided, and an image based on the image data supplied from the first control unit 100 via the second control unit 200 is displayed. It is formed on a recording medium by an electrophotographic method. The UI 303 includes, for example, a touch panel, a keypad, and the like (not shown) and accepts user operations. On the touch panel, GUI (Graphical User Interface) for the user to operate the image forming apparatus 1000, information indicating the state of the image forming apparatus 1000, and the like are displayed. The keypad includes a key for instructing the start and stop of the operation of the image forming apparatus 1000, a numeric keypad for inputting numbers, and the like.

As described above, the present embodiment is a so-called multiprocessor system including two CPUs. FIG. 2 is a diagram illustrating a basic software configuration of the multiprocessor system according to the embodiment. In the following description, for the sake of convenience, software components are assumed to be the subject of operation.

  In the first control means 100, the first OS 20 operates, and in the second control means 200, the second OS 23 operates. The first OS 20 is an example of a first operating system according to the present invention, and the second OS 23 is an example of a second operating system according to the present invention. Processes 1, 2, and 3 are processes that constitute an application program that runs on the first OS 20, and are examples of processes according to the present invention. For example, the process 1 is a process for controlling the FAX unit 301, the process 2 is a process for controlling the image forming unit 302, and the process 3 is a process for controlling the UI 303.

  The drivers 7, 8, and 9 operating on the second OS 23 are device drivers that control the device 300, and are examples of device drivers according to the present invention. For example, the driver 7 controls the FAX unit 301, the driver 8 controls the image forming unit 302, and the driver 9 controls the UI 303.

  The processes 1, 2, and 3 call the drivers 7, 8, and 9 by a system call 11 through API (Application Programming Interface) 4, 5, and 6, respectively. The called drivers 7, 8, 9 execute processing corresponding to the contents of the system call 11, and return values 12 representing the execution results of the respective processing are sent to the processes 1, 2, 2, via the APIs 4, 5, 6. Return to 3.

  In the present embodiment, the processes 1, 2, and 3 operate on the first control unit 100 side, and the drivers 7, 8, and 9 operate on the second control unit 200 side. The system call 11 is executed through a library provided by the 1OS 20. Specifically, the system call 11 called by the API 13, 14, 15 of the first OS 20 may be associated in advance with the function 27 interpreted by the libraries 16, 17, 18, or alternatively, 3 may be configured to call function 27 directly. When the function 27 is called, the libraries 16, 17, and 18 convert the function 27 into a command 29 that is commonly interpreted by the first OS 20 and the second OS 23 in order to pass the contents of the function 27 to the second OS 23. The data is passed to the inter-OS communication driver 19. The inter-OS communication driver 19 transmits this command 29 to the inter-OS communication driver 22 by inter-OS communication. The inter-OS communication driver 19 provided in the first OS 20 is a program for communicating with the second OS 23, and the inter-OS communication driver 22 provided in the second OS 23 is a program for communicating with the first OS 20. The interface for communication between the OSs may be any system, but in this embodiment, an example using the PCIe 21 is shown.

  The inter-OS communication driver 22 passes the received command 29 to the tasks 24, 25, and 26. The tasks 24, 25, and 26 that have received the command 29 convert the command 29 into a system call 11 that is interpreted by the drivers 7, 8, and 9, respectively, and the driver 7 by the system call 11 through the APIs 4, 5, and 6, respectively. , 8 and 9 are called. The called drivers 7, 8, 9 execute processing corresponding to the contents of the system call 11, and return values 12 representing the execution results of the respective processing are sent to the tasks 24, 25, 25 via the APIs 4, 5, 6. Return to 26.

The tasks 24, 25, and 26 that have received the return value 12 convert the return value 12 into a status 30 that is commonly interpreted by the first OS 20 and the second OS 23 in order to pass the contents of the return value 12 to the first OS 20. Passed to the inter-OS communication driver 22. The inter-OS communication driver 22 transmits this status 30 to the inter-OS communication driver 19 by inter-OS communication. The inter-OS communication driver 19 passes the received status 30 to the libraries 16, 17, and 18. The libraries 16, 17, and 18 that have received the status 30 convert the status 30 into return values 28 that are interpreted by the processes 1, 2, and 3, respectively.
4 and 15 to return to processes 1, 2, and 3.

  The command issuing unit 56 operates on the first OS 20 and reissues the command 29 when returning from the power saving mode to the normal mode. For example, when the mode is shifted to the power saving mode, the second OS 23 is terminated, so that the assignment of the communication paths 47, 48, and 49 to the file director is lost. Therefore, when returning to the normal mode, it is necessary to reissue an open command, which is an example of the command 29. However, in the processes 1, 2, and 3, file descriptors are assigned to the communication paths 47, 48, and 49. Since the loss is not recognized, the function 27 is called without issuing the open command. Further, in the power saving mode, the system call 11 waiting for processing by the driver 7 also disappears, so it is necessary to reissue not only an open command but also an ioctl command that is an example of the command 29 and is an asynchronous command. Therefore, in the present embodiment, the command issuing unit 56 operates on the first OS 20. The command issuing unit 56 is provided in the inter-OS communication driver 19 for each of the communication paths 47, 48, 49 between the libraries 16, 17, 18 and the tasks 24, 25, 26. The command issuing unit 56 reissues the open command when returning from the power saving mode to the normal mode. In addition, when the second OS 23 is terminated after shifting to the power saving mode, the system calls 11 waiting for processing by the drivers 7, 8, and 9 are also lost. Therefore, the command issuing unit 56 reissues an ioctl command that is an asynchronous command when returning from the power saving mode to the normal mode. The open command and the ioctl command are examples of commands according to the present invention.

  The synchronous command is a command that waits for the next command to be issued until a return value is returned, and the asynchronous command is a command that can issue the next command without waiting for the return value to be returned. When an asynchronous command is issued, switching from the normal mode to the power saving mode may be performed in a state where no return value is returned.

  Next, an operation example of this embodiment will be described. The image forming apparatus 1000 operates in a normal mode or a power saving mode. In the normal mode, the first control unit 100, the second control unit 200, and the device 300 are energized. The first control means 100 satisfies a predetermined condition such as when the user's operation has not been performed for a predetermined time or when input from an external device has not been performed for a predetermined time. If so, the mode shifts to a power saving mode that suppresses power consumption. When the first control unit 100 shifts to the power saving mode, the first control unit 100 stops the power supply to the device predetermined in the device 300 and the second control unit 200. When the power supply to the second control unit 200 is stopped, the drivers 7, 8, and 9, the tasks 24, 25, and 26, the inter-OS communication driver 22 and the second OS 23 that have been operating in the second control unit 200 are terminated.

  When a predetermined interrupt occurs in the power saving mode, the first control unit 100 returns to the normal mode in which the second control unit 200 and the device 300 are energized. When the first control unit 100 returns to the normal mode, the first control unit 100 supplies power to the second control unit 200 and the device whose power supply has been stopped in the device 300. The second control unit 200 to which the power is supplied restarts the second OS 23 and restarts the inter-OS communication driver 22 and the drivers 7, 8, and 9.

FIG. 3 is a sequence diagram for explaining an operation example when returning from the power saving mode to the normal mode. For example, when there is an incoming call, the FAX unit 301 outputs an interrupt signal to the first OS 20 (step S1). This interrupt signal is an example of a notification for returning the second control unit 200 from the power saving mode to the normal mode. This interrupt signal is sent to the first OS 20 via the PCIe 21 without passing through the second OS 23. When acquiring the interrupt signal from the FAX unit 301, the first OS 20 instructs the command issuing unit 56 to access the device that has output the interrupt signal (step S2). Upon receiving this instruction, the command issuing unit 56 accesses the FAX unit 301 via the PCIe 21 without passing through the second OS 23, and instructs the start of FAX communication (step S3).

  Next, the first OS 20 energizes the second control means 200 (step S4). When the second control means 200 is energized, the second OS 23 is activated (step S5). The activated second OS 23 activates the drivers 7, 8, and 9 (step S6, step S7, and step S8).

  When the drivers 7, 8, and 9 are activated, the second OS 23 notifies the command issuing unit 56 of the completion of driver initialization by the inter-OS communication driver 22 (step S9). Upon receiving this notification, the command issuing unit 56 reissues the open command and reissues the ioctl command.

  Here, the command issuing unit 56 determines the order of command reissuance according to the device that has output the interrupt signal. Specifically, the command 29 is reissued to the communication path corresponding to the device that has output the interrupt signal. As described above, when the device that has output the interrupt signal is the FAX unit 301, the command issuing unit 56 first reissues an open command to the communication path 47 through inter-OS communication (step S10). The inter-OS communication driver 22 passes the received open command to the task 24. Upon receiving the command 29, the task 24 converts the open command into a system call 11 interpreted by the driver 7, and calls the driver 7 by the system call 11 via the API 4. The called driver 7 executes processing according to the contents of the system call 11, and returns a return value 12 representing the execution result of the processing to the task 24 via the API 4 (step S11). The task 24 that has received the return value 12 converts the return value 12 into a status 30 that is interpreted in common by the first OS 20 and the second OS 23 in order to pass the contents of the return value 12 to the first OS 20. Pass to 22. The inter-OS communication driver 22 transmits this status 30 to the command issuing unit 56 by inter-OS communication. Next, the command issuing unit 56 reissues the ioctl command to the communication path 47 through inter-OS communication (step S12). The driver 7 called by the system call 11 corresponding to this command executes a process corresponding to the content of the system call 11 and returns a return value 12 representing the execution result of the process (step S13). By reissuing the command to the driver 7, the process 1 that performs FAX processing and the driver 7 that controls the FAX unit 301 can communicate with each other. In addition, since the command is reissued to the communication path 47 corresponding to the FAX unit 301 that has output the interrupt signal, the command to the communication path 47 is performed after the command is reissued to the communication paths 48 and 49. Compared to the configuration in which reissuing is performed, the time until the processing for the FAX unit 301 that has caused the return to the normal mode can be started is shortened.

  Since the response from the FAX unit 301 to the access in step S3 is known in advance, the command issuing unit 56 receives the command from the FAX unit 301 for the access in step S3 after reissuing the command to the communication path 47 is completed. A response similar to the response is notified to the process 1 that performs FAX processing without waiting for a response from the FAX unit 301 (step S14). Compared with the configuration in which the response from the FAX unit 301 to the access in step S3 is waited and the acquired response is notified to the process 1, the time until the process 1 can start processing on the FAX unit 301 is shortened.

Next, the command issuing unit 56 reissues the open command to the communication path 48 (step S15). The driver 8 is called by this open command. The driver 8 called by the reissued open command returns a return value 12 (step S16). Further, the command issuing unit 56 reissues the ioctl command to the communication path 48 (step S17). The driver 8 is called by this ioctl command. The driver 8 called by the reissued ioctl command returns a return value 12 (step S18). In addition, the command issuing unit 56 reissues the open command to the communication path 49 (step S19). The driver 9 is called by this open command. The driver 9 called by the reissued open command returns a return value 12 (step S20). Further, the command issuing unit 56 reissues the ioctl command to the communication path 49 (step S21). The driver 9 called by the reissued ioctl command returns a return value 12 (step S22).

  When the FAX unit 301 finishes the processing for the access in step S3, the FAX unit 301 outputs a response to the access to the driver 7 (step S23). The driver 7 notifies the command issuing unit 56 of the response from the FAX unit 301 via the inter-OS communication driver 22 and the PCIe 21 (step S24). Since the command issuing unit 56 notifies the response similar to this response in step S14, the command issuing unit 56 discards the notification (step S25) and does not notify the process 1 that performs the FAX processing.

  FIG. 4 is a sequence diagram for explaining another operation example when returning from the power saving mode to the normal mode. For example, when the key of the UI 303 is operated in the power saving mode, the UI 303 outputs an interrupt signal to the first OS 20 (step S31). This interrupt signal is an example of a notification for returning the second control unit 200 from the power saving mode to the normal mode. This interrupt signal is sent to the first OS 20 via the PCIe 21 without passing through the second OS 23. When acquiring the interrupt signal from the UI 303, the first OS 20 instructs the command issuing unit 56 to access the device that has output the interrupt signal (step S32). Upon receiving this instruction, the command issuing unit 56 accesses the UI 303 via the PCIe 21 without passing through the second OS 23, and instructs the initialization of the UI 303 (step S33).

  Next, the first OS 20 energizes the second control means 200 (step S34). When the second control means 200 is energized, the second OS 23 is activated (step S35). The activated second OS 23 activates the drivers 7, 8, and 9 (step S36, step S37, and step S38).

  When the drivers 7, 8, and 9 are activated, the second OS 23 notifies the command issuing unit 56 of the completion of driver initialization by the inter-OS communication driver 22 (step S39). Upon receiving this notification, the command issuing unit 56 reissues the open command and reissues the ioctl command.

Here, the command issuing unit 56 first reissues a command to the driver of the device that has output the interrupt signal. As described above, when the device that has output the interrupt signal is the UI 303, the command issuing unit 56 first reissues an open command to the communication path 49 through inter-OS communication (step S40). The inter-OS communication driver 22 passes the received open command to the task 26. Upon receiving the open command, the task 26 converts the open command into a system call 11 interpreted by the driver 9 and calls the driver 9 by the system call 11 via the API 6. The called driver 9 executes processing according to the contents of the system call 11, and returns a return value 12 representing the execution result of the processing to the task 26 via the API 6 (step S41). The task 26 that has received the return value 12 converts the return value 12 into a status 30 that is interpreted in common by the first OS 20 and the second OS 23 in order to pass the contents of the return value 12 to the first OS 20. Pass to 22. The inter-OS communication driver 22 transmits this status 30 to the command issuing unit 56 by inter-OS communication. Next, the command issuing unit 56 reissues the ioctl command to the communication path 49 by the inter-OS communication (step S42). The driver 9 called by the system call 11 corresponding to this command executes a process corresponding to the content of the system call 11 and returns a return value 12 indicating the execution result of the process (step S43). By reissuing the command to the driver 9, the process 3 that performs UI processing and the driver 9 that controls the UI 303 can communicate with each other. In addition, since the command is reissued to the communication path 49 corresponding to the UI 303 that has output the interrupt signal, the command is reissued to the communication paths 47 and 48, and then the command to the communication path 49 is reissued. Compared to the configuration for issuing, the time until the processing for the UI 303 that has caused the return to the normal mode can be started is shortened.

  Note that since the response from the UI 303 with respect to the access at step S33 is known in advance, the command issuing unit 56 is similar to the response from the UI 303 with respect to the access at step S33 after the reissue of the command to the communication path 49 is completed. The response is notified to the process 3 that performs UI processing without waiting for a response from the UI 303 (step S44). In comparison with the configuration in which the response from the UI 303 to the access in step S33 is waited and the acquired response is notified to the process 3, the time until the process 3 can start the process on the UI 303 is shortened.

  Next, the command issuing unit 56 reissues the open command to the communication path 47 (step S45). The driver 7 is called by this open command. The driver 7 called by the reissued open command returns a return value 12 (step S46). Further, the command issuing unit 56 reissues the ioctl command to the communication path 47 (step S47). The driver 7 is called by this ioctl command. The driver 7 called by the reissued ioctl command returns a return value 12 (step S48). In addition, the command issuing unit 56 reissues an open command to the communication path 48 (step S49). The driver 8 is called by this open command. The driver 8 called by the reissued open command returns a return value 12 (step S50). Further, the command issuing unit 56 reissues the ioctl command for the communication path 48 (step S51). The driver 8 is called by this ioctl command. The driver 8 called by the reissued ioctl command returns a return value 12 (step S52).

  When the UI 303 finishes the processing for the access in step S33, the UI 303 outputs a response to the access to the driver 9 (step S53). The driver 9 notifies the response from the UI 303 to the command issuing unit 56 via the inter-OS communication driver 22 and the PCIe 21 (step S54). Since the command issuing unit 56 notifies the response similar to this response in step S44, the command issuing unit 56 discards the notification (step S55) and does not notify the process 3 that performs UI processing.

[Modification]
As mentioned above, although embodiment of this invention was described, this invention is not limited to embodiment mentioned above, It can implement with another various form. For example, the present invention may be implemented by modifying the above-described embodiment as follows. In addition, you may combine each of embodiment mentioned above and the following modifications.

In the embodiment described above, the first OS 20 that has acquired the interrupt signal instructs the command issuing unit 56 to access the device, and the command issuing unit 56 that has acquired this instruction is accessing the device, but outputs the interrupt signal. The configuration for accessing the device is not limited to the configuration of the embodiment. For example, in the present invention, after the first OS 20 acquires the interrupt signal, the second OS 23 and the drivers 7, 8, and 9 may be activated, and the activated driver may access the device that has output the interrupt signal. When the driver accesses the device that has output the interrupt signal, the command issuing unit 56 may notify the process that controls the device that has output the interrupt signal without discarding the response from the device.

  In the embodiment described above, the notification in step S14 is performed after the reissuance of the command to the driver 7 that controls the FAX unit 301 that has output the interrupt signal is completed. Notification may be made while the return value to the reissue of the ioctl command is acquired, that is, between step S15 and step S18. Further, the notification in step S14 may be notified between step S19 and step S24.

  In the embodiment described above, a response similar to the response to the access to the device is notified to the process before the response is output, and the response to the access to the device is discarded. May not notify the process of a response similar to the response to access to the device before the response is output, and may notify the process without discarding the response to access to the device.

1, 2, 3 ... process, 4, 5, 6 ... API, 7, 8, 9 ... driver, 11 ... system call, 12 ... return value, 13, 14, 15 ... API, 16, 17, 18 ... library, DESCRIPTION OF SYMBOLS 19 ... OS communication driver, 20 ... 1st OS, 21 ... PCIe, 22 ... OS communication driver, 23 ... 2nd OS, 24, 25, 26 ... Task, 27 ... Function, 28 ... Return value, 29 ... Command, 30 ... Status, 47, 48, 49 ... Communication path, 56 ... Command issuing unit, 100 ... First control means, 101 ... CPU, 102 ... RAM, 103 ... ROM, 104 ... Communication I / F, 105 ... HDD, 106 ... LAN terminal, 110 ... bus, 200 ... second control means, 201 ... CPU, 202 ... RAM, 203 ... ROM, 210 ... bus, 300 ... device, 301 ... FAX unit, 302 ... image formation , 303 ... UI, 1000 ... image forming apparatus

Claims (7)

A second control means for executing a second operating system and operating a plurality of device drivers provided for each of a plurality of devices to be controlled on the second operating system;
When the first operating system is executed and a process corresponding to the device operates on the first operating system and the second control unit is returned from the power saving state, a notification is received from the device. Reissue the commands issued before entering the power saving state for the device driver corresponding to the device that output the notification, and change the order of the reissues to the commands issued to other device drivers. And a first control means for making the order earlier than the issuing order. The second control means acquires a response to access to the device that has output the notification, and supplies the response to the first control means,
The control device according to claim 1, wherein the first control unit supplies the response to the process before the response is supplied from the second control unit. The control apparatus according to claim 2, wherein the first control unit supplies the response to the process before reissuing the command to a device driver other than a device driver corresponding to the device that has output the notification. . The control device according to claim 3, wherein the first control unit discards the response supplied from the second control unit. The control apparatus according to claim 2, wherein when the notification is acquired, the first control unit accesses the device that has output the notification before restarting the second operating system. The control device according to claim 5, wherein the first control unit accesses the device without going through the second operating system and the device driver when the notification is acquired. Computer
Means for executing a first operating system and a process corresponding to a device operating on the first operating system;
When a notification for returning the second control unit that executes the device driver corresponding to the device from the power saving state is acquired from the device, the device driver corresponding to the device that has output the notification enters the power saving state. A program for re-issuing previously issued commands and for causing the re-issue order to function as a control means that is faster than the re-issue order of commands issued to other device drivers.

Images