7.3. Operating System Interface

LSB-conforming applications shall use the following aspects of the Operating System Interfaces as defined in Chapter 3 of the System V ABI, IA32 Supplement.

7.3.1. Virtual Address Space

LSB-conforming implementations shall support the virtual address space described in Chapter 3 of the System V ABI, IA32 Supplement.

7.3.1.1. Page Size

LSB-conforming applications should call sysconf() to determine the current page size. See also Chapter 3 of the System V ABI, IA32 Supplement.

7.3.1.2. Virtual Address Assignments

LSB-conforming systems shall provide the virtual address space configuration as described in Chapter 3 of the System V ABI, IA32 Supplement (Virtual Address Assignments).

7.3.1.3. Managing the Process Stack

LSB-conforming systems shall manage the process stack as specified in Chapter 3 of the System V ABI, IA32 Supplement.

7.3.1.4. Coding Guidlines

LSB-conforming applications should follow the coding guidleines provided in Chapter 3 of the System V ABI, IA32 Supplement.

7.3.2. Processor Execution Mode

LSB-conforming applications shall run in the user-mode ring as described in Chapter 3 of the System V ABI, IA32 Supplement.

7.3.3. Exception Interface

7.3.3.1. Introduction

LSB-conforming system shall provide the exception interface described in Chapter 3 of the System V ABI, IA32 Supplement.

7.3.3.2. Hardware Exception Types

LSB-conforming systems shall map hardware exceptions to signals as described in Chapter 3 of the System V ABI, IA32 Supplement.

7.3.3.3. Software Trap Types

Software generated traps are subject to the limitations described in Chapter 3 of the System V ABI, IA32 Supplement.

7.3.4. Signal Delivery

There are no architecture specific requirements for signal delivery.

7.3.4.1. Signal Handler Interface

There are no architecture specific requirements for the signal handler interface.