TW201216165A - System management interrup mechanism - Google Patents

System management interrup mechanism Download PDF

Info

Publication number
TW201216165A
TW201216165A TW99134924A TW99134924A TW201216165A TW 201216165 A TW201216165 A TW 201216165A TW 99134924 A TW99134924 A TW 99134924A TW 99134924 A TW99134924 A TW 99134924A TW 201216165 A TW201216165 A TW 201216165A
Authority
TW
Taiwan
Prior art keywords
system management
program
application
fragment
transaction program
Prior art date
Application number
TW99134924A
Other languages
Chinese (zh)
Inventor
Ying-Chih Lu
Yu-Hui Wang
Original Assignee
Inventec Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Inventec Corp filed Critical Inventec Corp
Priority to TW99134924A priority Critical patent/TW201216165A/en
Publication of TW201216165A publication Critical patent/TW201216165A/en

Links

Abstract

A system management interrupt (SMI) mechanism is provided for an operating system executing an application, wherein the application comprises at least one atomic program segment (The attributes of the atomic program segment are: It cannot be interrupted while its execution. And it can access all the system resources). The SMI mechanism includes triggering an SMI to enter a system management mode (SMM) while the operating system executes the application at the atomic program segment. Under the SMM, a SMI handler is executed to copy the atomic program segment to the SMM RAM. The SMM is terminated while the SMI handler finishes the execution of the copied program segment. The operating system is restored to continue executing the application.

Description

201216165 ιυυ^/.iW 349l〇twf.doc/t 六、發明說明: 【發明所屬之技術領域】 本發明是有關於一種系統管理中斷機制,且特別是有 關於了種將程式片段複製至系統管理模式隨機存取記憶體 内,並在系統管理中斷環境下執行此程式片段的機制。 【先前技術】 • 於多重處理系統中,並無法保證一個需要單一性的應 用程式片段可以不被其他程式或執行緒(thread)所中斷,更 無法保證此程式片段是否可以存取由作業系統管理與限制 的系統的任何資源,例如輸入輸出(1/〇)、記憶體對映輪入 輸出(MMIO)、記憶體或周邊控制器介面標準組態空間 (PCI/PCIE Configuration Spaee)、晶 >{組某些基於安全考 量受保護之暫存器。 舉例而言,當一個名為記憶體注入錯誤(mem〇ry injection error)的應用程式需要存取記憶體的任何位址 • 時,但某些記憶區塊已經受到作業系統保護而為作業系統 所擁有,而某些記憶區塊則為其他程式或執行緒所擁有, 因此此程式不一定有權限可存取上述的記憶體的位址。再 者,晶片組上之與記憶體控制器有關之某些暫存器只能於 系統管理模式(System Management Mode,SMM)下被存 取,而此程式又必需要能存取這些暫存器方能正常工作, 但在作業糸統下其卻無法存取此些暫存器,故其無法正常 工作。此外,此程式也不允許記憶體的讀取與寫入操作被 3 201216165201216165 ιυυ^/.iW 349l〇twf.doc/t VI. Description of the Invention: [Technical Field] The present invention relates to a system management interrupt mechanism, and in particular to copying program fragments to system management A mechanism for mode random access memory and execution of this program fragment in a system management interrupt environment. [Prior Art] • In a multi-processing system, there is no guarantee that an application fragment that requires singularity can be interrupted by other programs or threads, and there is no guarantee that the program fragment can be accessed by the operating system. Any resources of the system with restrictions, such as input and output (1/〇), memory mapping wheel input and output (MMIO), memory or peripheral controller interface standard configuration space (PCI/PCIE Configuration Spaee), crystal > {Groups of certain protected registers based on security considerations. For example, when an application called memory injection error needs to access any address of the memory, some memory blocks are already protected by the operating system and are used by the operating system. Own, and some memory blocks are owned by other programs or threads, so the program does not have permission to access the address of the above memory. Furthermore, some of the registers associated with the memory controller on the chipset can only be accessed in the System Management Mode (SMM), which must be accessible to the program. It works fine, but it can't access these registers under the operating system, so it can't work normally. In addition, this program also does not allow memory read and write operations to be 3 201216165

iW^/.rw 3491〇twf.docA 行。然而,在是此程式必須在不被中斷下進 斷,偏若發生帽執行,、戰行式不被中 【發明内容】 斯環系統管理中斯機制,可在系統管理中 割交易程式片段(Atamiep 中’本發明的不可分 式之執行不可射斷(也就之f為:此程 =airrtOTUpt ’SMI)之嶋概設計上正具有 發明ίΓ種系辭理情鋪,翻在以一作宰 程f段’此系統管理中斷機 ==ΪΠ可分割交易程式片段時,觸發二 =統:理中斷以進入―系純管理模式。於該系統管 程式片將該不可分割交; 統管理中斷處理程式執行該不;:。, 系統管理中斷處理程式執行完畢該;可分割; 時,跳出該系統管理模式。返回該作業系統以繼續Si 201216165 1 whj /. iW 3491〇twf.doc/t 應用程式。 在本發明之一實施例中’上述之系統管理中斷機制, 其中以該作業系統執行該應用程式至該不可分割交易程式 片段時’還包括將該不可分割交易程式片段的一基底位址 與一尺寸寫入一記憶體中的一擴充基本輸入輸出系統資料 區0iW^/.rw 3491〇twf.docA line. However, in this program, the program must be interrupted without interruption, if the cap execution occurs, and the battle mode is not used. [Inventive content] The Sihuan system management mechanism can cut the transaction program fragment in the system management ( Atamiep's inseparable execution of the invention can not be broken (that is, f is: this process = airrtOTUpt 'SMI) is designed to have an invented Γ Γ 辞 辞 , , , , , , , , 'This system management interrupt machine == ΪΠ can split the transaction program fragment, trigger two = system: the interrupt to enter the "system pure management mode." The system management program will be inseparable; the system management interrupt handler executes the No;:, the system management interrupt handler is executed; can be split; when the system management mode is exited. Return to the operating system to continue Si 201216165 1 whj /. iW 3491〇twf.doc/t application. In one embodiment of the invention, the system management interrupt mechanism described above, wherein when the operating system executes the application to the fragment of the indivisible transaction program, the method further includes the fragment of the inseparable transaction program. An expansion base address and a size of a memory write of the BIOS Data Area 0

在本發明之一實施例中’上述之系統管理中斷機制, 其中將該不可分割交易程式片段複製至該系統管理模式隨 機存取記憶體中的步驟包括:將該擴充基本輸入輸出系統 資料區中所寫入的該不可分割交易程式片段的該基底位址 與該尺寸所指到之不可分割交易程式片段複製到該系統管 理模式隨機存取記憶體中。 在本發明之一實施例中’上述之系統管理中斷機制, 其中該系統管理中斷包括一軟體系統管理中斷。 在本發明之一實施例中,上述之系統管理中斷機制, 其中跳出該系統管理模式之前,還包括更新該不可分割交 易程式片段的一程式標頭中的一執行結果狀態。 在本發明之一實施例中’上述之系統管理中斷機制, 其中返回該作業系統以繼續執行該應用程式的步驟還包括 該應用程式核對該不可分割交易程式片段的該程式標頭中 的該執行結果狀態。 、 其在本發明之一實施例中,上述之系統管理中斷機制, 寫中桃出該系統管理模式之前,還包括將一程式執行結果 •、’、入該不可分割交易程式片段的一程式標頭中的一結果攔 5 201216165 100437.TW 34910twf.d〇c/t 位 在本發化-實關中,上述之系辭理 /、中該程式執行結果包括—輸人參數與 在本發明之一實施例中,上營^二 式一括藉令 立中;實施例中,上述之系統管理中斷機制, 二中,不可》割交易程式片段包括—不能被其他程序中斷 的程式片段且/歧-需存取所有系統資源的程式片段。 基於上述,本發明於作業系統執行應用程式過程中, =應用程式巾的不可分败易程式片段複製至系統管理模 ^隨機存取記顏内,並在线f理情環境下,以系統 官理中斷處理程式執行此*可分败g程式片段 ,因此無 ,以作業系統來達成應用程式的單一性而同時可以存取 ^統的所有資源。所以在作業系統下的所有應用程式面臨 單一性問題或是需要達成存取系統所有資源的目的時,皆 可以應用本發明的系統管理中斷機制予以解決。 為讓本發明之上述特徵和優點能更明顯易懂,下文特 舉實施例,並配合所附圖式作詳細說明如下。 【實施方式】 圖1是依照本發明之一實施例的一種系統管理中斷機 制流程簡圖。圖2是依照本發明一實施例的應用系統管理 中斷機制的一系統的示意圖。請參照圖1與圖2 ’於步驟 6 ⑧ 201216165In an embodiment of the present invention, the system management interrupt mechanism described above, wherein the step of copying the non-separable transaction program segment into the system management mode random access memory comprises: inputting the extended basic input and output into a system data area The base address of the indivisible transaction program segment written and the indivisible transaction program segment indicated by the size are copied into the system management mode random access memory. In an embodiment of the invention, the system management interrupt mechanism described above, wherein the system management interrupt comprises a software system management interrupt. In an embodiment of the invention, the system management interrupt mechanism, wherein before jumping out of the system management mode, further comprises updating an execution result state in a program header of the non-divisionable transaction program segment. In an embodiment of the invention, the system management interrupt mechanism described above, wherein the step of returning the operating system to continue executing the application further comprises the application checking the execution in the program header of the non-dividable transaction program segment Result status. In an embodiment of the present invention, the system management interrupt mechanism described above, before writing the system management mode, includes executing a program execution result, and selecting a program identifier of the inseparable transaction program segment. The result in the head is 5 201216165 100437.TW 34910twf.d〇c/t in the localization-reality, the above-mentioned system lexicon/, the program execution result includes-input parameter and implementation in one of the inventions In the example, the upper camp ^2 type includes the borrowing order; in the embodiment, the above system management interrupt mechanism, the second, the non-cutting program fragment includes - the program fragment that cannot be interrupted by other programs and / Take a program fragment of all system resources. Based on the above, in the process of executing the application program in the operating system, the non-distributable program fragment of the application towel is copied into the system management module, and the system is interrupted by the system officially. The processing program executes this * to distinguish the g-segment fragments, so no, the operating system can achieve the singularity of the application while accessing all the resources of the system. Therefore, when all applications under the operating system face a single problem or need to achieve access to all resources of the system, the system management interrupt mechanism of the present invention can be applied to solve the problem. The above described features and advantages of the present invention will become more apparent from the description of the appended claims. [Embodiment] FIG. 1 is a schematic diagram of a system management interrupt mechanism flow according to an embodiment of the present invention. 2 is a schematic diagram of a system for managing a system management interrupt mechanism in accordance with an embodiment of the present invention. Please refer to Figure 1 and Figure 2' in step 6 8 201216165

1W4J/.1'W 3491〇twf.docA sioi中,以一作業系統執行一應用程式2〇2,其中此應用 程^ 202包含至少一不可分割交易程式片段。其中上述不 可刀割父易程式片段例如是不能被其他程序中斷的一程式 片段且/或是需要存取所有系統資源的—程式片段。換句話 說,上述所謂的不能被其他程序中斷的一程式片段,例如 ^具有單一性的程式片段。此外,此不可分割交易程式片 段包含程式標頭(header),而此程式標頭還至少包括程式片 段的進入點(entry)、輸入的參數、輸出的參數以及執行結 果狀態。 之後,於步驟S105中,判斷作業系統執行上述應用 程式202是否執行到此應用程式202的不可分割交易程式 片段。當確認作業系統的確執行到此應用程式的不可分割 交易程式片段時,則觸發一系統管理中斷(System Management lnterrupt,8_以進入一系統管理模式(咖㈣ Management Mode ’ SMM)(步驟Sill),也就是系統管理中 斷被觸發至中央處理單元(Central Processing Unit, # CPU)204 ’由中央處理單元204執行存在於系統管理模式1W4J/.1'W 3491〇twf.docA In sioi, an application program 2〇2 is executed by an operating system, wherein the application 202 includes at least one indivisible transaction program fragment. The above-mentioned non-cutting program is, for example, a program fragment that cannot be interrupted by other programs and/or a program fragment that needs to access all system resources. In other words, the above-mentioned so-called program fragment that cannot be interrupted by other programs, such as a program fragment having a unity. In addition, the indivisible transaction fragment includes a program header, and the program header further includes at least an entry of the program segment, input parameters, output parameters, and execution result status. Thereafter, in step S105, it is determined whether the operating system executes the application program 202 to execute an indivisible transaction program segment to the application 202. When it is confirmed that the operating system does execute the fragment of the indivisible transaction program of the application, a system management interrupt (System Management lnterrupt, 8_ is entered to enter a system management mode (S) (Step Sill), That is, the system management interrupt is triggered to the central processing unit (Central Processing Unit, #CPU) 204' is executed by the central processing unit 204 and exists in the system management mode.

隨機存取記憶體(SMM Random Aceess MemQry,SMM RAM)206内的系統管理中斷處理程式(SMI handler,以下 簡稱SMI處理程式)2〇8。反之,則繼續以作業系統執行此 應用程式202(步驟S101)。 具體而e,系統管理中斷為優先權(pri〇rity)最高之中 斷,其包括軟體系統管理中斷、硬體系統管理中斷及週期 性系統管理中斷。軟體SMI是由軟體對輸入輪出埠做寫入 7 201216165 ιυυ^/.i'W 3491 Otwf.doc/t 而觸發的SMI。硬體系統管理中斷是由硬體對其所债 之某-個事件_發之SMI。週祕系統管財斷則由晶 片每隔-段固定時間對中央處理單元所觸發的系統管理曰中曰 斷。於本㈣-實關巾’上述㈣統管理情包括軟體 SMI ° 另外,以作業系統執行應用程式2〇2至不可分割交易 程式片段時,還包括料可分财綠Μ段的—基底位 址與-尺寸寫入-記憶體2U)中的一擴充基本輸入輸出系 統資料區(Extended BIOS Data Area,EBDA,以下均簡稱 擴充BIOS資料區)212。例如,將不可分割交易程式片段 的基底位址(base address)x與尺寸y分別寫入擴充BI〇s資 料區212中的基底位址攔位212a與尺寸攔位212b中。 接著,於步驟S115中,於此系統管理模式下,以中 央處理單元204執行SMI處理程式208,以將不可分割交 易程式片段複製至系統管理模式隨機存取記憶體2〇6中。 更明確的說,將不可分割交易程式片段複製至系統管理模 式隨機存取記憶體206中的步驟包括將該擴充BI〇s資料 區212中所寫入的不可分割交易程式片段的基底位址乂與 尺寸y所指到之不可分割交易程式片段複製到系統管理模 式隨機存取記憶體206中。也就是SMI處理程式208將不 可分割乂易程式片段複製至系統管理模式隨機存取記憶體 206中做為SMI處理程式208的一部分,並且跳至此程式 標頭的進入點(entry)攔位所指到的程式進入點及依標頭之 輸入參數執行之。 201216165 100437.TW 3491 Otwf.doc/t 續之,於步驟S211中’以SMI處理程式2〇8執行不 可为割交易私式片段。當SMI處理程式208執行完畢不可 分割交易程式片段時,則跳出系統管理模式(步驟咖)。 也就是在SMI處理程式施執行完畢不可分割交易程式片 段時,中央處理單元204會執行一回復(Resume,rsm)指 令’使得中央處理單元2〇4離開系統管理模式,並且回到 糸統管理中斷發生時作録統被中斷的程式點。 於-實施例中,跳出系統管理模式之前,軌括更新 不可分割父易程式片段的—程式標頭中的—狀態(_s), 利如執2結果狀態。此外,於另—實補巾跳出系統管理 j式之刖,還包括將一程式執行結果寫入該不可分割交易 程式片段的-程式標頭巾的—結果獅。上述程式執行結 括一輸人參數與—輸出參數。再者,返回作業系統以 繼^執?應用程式2〇2的步驟還包括應用程式2〇2核對不 ^分割交綠式諸雜式標頭巾的執行結果㈣與結果 糊位。 繼之,於步驟灿中,返回作業系統以繼續執行應 用程式202 〇 於又一實施例中,為確保應用程式2〇2與SMI處理程 ^ 208之間的正確互動’可在應用程式202與SMI處理程 〔208之間建立一通信協定(pr〇t〇c〇1)。也就是遞處理程 〔208必須提供64位元大真實模式(64bit Big-Real Mode) 二需要不可分败易程式片段,而需要不可分#]交易程式 片段本相會認定其不可分鼓易式片段是在64位元大 201216165 iU〇43/.i'W 3491 Otwf.doc/t 真實模式執行,以便其可以存取到大於等於四十億位组(4 Giga Byte)空間,例如記憶體、記憶體對映輸1輸出 (memory-mapped I/O,MMIO)空間或周邊控制器介面標準 組態空間(PCI Express configuration space)。此外,此不可 分割交易程式片段必須能獨立編譯,並假設其執行環境是 在64位元大真實模式或32位元大真實模式。 綜上所述’因為系統管理中斷機制能讓系統只執行一 個SMI處理程式,因此可以達到程式不被中斷執行的單一 )·生所以,本發明於作業系統執行應用程式過程中將應 $式中的不可分割交易程式片段複製至系統管理模式隨 ,存取記憶體内’並在系統管理中斷環境下,以系統管理 中斷處理程式執行此科分割交易程式片段。如此 無^作業系統控管來達成應用程式的單一性而同時可 的所有資源’例如輸入輸出(1/〇)、讀1〇、記 控制器介面標準組態空間。所以在作業系統下 有用程式面臨單一性問題或是需要達成存取系統所 予以解'決目的時’皆可以應用本發明的系統管理中斷機制 ,然本發明已以實施例揭露如上,然其並非用以限定 本所屬技術領域中具有通常知識者,在不脫離 發明之俾2和1巳圍内’當可作些許之更動與潤飾,故本 之保遵範圍當視後附之申請專利範圍所界定者為準。 【圖式簡單說明】 201216165 100437.TW 34910twf.doc/t 圖1是依照本發明之一實施例的一種系統管理中斷機 制流程簡圖。 圖2是依照本發明一實施例的應用系統管理中斷機制 的一系統的示意圖。 【主要元件符號說明】 S101〜S311 :系統管理中斷機制流程步驟 202 :應用程式 204 :中央處理單元 206:系統管理模式隨機存取記憶體 208:系統管理中斷處理程式 210 :記憶體 212 :擴充BIOS資料區 212a :基底位址欄位 212b :尺寸攔位The system management interrupt processing program (SMI handler, hereinafter referred to as SMI processing program) in the random access memory (SMM Random Aceess MemQry, SMM RAM) 206 is 2〇8. Otherwise, the application 202 is continued to be executed by the operating system (step S101). Specifically, the system management interrupt is the highest priority (priority), which includes software system management interrupts, hardware system management interrupts, and periodic system management interrupts. The software SMI is the SMI that is triggered by the software to write to the input wheel 7 201216165 ιυυ^/.i'W 3491 Otwf.doc/t. The hardware system management interruption is the SMI of the event that the hardware is responsible for. The system of financial management of the Zhou Mi system is interrupted by the system management that is triggered by the central processing unit at regular intervals of the wafer. In this (four)-the real customs towel, the above (four) system management includes software SMI ° In addition, when the application system executes the application program 2〇2 to the indivisible transaction program segment, it also includes the base address of the material that can be divided into green segments. An extended BIOS data area (EBDA, hereinafter referred to as an extended BIOS data area) 212 is included in the AND-size write-memory 2U. For example, the base address x and size y of the indivisible transaction program fragment are written into the base address block 212a and the size block 212b in the extended BI〇s data area 212, respectively. Next, in step S115, in the system management mode, the central processing unit 204 executes the SMI processing program 208 to copy the undivided transaction program fragments into the system management mode random access memory 2〇6. More specifically, the step of copying the inseparable transaction program fragment into the system management mode random access memory 206 includes the base address of the indivisible transaction program fragment written in the extended BI〇s data area 212. The indivisible transaction program segment indicated by the size y is copied to the system management mode random access memory 206. That is, the SMI handler 208 copies the indivisible program fragments into the system management mode random access memory 206 as part of the SMI handler 208 and jumps to the entry barrier of the program header. The program entry point to the point and the input parameters of the header are executed. 201216165 100437.TW 3491 Otwf.doc/t Subsequently, in step S211, the SMI processing program 2〇8 is executed to execute the private segment. When the SMI handler 208 executes the inseparable transaction program segment, it exits the system management mode (step coffee). That is, when the SMI processing program executes the execution of the inseparable transaction program segment, the central processing unit 204 executes a reply (resm, rsm) instruction to cause the central processing unit 2〇4 to leave the system management mode and return to the system management interrupt. The program point where the recording system was interrupted when it occurred. In the embodiment, before jumping out of the system management mode, the track updates the state (_s) in the program header of the undividable parent program segment, such as the result state of the execution 2 result. In addition, after the other-real patch jumps out of the system management mode, it also includes writing a program execution result to the program-headband of the indivisible transaction program fragment--the result lion. The above program execution includes an input parameter and an output parameter. Furthermore, returning to the operating system to continue? The application 2〇2 step further includes the application 2〇2 checking the execution result (4) of the non-segmented green type miscellaneous headband and the result paste. Then, in step chan, returning to the operating system to continue executing the application 202. In yet another embodiment, to ensure proper interaction between the application 2 〇 2 and the SMI processing 208, the application 202 can be A communication protocol (pr〇t〇c〇1) is established between the SMI processes [208]. That is, the processing process [208 must provide 64-bit big-real mode (64bit Big-Real Mode) two need to be inseparable from the easy-to-decode fragment, but need to be inseparable #] the transaction program fragment will find its inseparable drum style is in 64-bit large 201216165 iU〇43/.i'W 3491 Otwf.doc/t Real mode execution so that it can access more than or equal to 4 Giga Byte space, such as memory, memory pairs The memory-mapped I/O (MMIO) space or the peripheral controller interface (PCI Express configuration space). In addition, this non-divisible trading program fragment must be compiled independently, and its execution environment is assumed to be in 64-bit large real mode or 32-bit large real mode. In summary, because the system management interrupt mechanism allows the system to execute only one SMI processing program, it can achieve a single program that is not interrupted. Therefore, the present invention will be executed in the execution system of the operating system. The inseparable transaction program fragment is copied to the system management mode, and the memory is interrupted. In the system management interrupt environment, the system management interrupt processing program executes the segmentation transaction program fragment. In this way, there is no operating system control to achieve the singularity of the application and all the resources at the same time, such as input and output (1/〇), read 1〇, and the controller interface standard configuration space. Therefore, the system management interrupt mechanism of the present invention can be applied to the utility program in the operating system, or the system management interrupt mechanism of the present invention can be applied to the solution. However, the present invention has been disclosed in the above embodiments, but it is not In order to limit the general knowledge in the technical field, it is possible to make some changes and refinements without departing from the scope of the invention, and therefore the scope of the patent application is attached to the scope of the patent application. The definition is subject to change. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a schematic diagram of a system management interrupt mechanism flow in accordance with an embodiment of the present invention. 2 is a schematic diagram of a system for an application system management interrupt mechanism in accordance with an embodiment of the present invention. [Main Component Symbol Description] S101~S311: System Management Interrupt Mechanism Flow Step 202: Application 204: Central Processing Unit 206: System Management Mode Random Access Memory 208: System Management Interrupt Processing Program 210: Memory 212: Expansion BIOS Data area 212a: base address field 212b: size block

Claims (1)

201216165 100437.TW 34910twf.doc/t 七、申請專利範園: 1 一種系統管理中斷機制,適用在以一作業系統執行 -應用料,其中該應用程式包含至少—科分割交易程 式片段,此系統管理中斷機制包括: 以該作業系統執行該應用程式至該不可分割父易程 式片段時,觸發一系統管理中斷以進入一系統管理模式, 於該系統管理模式下,執行一系統管理中斷處理程 式,以將該不可分割交易程式片段複製至一系統管理模式 隨機存取記憶體中; 該系統管理中斷處理程式執行該不可分割交易程式 片段; 當該系統管理中斷處理程式執行完畢該不可分割交 易程式片段時,跳出該系統管理模式;以及 返回該作業系統以繼續執行該應用程式。 2.如申請專利範圍第1項所述之系統管理中斷機 制’其中以該作業系統執行該應用程式至該不可分割交易 程式片段時’還包括將該不可分割交易程式片段的一基底 位址與一尺寸寫入一記憶體中的一擴充基本輸入輸出系統 資料區。 .甲知專利範圍第2項所述之系統管理中斷機 # ί t 可分割交易程式片段複製至該系統管理模 k咨·_中的步驟包括:將該擴充基本輸入輸出 所寫t入的該不可分割交易程式片段的該基底 、〜所^到之該不可分割交易程式片段複製到錢 201216165 100437.TW 34910twf.doc/t 系統管理模式隨機存取記憶體中。 4. 如申請專利範圍第1項所述之系統管理中斷機 制,其中該系統管理中斷包括一軟體系統管理中斷。 5. 如申凊專利範圍第1項所述之系統管理中斷機 制,其中跳出該系統管理模式之前,還包括更新該不可分 割交易程式片段的一程式標頭中的一執行結果狀緣。 :·如申請專利範圍第5項所述之系統管理中斷機 t拓i中返回該作業系統以繼續執行該應用程式的步驟還 頭=:=不可分割交易程式片段的該程式標 制,… 該不可分割交易程式片段的 制 .如申凊專利範圍第7項 該程式執行結果包括一輪統一= 如申請專利難第 I輸出參數。 t其t«該系辭理模式的項H之系辭理情相 才曰7以跳出該系統管理模式。步驟包括藉由執行一回復 10.如申請專利範圍 該不可相交易m之祕管理情機 中斷的程式片段且/或是乃奴包括-不能被其他程序 段。 冑存取所有系統資源的程式片 13201216165 100437.TW 34910twf.doc/t VII. Application for Patent Park: 1 A system management interrupt mechanism, which is applied to an operating system-application, where the application contains at least a section of the transaction program fragment, this system management The interrupt mechanism includes: when the operating system executes the application to the undivided parent program segment, triggering a system management interrupt to enter a system management mode, and executing a system management interrupt processing program in the system management mode, Copying the inseparable transaction program fragment into a system management mode random access memory; the system management interrupt processing program executes the inseparable transaction program fragment; when the system management interrupt processing program executes the inseparable transaction program fragment Jumping out of the system management mode; and returning to the operating system to continue executing the application. 2. The system management interruption mechanism of claim 1, wherein the execution of the application to the non-separable transaction program segment further includes a base address of the fragment of the inseparable transaction program A size is written into an extended basic input/output system data area in a memory. The system management interrupter described in item 2 of the patent scope is the step of copying the detachable transaction program fragment into the system management module, and includes: writing the expanded basic input and output into the The base of the inseparable transaction program fragment, the fragment of the indivisible transaction program is copied to the money 201216165 100437.TW 34910twf.doc/t system management mode random access memory. 4. The system management interrupt mechanism of claim 1, wherein the system management interrupt comprises a software system management interrupt. 5. The system management interrupt mechanism of claim 1, wherein before exiting the system management mode, updating an execution result of a program header of the non-sediable transaction program fragment. :· As in the system management interrupter described in item 5 of the patent application scope, the step of returning the operating system to continue the execution of the application is still === the program of the inseparable transaction program fragment, ... The system of the inseparable transaction program fragment. For example, the execution result of the program in the scope of the patent includes a round of uniform = if the patent application is difficult to output the first parameter. t its t« the lexical pattern of the item H of the rhetoric of the system to jump out of the system management mode. The steps include by performing a reply. 10. If the scope of the patent is applied, the secret management of the non-transactional m is interrupted and/or the slave is included - cannot be used by other programs.程式Access to all system resources 13
TW99134924A 2010-10-13 2010-10-13 System management interrup mechanism TW201216165A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
TW99134924A TW201216165A (en) 2010-10-13 2010-10-13 System management interrup mechanism

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
TW99134924A TW201216165A (en) 2010-10-13 2010-10-13 System management interrup mechanism

Publications (1)

Publication Number Publication Date
TW201216165A true TW201216165A (en) 2012-04-16

Family

ID=46787114

Family Applications (1)

Application Number Title Priority Date Filing Date
TW99134924A TW201216165A (en) 2010-10-13 2010-10-13 System management interrup mechanism

Country Status (1)

Country Link
TW (1) TW201216165A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9411667B2 (en) 2012-06-06 2016-08-09 Intel Corporation Recovery after input/ouput error-containment events

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9411667B2 (en) 2012-06-06 2016-08-09 Intel Corporation Recovery after input/ouput error-containment events

Similar Documents

Publication Publication Date Title
JP3914541B2 (en) Block processing constraints based on address
US8719543B2 (en) Systems and methods implementing non-shared page tables for sharing memory resources managed by a main operating system with accelerator devices
JP4688862B2 (en) Providing support for single step functionality of virtual machines in virtual machine environments
US8185783B2 (en) Split user-mode/kernel-mode device driver architecture
US8434098B2 (en) Synchronizing split user-mode/kernel-mode device driver architecture
JP4764360B2 (en) Techniques for using memory attributes
US9830210B2 (en) CPU-to-GPU and GPU-to-GPU atomics
US20090210888A1 (en) Software isolated device driver architecture
TWI667588B (en) Computing device, method and machine readable storage media for detecting unauthorized memory accesses
WO2016137579A1 (en) Return oriented programming attack detection via memory monitoring
KR20170031697A (en) On-demand shareability conversion in a heterogeneous shared virtual memory
KR20110044884A (en) Virtualization Advanced Synchronization Capability
KR20120061938A (en) Providing state storage in a processor for system management mode
US10229077B2 (en) Method for data transfer between real-time tasks using a DMA memory controller
JP2018523201A (en) Firmware related event notification
JP6367490B2 (en) Memory access protection with processor transactional memory support
CN111414626A (en) TEE extension-based real-time guaranteeing method and system
CN101630276A (en) High-efficiency memory pool access method
JP2015514252A (en) Report malicious activity on the operating system
WO2012163017A1 (en) Method for processing access exception of distributed virtual machine and virtual machine monitor
JP5392263B2 (en) Information processing apparatus and memory protection method thereof
JP5999216B2 (en) Data processing device
WO2013125012A1 (en) Computing device, access management method, and access management program
TW201216165A (en) System management interrup mechanism
US9384015B2 (en) Techniques for dynamically redirecting device driver operations to user space