JP3674446B2 - Individual application patch management apparatus and individual application patch management method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
  The present invention executes a specific application (hereinafter referred to as a specific application) that requires application of a specific patch (hereinafter referred to as an individual patch) other than a patch generally applied to an OS (operating system). The individual application patch management apparatus and individual application patch management method for managing the application of individual patches to an OS, particularly when a task is switched between specific applications, the application status of the individual patches to the OS is changed according to the switching of the specific application. The present invention relates to an individual application patch management apparatus and an individual application patch management method that are dynamically switched.
[0002]
[Prior art]
  Conventionally, a patch applied to an OS generally affects all applications. However, if a patch required by a specific application is applied to the OS, a problem may occur when another application is executed.
[0003]
  Here, as specific examples of the prior art having a technical field similar to that of the present invention, there are those disclosed in JP-A-5-241814 and JP-A-3-166624.
[0004]
  When executing a load module already modified by a patch, all the patches are reflected when the load module is loaded. Previously, if you wanted to modify some of the patches and execute the load module, you modified the load module before executing it.
[0005]
  On the other hand, Japanese Patent Application Laid-Open No. 5-241814 provides a patch management apparatus that can correct and delete patches already stored in a load module at the time of execution, and can easily execute the load module according to the application.
[0006]
  Similarly, in Japanese Patent Application Laid-Open No. 3-166624, when executing a load module modified by a patch, all patches are unconditionally reflected in the executable program when the load module is loaded. In the conventional example, patches are collectively managed, so that patches to be reflected in an execution format program when loading a load module can be selected according to use.
[0007]
[Problems to be solved by the invention]
  However, all of the above conventional examples require input of a patch correction instruction from the user in order to correct / delete the patch to be reflected in the execution format program in accordance with the application. Also, such patch correction based on the input of the patch correction instruction from the user is limited to the point in time when the patch correction instruction is input, and each time the usage changes, the user again inputs the patch correction instruction. Must be done.
[0008]
  Therefore, according to the present invention, when applying an individual patch required by a specific application to the OS, it is necessary to determine an individual patch required to be applied to the OS for each specific application and to input a patch correction instruction or the like from the user. The object is to provide an individual application patch management apparatus and an individual application patch management method capable of dynamically switching the patch application status to the OS when executing a specific application.
[0009]
  In addition, the present invention determines a specific patch (hereinafter also referred to as an individual patch) that is required to be applied to each user for one application, and does not require input from the user such as a patch correction instruction. It is an object of the present invention to provide an individual application patch management apparatus and an individual application patch management method capable of dynamically switching the patch application status for an application for each user who uses it.
[0010]
  In addition, when the user does not use a specific application, or when the user devises a bug avoidance such as processing the output file, the input from the user from the outside, An object of the present invention is to provide an individual application patch management apparatus and an individual application patch management method for invalidating individual patch application to an OS requested by a specific application or changing the level of individual patch application to an OS requested by the specific application. And
[0011]
  Furthermore, the present invention avoids applying an unnecessary individual patch to the OS when it is not preferable to apply the individual patch required by the specific application to the OS when the user uses the specific application. An object of the present invention is to provide an individual application patch management apparatus and an individual application patch management method.
[0012]
[Means for Solving the Problems]
  In order to achieve this object, according to the first aspect of the present invention, when a task is switched to a specific application as a task switch in the OS, the specific application is applied to the OS when there is a memory access. The content of the TLB (Translation-Lookaside buffer) is rewritten so as to point to the virtual address in the virtual storage space of the requested individual patch.
[0013]
  The invention described in claim 2 is the memory access using the virtual address of the kernel file in the invention described in claim 1 by rewriting the virtual address of the kernel file in which the individual patch is registered in the TLB to the virtual address of the individual patch. The TLB content is rewritten so as to point to the virtual address of the individual patch when there is an error.
[0014]
  The invention according to claim 3 reads a kernel file.Virtual memory on virtual storage spaceIf an individual patch that requires a specific application to apply to the OS is registered for the kernel file, the individual patch is read into the virtual storage space and the kernel fileVirtual storage spaceKernel reading means for outputting the virtual address, the virtual address on the virtual storage space of the individual patch, and the name of the specific application as information, and a TLB replacement page table for holding the information output from the kernel reading means in a table format And OS task switching means for detecting task switching to the specific application as task switching in the OS, and when the OS task switching means detects switching of the task to the specific application, the detected specific application On the virtual storage space registered with the name of the specific application.Of the individual patchVirtual address andIn virtual memoryofKernel fileA TLB (Translation-Lookaside buffer) is rewritten based on a virtual address.
[0015]
  The invention according to claim 4 is the virtual address of the kernel file in the invention according to claim 3, when the switching of the task to the specific application is detected by the OS task switching means.Associated with TLBRegisteredHaveFruitmemoryUpNodressThe, The virtual address on the virtual storage space of the individual patchsoRewriteGetIt is characterized by that.
[0016]
  According to a fifth aspect of the present invention, in the third or fourth aspect of the invention, the kernel reading means starts from the relative address from the head of the kernel file of the kernel file before being read and the head of the individual patch of the individual patch before being read. When the relative address matches, it is determined that the individual patch is registered in the kernel file, and the kernel file isVirtual memoryAs well as individual patches in the virtual storage space, and the names of specific applications and kernel filesVirtual memoryThe upper virtual address and the virtual address on the virtual storage space of the individual patch are written in the TLB replacement table.
[0017]
  According to the sixth aspect of the present invention, when a user switch occurs as a task switch in an application, a virtual address on a virtual storage space of an individual patch that the user requests to apply to the application when there is a memory access. As indicated, the contents of TLB (Translation-Lookaside buffer) are rewritten.
[0018]
  The invention described in claim 7 provides the memory access using the virtual address of the application file by rewriting the virtual address of the application file in which the individual patch is registered in the TLB to the virtual address of the individual patch. The TLB content is rewritten so as to point to the virtual address of the individual patch when there is an error.
[0019]
  The invention according to claim 8 reads an application file.Virtual memory on virtual storage spaceIf an individual patch that the user requests to apply to the application file is registered for the application file, the individual patch is read into the virtual storage space, and the application fileVirtual storage spaceAn application reading means for outputting the virtual address, the virtual address on the virtual storage space of the individual patch, and the user name as information, and a TLB replacement page table for holding the information output from the application reading means in a table format And application task switching means for detecting task switching to the user as task switching in the application, and when the task switching to the user is detected by the application task switching means, the name of the detected user is TLB. If it is registered on the replacement page table, it will be registered on the virtual storage space registered with the user's name.Individual patchVirtual address andIn virtual memoryofApplication fileThe content of TLB (Translation-Lookaside buffer) is rewritten based on the virtual address.
[0020]
  The invention according to claim 9 is the invention according to claim 8, wherein when switching of the task to the user is detected by the application task switching means,applicationThe virtual address of the fileIn association with TLBRegisteredHaveOn real memoryNodressThe, The virtual address on the virtual storage space of the individual patchsoRewriteGetIt is characterized by that.
[0021]
  According to a tenth aspect of the present invention, in the invention according to the eighth or ninth aspect, the application reading means starts from the relative address from the top of the application file of the application file before being read, and the individual patch head of the individual patch before being read. When the relative address matches, it is determined that the individual patch is registered in the application file, and the application file isVirtual memoryIn addition to placing individual patches on the virtual storage space, user names and application filesVirtual memoryThe upper virtual address and the virtual address on the virtual storage space of the individual patch are written in the TLB replacement table.
[0022]
  According to an eleventh aspect of the present invention, in the invention according to any one of the first to fifth aspects, the individual application patch management device is further configured to enable / disable the application of the individual patch to the OS by the specific application based on an input operation from the user. Individual patch application valid / invalid designation means for designating invalidity, and mask means for masking entries in the TLB replacement page table based on the designation in the individual patch application valid / invalid designation means.
[0023]
  According to a twelfth aspect of the present invention, in the invention according to any one of the first to fifth aspects, the individual application patch management device further sets an application level of the individual patch to the OS for each specific application based on an input operation from the user. An individual patch application level designating unit for designating and a masking unit for masking an entry in the TLB replacement page table based on the designation in the individual patch application level designating unit.
[0024]
  According to the thirteenth aspect of the present invention, when a task is switched to a specific application as a task switch in the OS, a virtual storage space of an individual patch that the specific application requests to apply to the OS when there is a memory access The content of TLB (Translation-Lookaside buffer) is rewritten so as to point to the upper virtual address.
[0025]
  In the invention described in claim 14, in the invention described in claim 13, memory access is performed using the virtual address of the kernel file by rewriting the virtual address of the kernel file in which the individual patch is registered in the TLB to the virtual address of the individual patch. The TLB content is rewritten so as to point to the virtual address of the individual patch when there is an error.
[0026]
  The invention according to claim 15 reads a kernel file.Virtual memory on virtual storage spaceIf an individual patch that requires a specific application to apply to the OS is registered for the kernel file, the individual patch is read into the virtual storage space and the kernel fileVirtual memoryThe above-described virtual address, the virtual address in the virtual storage space of the individual patch, and the name of the specific application are output as information, and the information output by the kernel reading process is written in the TLB replacement page table in a table format. An information writing step, and an OS task switching step for detecting task switching to a specific application as task switching in the OS, and is detected when task switching to the specific application is detected by the OS task switching step. If the name of the specific application is registered on the TLB replacement page table, the virtual application is registered with the name of the specific application.Individual patchVirtual address andIn virtual memoryofKernel fileThe content of the TLB is rewritten based on the virtual address.
[0027]
  The invention according to claim 16 is the virtual address of the kernel file in the invention according to claim 15 when the task switching to the specific application is detected by the OS task switching step.In association with TLBRegisteredHaveOn real memoryNodressThe, The virtual address on the virtual storage space of the individual patchsoRewriteGetIt is characterized by that.
[0028]
  The invention according to claim 17 is the invention according to claim 15 or 16, wherein, in the kernel reading step, the relative address from the head of the kernel file before being read and the head of the individual patch of the individual patch before being read. When the relative address matches, it is determined that the individual patch is registered in the kernel file, and the kernel file isVirtual memoryAs well as individual patches in the virtual storage space, and the names of specific applications and kernel filesVirtual memoryThe upper virtual address and the virtual address on the virtual storage space of the individual patch are written in the TLB replacement table.
[0029]
  In the invention described in claim 18, when a user switching occurs as a task switching in an application, a virtual address on a virtual storage space of an individual patch requested by the user to be applied to the application when there is a memory access. As indicated, the contents of TLB (Translation-Lookaside buffer) are rewritten.
[0030]
  According to a nineteenth aspect of the present invention, in the invention of the eighteenth aspect, by rewriting the virtual address of the application file in which the individual patch is registered in the TLB to the virtual address of the individual patch, the memory access is performed with the virtual address of the application file. The TLB content is rewritten so as to point to the virtual address of the individual patch when there is an error.
[0031]
  The invention according to claim 20 reads an application file.Virtual memory on virtual storage spaceIf an individual patch that the user requests to apply to the application file is registered for the application file, the individual patch is read into the virtual storage space, and the application fileVirtual memoryThe application reading process for outputting the virtual address, the virtual address on the virtual storage space of the individual patch, and the user name as information, and information for writing the information output by the application reading process to the TLB replacement page table in a table format A writing process and an application task switching process for detecting a task switching to the user as a task switching in the application, and when the task switching to the user is detected by the application task switching process, If the name is registered on the TLB replacement page table, the virtual storage space is registered with the user's name.Individual patchVirtual address andIn virtual memoryofApplication fileThe content of TLB (Translation-Lookaside buffer) is rewritten based on the virtual address.
[0032]
  The invention according to claim 21 is the invention according to claim 20, wherein switching of a task to the user is detected by the application task switching means.applicationThe virtual address of the fileIn association withRegisteredHaveOn real memoryNodressThe, The virtual address on the virtual storage space of the individual patchsoRewriteGetIt is characterized by that.
[0033]
  The invention according to claim 22 is the invention according to claim 20 or 21, wherein, in the application reading step, the relative address from the beginning of the application file of the application file before being read and the beginning of the individual patch of the individual patch before being read. When the relative address matches, it is determined that the individual patch is registered in the application file, and the application file isVirtual memoryIn addition to placing individual patches on the virtual storage space, user names and application filesVirtual memoryThe upper virtual address and the virtual address on the virtual storage space of the individual patch are written in the TLB replacement table.
[0034]
  According to a twenty-third aspect of the present invention, in the invention according to any one of the thirteenth to seventeenth aspects, the individual application patch management method further includes: enabling / disabling the application of the individual patch to the OS by the specific application based on an input operation from the user. An individual patch application valid / invalid designation process for designating invalidity, and a mask process for masking an entry in the TLB replacement page table based on designation in the individual patch application valid / invalid designation process.
[0035]
  According to a twenty-fourth aspect of the present invention, in the invention according to any one of the thirteenth to seventeenth aspects, the individual application patch management method further sets an application level of the individual patch to the OS for each specific application based on an input operation from the user. An individual patch application level designating step for designating and a masking process for masking an entry in the TLB replacement page table based on the designation in the individual patch application level designating step.
[0036]
DETAILED DESCRIPTION OF THE INVENTION
  Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
[0037]
  FIG. 1 is a diagram showing a schematic configuration of an individual application patch management apparatus and a schematic configuration of processing by an individual application patch management method according to an embodiment of the present invention. In FIG. 1, 1 is an OS switching unit that detects task switching when a task switching occurs in the OS, 2 is a TLB replacement page table that designates switching of a virtual address page for each application, The kernel, which is the basic part of the OS stored in the hard disk, etc., 4 is an individual patch that is also stored in the hard disk etc. and prepared for each application, and 5 reads the kernel file from the kernel 3 in units of pages, for example. If the individual patch is registered for the kernel file, the kernel reading means (usually, the individual patch 4 is read from the individual patch 4 and the information for specifying the switching of the virtual address page is registered in the TLB replacement page table. Boot load), 6 is a virtual TLB associating the space and the real memory (Translation-Lookaside buffer), 7 is arranged kernel file loaded by the kernel reading means 5Virtual memory, 8 are individual patch spaces in which individual patches read by the kernel reading means 5 are arranged.
[0038]
  Next, the operation of the individual application patch management apparatus and the individual application patch management method in this embodiment will be described with reference to the flowcharts of FIGS.
[0039]
  When the OS is started, the kernel reading unit 5 reads a kernel file from the kernel 3 (step S1). Normal,Virtual memory7 and the virtual storage space are managed by the concept of pages, and are divided into about 16 Kbytes. This sizeVirtual memory7 and a normal minimum management unit in the virtual storage space. In the present embodiment, the kernel reading unit 5 reads the kernel file and individual patches in units of one page.
[0040]
  The kernel reading means 5 reads the read kernel file.Virtual memory7 (step S2), it is determined whether or not an individual patch is registered in the kernel file (step S3). If the individual patch is registered (step S3 / YES), the kernel file is read and the individual patch registered in the kernel file is read and arranged in the individual patch space 8 (step S4). If the individual patch is not registered (step S3 / NO), the process proceeds to step S6 described later, and it is determined whether all kernel files have been read from the kernel 3.
[0041]
  As described above, when the kernel reading unit 5 places an individual patch on the individual patch space 8, the name of the application requesting the patch application to the OS of the individual patch and the kernel file in which the individual patch has been registered.Virtual memoryThe correspondence between the virtual address page number on 7 and the virtual address page number on the individual patch space 8 of the individual patch is written into the TLB replacement table 2 (step S5).
[0042]
  Next, the kernel reading means 5 determines whether or not reading has been completed for all the kernel files accommodated in the kernel 3 (step S6). If it is determined in this determination that all kernel files have been read (step S6 / YES), the above processing is terminated. On the other hand, if it is determined that all the kernel files accommodated in the kernel 3 have not been read (step S6 / NO), the above processing is continued for the kernel file that has not been read. .
[0043]
  The OS task switching means 1 determines whether or not application switching has occurred as OS task switching (step S11). If it is determined in this determination that application switching has not occurred (step S11 / NO), the OS task switching unit 1 continues to monitor task switching. On the other hand, when it is determined that the application switching has occurred (step S11 / YES), the OS task switching unit 1 obtains the name of the application to which the task is transferred next (step S12).
[0044]
  Next, it is determined whether or not the application name obtained in step S12 exists on the TLB replacement table 2 (step S12). In this determination, when it is determined that the application name does not exist on the TLB replacement table 2 (step S13 / NO), the process returns to step S11. On the other hand, when it is determined that the name of the application exists on the TLB replacement table 2 (step S13 / YES), on the TLB replacement table 2Climb toRecordedHaveRuVirtual memoryAll virtual address page numbers on 7aboutCorresponding to their virtual address page numberTo TLB replacement table 2RegisteredingVirtual address page number on the individual patch space 8soThe contents of TLB 6 are rewritten (step S14). Thereafter, control is passed to the function of the virtual storage system of the OS described later (step S15).
[0045]
  Rewritten like thisVirtual memory7 If there is external memory access to the virtual address page number onVirtual memorySince the virtual address page number on 7 is rewritten to the virtual address page number on the individual patch space 8, it is linked to the page on the individual patch space 8 indicated by the virtual address page number.
[0046]
  However, the individual patches on the individual patch space 8 are actual memos.ReTherefore, a page fault occurs when the memory is accessed. Therefore, the virtual storage system of the OS causes the individual patch existing on the individual patch space 8 to be actually recorded due to this page fault.ReAnd read this real memoReFree spaceNoA dress page number is newly registered as TLB contents.
[0047]
  Next, the operation of the individual application patch management apparatus and the individual application patch management method in the present embodiment will be specifically described with reference to FIGS. 4 and 5.
[0048]
  The kernel reading means 5 reads the actual memo sequentially from the top of the kernel file for each page unit from the hard disk or the like.ReArranged in orderYouThe In this reading operation, a kernel file to be read is specified by an address represented by a relative page number from the top of the kernel file.
[0049]
  Further, when reading the kernel file by the above operation, the kernel reading means 5 determines whether or not an individual patch is registered for each kernel file.YouThe Details of this determination operation will be described below.
[0050]
  As described above, the address of the kernel file is managed by the relative page number from the head of the kernel file on the hard disk or the like. Similarly, the address of each individual patch is managed by the relative page number from the head of the individual patch for each application. The kernel reading means 5 reads the kernel file from the kernel 3 by sequentially specifying the relative page numbers, and whether there is an individual patch at the address of the relative page number that matches the relative page number in the individual patch 3. Determine whether or not. If it exists, the kernel reading means 5 determines that the individual patch is registered in the read kernel file.
[0051]
  In addition, when a plurality of individual patches are registered in one kernel file (for example, when application A and application B are registered in one kernel file), the kernel reading unit 5 stores these individual patches. Individually arranged in the individual patch space 8, application A and application B as application names, virtual address page numbers of those individual patches in the individual patch space, and the kernel file in which those individual patches are registeredVirtual memory 7The upper virtual address page number is written on the TLB replacement page table 2.
[0052]
  When it is determined that the individual patch is registered in the kernel file read in this way, the kernel reading means 5 reads the kernel file.Virtual memory7, and the individual patch entities registered in the kernel file are arranged in the individual patch space 8.
[0053]
  The individual patch space 8 is an area existing on the virtual storage space. For the virtual storage space management function of the OS, all virtual address page numbers in the virtual storage space to which the individual patch space 8 belongs are reserved, and management information that the area exists on the hard disk is passed.
[0054]
  According to FIG. 4, when the kernel file having the relative page number 1 is read by the kernel reading means 5 in the kernel 3, as shown in FIG.Virtual memory7 is arranged in the area above. Further, the kernel reading unit 5 determines for each application whether or not the individual patch stored in the relative page number 1 exists in the individual patch 3. In the embodiment shown in the figure, individual patches required by the application A are registered.
[0055]
  The kernel reading means 5 compares the relative page number between the individual patch requested by the application A and the read kernel file. As a result of comparison, the individual patches match each other with the relative page number 1. It is arranged on the individual patch space 8. In addition, the kernel reading means 5Virtual memory7 write the virtual address page number of the kernel file on 7, the virtual address page number of the individual patch on the individual patch space 8, and the name of the application A to the TLB replacement table.
[0056]
  Next, according to FIG. 5, the contents written in the TLB replacement page table 2 by the above operation of the kernel reading means 5 are:Virtual memory2 as the virtual address page number of the kernel file on 7, 1000 as the virtual address page number of the individual patch on the individual patch space 8, andProvisionalA is registered as the name of the application requesting the replacement of the virtual address page number 2 with the virtual address page number 1000.
[0057]
  Furthermore, according to this figure, as an example of TLB contents, virtual address page number 0 and real memoryNoDress page number 0, virtual address page number 1 and real memoryNoDress page number 3, virtual address page number 2, and real memoryNoDress page number 1 and virtual address page number 3 on real memoryNoDress page number 2 is associated.
[0058]
  As described above, when the kernel reading unit 5 writes the above contents in the TLB replacement page table 2 and the OS task switching unit 1 detects the switching of the task to the application A, the OS task switching unit 1 stores the TLB replacement page table 2 in the TLB replacement page table 2. Based on all the contents related to the application A being written, the contents of the TLB 6 are rewritten.
[0059]
  In the TLB replacement page table 2, the application AVirtual memoryAll the individual patches registered in relation to application A in the TLB replacement page table 2 for the part registered in the TLB 6 with the same virtual address page number as the virtual address page number registered on 7 TLB where the virtual address page number matches the space6The virtual address page number is rewritten to the virtual address page number on the individual patch space 8 by the application A in the TLB replacement page table 2.
[0060]
  For example, if virtual address page number 2 is input to the TLB as an external memory access, virtual address page number 2 and the actual memoALink with dress page number 1 is released,AThe area on the real memory indicated by the dress page number 1 is released.
[0061]
  In the TLB replacement page table 2, the virtual address page number 2 andIndividual patch space 8Since the upper virtual address page number 1000 is registered in association with the TLB 6, the virtual address page number 2 is rewritten from the virtual address page number 2 to the virtual address page number 1000 on the individual patch space 8. Therefore, when the memory access of the virtual address page number 2 is performed, the virtual address page number 1000 on the individual patch space 8 is accessed instead.
[0062]
  However, the virtual address page number 1000 exists in the individual patch space 8 and is a real memo.ToSince it is not an area to which it belongs, a memory fault occurs during this access. When a memory fault occurs, the actual patch of the individual address of the virtual address page number 1000 is actually recorded by the function of the OS virtual storage system.ReFree space (here:ADress page number 4 area), and the contents of TLB6 are newlyADress page number 4 is registered corresponding to virtual address page number 2.
[0063]
  The application of the individual patch required for the OS for each application has been described above. However, as another embodiment of the present invention, the case of applying the individual patch required for the application for each user will be described. To do.
[0064]
  FIG. 6 is a diagram showing a schematic configuration of the individual application patch management apparatus and a schematic configuration of processing by the individual application patch management method in the present embodiment. In FIG. 6, 11 is an application task switching means for detecting task switching when a task is switched in an application, 12 is a TLB replacement page table that designates switching of a virtual address page for each user, 13 Is an application stored in a hard disk or the like, 14 is an individual patch that is also stored in the hard disk or the like and is prepared for each user, and 15 is an application that reads an application file, for example, on a page basis from the application 13. On the other hand, if an individual patch is registered, an application for reading the individual patch from the individual patch 14 and registering information for designating switching of the virtual address page in the TLB replacement page table 12 Means narrowing seen, 16, TLB, 17 associating the virtual memory space and the real memory, the application file loaded by the application reading means 15 are arrangedVirtual memory, 18 is an individual patch space in which the individual patches read by the application reading means 15 are arranged.
[0065]
  Next, the operation of the individual application patch management apparatus and the individual application patch management method in this embodiment will be described with reference to the flowcharts of FIGS.
[0066]
  When the OS is activated, the application reading unit 15 reads an application file from the application 13 (step S21). Also in this embodiment, it is assumed that the application reading unit 15 performs an operation of reading application files and individual patches in units of one page.
[0067]
  Next, the application reading means 15 reads the read application file.Virtual memory17 (step S22), and each time it is determined whether or not an individual patch is registered in the application file (step S23). If the individual patch has been registered (step S23 / YES), the application file is read and the individual patch registered in the application file is read and arranged in the individual patch space 18 (step S24). If the individual patch is not registered (step S23 / NO), it is determined whether all application files have been read from the application 13 in step S26 described later.
[0068]
  As described above, when the application reading unit 15 arranges an individual patch in the individual patch space 18, the user name requesting the application of the individual patch to the OS of the OS and the application file in which the individual patch is registered.Virtual memoryThe correspondence between the virtual address page number on 17 and the virtual address page number on the individual patch space 18 of the individual patch is written in the TLB replacement table 12 (step S25).
[0069]
  Next, the application reading unit 15 determines whether reading has been completed for all application files accommodated in the application 13 (step S26). When it is determined that the reading has been completed (step S26 / YES), the above processing is terminated. On the other hand, when it is determined that reading has not been completed for all application files accommodated in the application 13 (step S26 / NO), processing is continued for application files that have not been read.
[0070]
  The application task switching means 11 determines whether or not a user switching has occurred as a switching of application tasks (step S31). In this determination, when it is determined that no user switching has occurred (step S31 / NO), the application task switching unit 11 continues to monitor task switching. On the other hand, when it is determined that the user switching has occurred (step S31 / YES), the application task switching unit 11 obtains the name of the next user (step S32).
[0071]
  Next, it is determined whether or not the user name obtained in step S32 exists on the TLB replacement table 12 (step S32). In this determination, when it is determined that the user name does not exist on the TLB replacement table 12 (step S33 / NO), the process returns to step S31. On the other hand, when it is determined that the name of the user exists on the TLB replacement table 12 (step S33 / YES), on the TLB replacement table 12Climb toRecordedHaveRuVirtual memoryAll virtual address page numbers on 17aboutCorresponding to their virtual address page numberIn TLB replacement table 12RegisteredingVirtual address page number on the individual patch space 18so, The content of the TLB 16 is rewritten (step S34). Thereafter, control is passed to the functions of the OS virtual storage system already described (step S35).
[0072]
  As another embodiment, individual patch application valid / invalid designation means that can designate validity / invalidity of application of an individual patch to an OS by a specific application based on an input operation from a user, or for each application based on an input operation from the user. 1 is added to the configuration of FIG. 1 with individual patch application level designation means that can designate the application level of the individual patches for the OS and masking means for masking entries in the TLB replacement page table 2 based on the designation made by these means. To do.
[0073]
  For example, when there is an application that is not used by the user and the application is a specific application that requires the OS to apply an individual patch, or the application is a specific application and the user When bug evasion is devised such as processing the output file above, the individual patch application valid / invalid designation means gives an instruction to invalidate the application of the individual patch to the OS by the specific application. The mask means receives this instruction and masks all entries related to the specific application in the TLB replacement page table 2.
[0074]
  As a result, the individual patch is not applied to the specific application under the above circumstances, and when the user is not using the application, waste of the application operation of the individual patch can be eliminated. In addition, if the user is trying to avoid bugs such as processing output files on a specific application, a problem will occur if the individual patch is applied to the OS, but the user disables the application of the individual patch. This point can also be avoided by giving the instruction.
[0075]
  In addition, when it is not preferable to apply an individual patch to the OS when a user uses a specific application, for example, a patch that improves calculation accuracy may slow down the calculation speed. The user inputs the contents to that effect to the individual patch application level designating unit so as to invalidate some of the individual patches applied to the OS by this application. The mask means receives a designation from the individual patch application level designation means and masks a portion corresponding to the invalid individual patch on the TLB replacement page table 2.
[0076]
  As a result, if the user wants to avoid unnecessary patch application when using a specific application, the patch application level can be applied by inputting the patch application level using the individual patch application level designation means. Can do.
[0077]
【The invention's effect】
  As is apparent from the above description, according to the present invention, when a patch required by a specific application is applied to the OS, a patch required to be applied to the OS is determined for each application, and a patch correction instruction or the like is determined. It is possible to dynamically switch the patch application status for the OS when executing a specific application without requiring input from the user.
[0078]
  In addition, according to the present invention, an individual patch that is required to be applied to each user for one application is determined, and input from the user such as a patch correction instruction is not required. The individual patch application status for the application can be dynamically switched for each user to use.
[0079]
  Further, according to the present invention, when a user does not use a specific application, or when the user devises bug avoidance such as processing an output file, an input from the user from outside The individual patch application to the OS required by the specific application can be disabled, or the level of individual patch application to the OS required by the specific application can be changed.
[0080]
  Furthermore, according to the present invention, when it is not preferable to apply the individual patch required by the specific application to the OS when the user uses the specific application, application of an unnecessary individual patch to the OS is avoided. be able to.
[Brief description of the drawings]
FIG. 1 is a diagram showing a schematic configuration of an individual application patch management apparatus and a schematic configuration of processing by an individual application patch management method according to a first embodiment of the present invention.
FIG. 2 is a first flowchart showing an operation of an individual application patch management apparatus and an individual application patch management method according to the first embodiment of the present invention.
FIG. 3 is a second flowchart showing the operation of the individual application patch management apparatus and the individual application patch management method in the first embodiment of the present invention.
FIG. 4 is a first diagram for specifically explaining the operation of the individual application patch management apparatus and the individual application patch management method according to the first embodiment of the present invention.
FIG. 5 is a second diagram for specifically explaining the operation of the individual application patch management apparatus and the individual application patch management method according to the first embodiment of the present invention.
FIG. 6 is a diagram showing a schematic configuration of an individual application patch management apparatus and a schematic configuration of processing by an individual application patch management method in the second embodiment of the present invention.
FIG. 7 is a second flowchart showing the operation of the individual application patch management apparatus and the individual application patch management method according to the second embodiment of the present invention.
FIG. 8 is a second flowchart showing the operation of the individual application patch management apparatus and the individual application patch management method according to the second embodiment of the present invention.
[Explanation of symbols]
  1 OS task switching means
  2,12 TLB replacement page table
  3 Kernel
  4, 14 Individual patch
  5 Kernel reading means
  6, 16 TLB
  7, 17Virtual memory
  8, 18 Individual patch space
  11 Application task switching means
  13 Application
  15 Application loading means

Claims (24)

  When task switching to a specific application occurs as task switching in the OS, it points to a virtual address in the virtual storage space of an individual patch that the specific application requests to apply to the OS when there is a memory access As described above, an individual application patch management apparatus characterized by rewriting the contents of a TLB (Translation-Lookaside buffer).   By rewriting the virtual address of the kernel file in which the individual patch is registered in the TLB to the virtual address of the individual patch, the virtual address of the individual patch is changed when memory access is performed using the virtual address of the kernel file. The individual application patch management apparatus according to claim 1, wherein the content of the TLB is rewritten to point. Together to arrange the kernel file into virtual memory read virtual memory space, the if the particular application to the kernel file if it is a separate patch registration requesting application to OS, the said individual patch virtual storage space A kernel reading means for outputting, as information, a virtual address on the virtual storage space of the kernel file, a virtual address on the virtual storage space of the individual patch, and a name of the specific application;
A TLB replacement page table that holds the information output from the kernel reading means in a table format;
OS task switching means for detecting task switching to the specific application as task switching in the OS,
When switching of the task to the specific application is detected by the OS task switching means, if the detected name of the specific application is registered on the TLB replacement page table, the name of the specific application is accompanied. The TLB (Translation-Lookaside buffer) is rewritten on the basis of the virtual address of the individual patch in the virtual storage space registered and the virtual address of the kernel file in the virtual memory. Patch management device. When the switching of the task to a particular application by the OS task switching means is detected, the virtual address registered in the TLB and associated real memory on the address Ru Tei of the kernel file of the individual patches individual application patch management apparatus according to claim 3, wherein the can exchange written in the virtual address on the virtual memory space. The kernel reading means includes
The individual patch is registered in the kernel file when the relative address from the beginning of the kernel file of the kernel file before being read matches the relative address from the beginning of the individual patch of the individual patch before being read. determining that said placing the individual patches in the virtual memory space with the kernel file is placed on the virtual memory, the name of a specific application, the virtual address of the virtual memory of the kernel file, and the individual 5. The individual application patch management apparatus according to claim 3, wherein a virtual address of the patch in the virtual storage space is written in the TLB replacement table.   When a user switch occurs as a task switch in an application, the TLB (points to a virtual address on the virtual storage space of the individual patch that the user requests to apply to the application when there is a memory access. Individual application patch management device characterized by rewriting the contents of Translation-Lookaside buffer).   By rewriting the virtual address of the application file in which the individual patch is registered in the TLB to the virtual address of the individual patch, the virtual address of the individual patch is changed when memory access is performed at the virtual address of the application file. The individual application patch management apparatus according to claim 6, wherein the content of the TLB is rewritten to point. Together to arrange the application file to the virtual memory of the read virtual storage space, if it is separate patch registration user for the application file requests application to the application, the individual patch the virtual storage space Application reading means for outputting the virtual address on the virtual storage space of the application file, the virtual address on the virtual storage space of the individual patch, and the name of the user as information,
A TLB replacement page table that holds the information output from the application reading means in a table format;
Application task switching means for detecting task switching to the user as task switching in the application,
When switching of the task to the user is detected by the application task switching means, if the detected user name is registered on the TLB replacement page table, it is registered along with the user name. A TLB (Translation-Lookaside buffer) content is rewritten based on a virtual address of the individual patch in the virtual storage space and a virtual address of the application file in the virtual memory. Management device. When task switching to the user by the application task switching means is detected, the virtual address in association with the address of the real memory Ru Tei registered in the TLB of the application file, the virtual of the individual patches individual application patch management apparatus according to claim 8, wherein the can exchange written in the virtual address on the memory space. The application reading means includes
When the relative address from the top of the application file of the application file before being read matches the relative address from the top of the individual patch before being read, the individual patch is registered in the application file. the placing individual patches in the virtual memory space, the name of the user, the virtual address on the virtual memory of the application file, and the individual patches with judges, placing the application file on the virtual memory and 10. The individual application patch management apparatus according to claim 8, wherein the virtual address on the virtual storage space is written in the TLB replacement table. The individual application patch management device further includes:
Individual patch application valid / invalid designation means for designating validity / invalidity of application of the individual patch to the OS by the specific application based on an input operation from a user;
6. The individual application patch management apparatus according to claim 1, further comprising a masking unit for masking an entry in the TLB replacement page table based on a designation by the individual patch application valid / invalid designation unit. . The individual application patch management device further includes:
Individual patch application level designation means for designating the application level of the individual patch for the OS for each specific application based on an input operation from a user;
6. The individual application patch management apparatus according to claim 1, further comprising a mask unit that masks an entry in the TLB replacement page table based on a designation in the individual patch application level designation unit.   When task switching to a specific application occurs as task switching in the OS, it points to a virtual address in the virtual storage space of an individual patch that the specific application requests to apply to the OS when there is a memory access As described above, an individual application patch management method characterized by rewriting the contents of a TLB (Translation-Lookaside buffer).   By rewriting the virtual address of the kernel file in which the individual patch is registered in the TLB to the virtual address of the individual patch, the virtual address of the individual patch is changed when memory access is performed using the virtual address of the kernel file. The individual application patch management method according to claim 13, wherein the content of the TLB is rewritten to point. Together to arrange the kernel file into virtual memory read virtual memory space, the if the particular application to the kernel file if it is a separate patch registration requesting application to OS, the said individual patch virtual storage space A kernel reading step for outputting the virtual address on the virtual memory of the kernel file, the virtual address on the virtual storage space of the individual patch, and the name of the specific application as information,
An information writing step of writing the information output by the kernel reading step into a TLB replacement page table in a table format;
An OS task switching step of detecting task switching to the specific application as task switching in the OS,
When switching of a task to the specific application is detected by the OS task switching step, if the detected name of the specific application is registered on the TLB replacement page table, the name of the specific application is set. The individual application patch management, wherein the contents of the TLB are rewritten based on the virtual address of the individual patch in the virtual storage space registered together with the virtual address of the kernel file in the virtual memory. Method. When the switching of the task to a particular application by the OS task switching step is detected, the virtual address registered in the TLB and associated real memory on the address Ru Tei of the kernel file of the individual patches individual application patch management method according to claim 15, wherein the can exchange written in the virtual address on the virtual memory space. In the kernel loading process,
The individual patch is registered in the kernel file when the relative address from the beginning of the kernel file of the kernel file before being read matches the relative address from the beginning of the individual patch of the individual patch before being read. determining that said placing the individual patches in the virtual memory space with the kernel file is placed on the virtual memory, the name of a specific application, the virtual address of the virtual memory of the kernel file, and the individual The individual application patch management method according to claim 15 or 16, wherein a virtual address of the patch in the virtual storage space is written in the TLB replacement table.   When a user switch occurs as a task switch in an application, the TLB (points to a virtual address on the virtual storage space of the individual patch that the user requests to apply to the application when there is a memory access. Individual application patch management method characterized by rewriting the contents of Translation-Lookaside buffer).   By rewriting the virtual address of the application file in which the individual patch is registered in the TLB to the virtual address of the individual patch, the virtual address of the individual patch is changed when memory access is performed at the virtual address of the application file. 19. The individual application patch management method according to claim 18, wherein the content of the TLB is rewritten to point. Together to arrange the application file to the virtual memory of the read virtual storage space, if it is separate patch registration user for the application file requests application to the application, the individual patch the virtual storage space An application reading step of outputting the virtual address on the virtual memory of the application file, the virtual address on the virtual storage space of the individual patch, and the name of the user as information;
An information writing step of writing the information output by the application reading step into a TLB replacement page table in a table format;
An application task switching step of detecting task switching to the user as task switching in the application;
When switching of a task to the user is detected by the application task switching step, if the detected user name is registered on the TLB replacement page table, it is registered along with the user name. The content of the TLB (Translation-Lookaside buffer) is rewritten based on the virtual address of the individual patch in the virtual storage space and the virtual address of the application file in the virtual memory. Patch management method. When task switching to the user by the application task switching means is detected, the virtual address registered in the TLB and associated real memory on the address Ru Tei of the application file, the said individual patches individual application patch management method according to claim 20, wherein the are re-out write to the virtual address of the virtual storage space. In the application loading process,
When the relative address from the top of the application file of the application file before being read matches the relative address from the top of the individual patch before being read, the individual patch is registered in the application file. the placing individual patches in the virtual memory space, the name of the user, the virtual address on the virtual memory of the application file, and the individual patches with judges, placing the application file on the virtual memory and The individual application patch management method according to claim 20 or 21, wherein the virtual address on the virtual storage space is written to the TLB replacement table. The individual application patch management method further includes:
An individual patch application valid / invalid designation step of designating validity / invalidity of application of the individual patch to the OS by the specific application based on an input operation from a user;
18. The individual application patch management method according to claim 13, further comprising a masking step of masking an entry in the TLB replacement page table based on designation in the individual patch application valid / invalid designation step. . The individual application patch management method further includes:
An individual patch application level designation step for designating an application level of the individual patch for the OS for each specific application based on an input operation from a user;
18. The individual application patch management method according to claim 13, further comprising a masking step of masking an entry in the TLB replacement page table based on designation in the individual patch application level designation step.

Images