Abstract: The present invention relates to a multilayer film comprising a layer (a) and a layer (c), in each case based on at least one propylene copolymer in an amount of at least 15% by weight, at least one propylene polymer in an amount of at least 40% by weight, in each case based on the total weight of the layer (a)/(c), at least one multi-ply inner layer (b) based on at least one homo- and/or copolyamide comprising isophoronediamine units as a polyamide component, adhesion promoter layers (d) and (e), wherein the thickness of the multi-ply layer (b) is at least 40% of the total thickness of the multilayer film, preferably at least 45% or at least 50%.

Abstract: The present invention relates to a multilayer film comprising a layer (a) and a layer (c), in each case based on at least one propylene copolymer in an amount of at least 15% by weight, at least one propylene polymer in an amount of at least 40% by weight, in each case based on the total weight of the layer (a)/(c), at least one multi-ply inner layer (b) based on at least one homo- and/or copolyamide comprising isophoronediamine units as a polyamide component, adhesion promoter layers (d) and (e), wherein the thickness of the multi-ply layer (b) is at least 40% of the total thickness of the multilayer film, preferably at least 45% or at least 50%.

Abstract: Various systems and methods for capability access management are disclosed herein. In one example, a system includes a memory and a processor to send a signed custom capability description (SCCD) received from a first vendor to the memory for storage. The system may send an application received from a second vendor to the memory for storage. The system attempts to match the application to an authorization listing of the SCCD, where the application can be modified to allow access to a previously inaccessible custom capability in response to the application matching the authorization listing of the SCCD.

Abstract: Techniques described herein enable the implementation of a secure driver framework. In one example, a method includes managing an unsecure operating system execution environment comprising a first user mode and a first kernel mode. The method can also include managing a secure execution environment comprising a second user mode and a second kernel mode, and executing a secure driver within the second user mode of the secure execution environment in response to a system call from an unsecure driver in the first kernel mode or the first user mode, wherein the secure driver enables the unsecure driver to communicate with a secure device. Furthermore, the method can include providing one or more system services of the second kernel mode to the secure driver.

Abstract: Various systems and methods for capability access management are disclosed herein. In one example, a system includes a memory and a processor to send a signed custom capability description (SCCD) received from a first vendor to the memory for storage. The system may send an application received from a second vendor to the memory for storage. The system attempts to match the application to an authorization listing of the SCCD, where the application can be modified to allow access to a previously inaccessible custom capability in response to the application matching the authorization listing of the SCCD.

Abstract: Techniques described herein enable the implementation of a secure driver framework. In one example, a method includes managing an unsecure operating system execution environment comprising a first user mode and a first kernel mode. The method can also include managing a secure execution environment comprising a second user mode and a second kernel mode, and executing a secure driver within the second user mode of the secure execution environment in response to a system call from an unsecure driver in the first kernel mode or the first user mode, wherein the secure driver enables the unsecure driver to communicate with a secure device. Furthermore, the method can include providing one or more system services of the second kernel mode to the secure driver.

Abstract: At least one embodiment provides a multilayered foil (100) having a first outer layer (10) and a second outer layer (30), which each comprise homo polypropylene. A central layer (20) is disposed between the first outer layer (10) and the second outer layer (30) and contains more than 25 wt % of homo polyamide and comprises copolyamide. The first outer layer (10) comprises microspheres (50).

Abstract: A device driver includes a kernel mode and a user-mode module. The device driver may access device registers while operating in user-mode to promote system stability while providing a low-latency software response from the system upon interrupts. The device driver may include kernel stubs that are loaded into the operating system, and may be device specific code written. The stubs may be called by a reflector to handle exceptions caught by the stubs. A reset stub may be invoked by the reflector when the user-mode module or host terminates abruptly or detects an interrupt storm. The reset stub may also be invoked if errant direct memory access DMA operations are being performed by a hardware device. The reset stub may ensure that hardware immediately stops unfinished DMA from further transfer, and may be called by the user-mode driver module.

Abstract: A device driver includes a kernel stub and a user-mode module. The device driver may access device registers while operating in user-mode to promote system stability while providing a low-latency software response from the system upon interrupts. Upon receipt of an interrupt, the kernel stub may run an interrupt service routine and write information to shared memory. Control is passed to the user-mode module by a reflector. The user-mode module may then read the information from the shared memory to continue servicing the interrupt.

Abstract: A computer configured to operate in diagnostic mode during which the operating system is suspended. During the diagnostic mode, tests can be performed on the computer system, including hardware, and the tests do not disrupt the operating system and are not disrupted by the operating system. When diagnostic mode is triggered, execution of the operating system is suspended. When the diagnostic tests are completed, the operating system may resume operation and test data may be made available within the operating system environment. Upon resuming, the state of the computer prior to entering diagnostic mode may be restored, preventing any changes made during diagnostic mode from interfering with operation of the operating system or application components.

Abstract: A device driver includes a hypervisor stub and a virtual machine driver module. The device driver may access device registers while operating within a virtual machine to promote system stability while providing a low-latency software response from the system upon interrupts. Upon receipt of an interrupt, the hypervisor stub may run an interrupt service routine and write information to shared memory. Control is passed to the virtual machine driver module by a reflector. The virtual machine driver module may then read the information from the shared memory to continue servicing the interrupt.

Abstract: A device driver includes a kernel mode and a user-mode module. The device driver may access device registers while operating in user-mode to promote system stability while providing a low-latency software response from the system upon interrupts. The device driver may include kernel stubs that are loaded into the operating system, and may be device specific code written. The stubs may be called by a reflector to handle exceptions caught by the stubs. A reset stub may be invoked by the reflector when the user-mode module or host terminates abruptly or detects an interrupt storm. The reset stub may also be invoked if errant DMA operations are being performed by a hardware device. The reset stub may ensure that hardware immediately stops unfinished DMA from further transfer, and may be called by the user-mode driver module.

Abstract: A device driver includes a kernel stub and a user-mode module. The device driver may access device registers while operating in user-mode to promote system stability while providing a low-latency software response from the system upon interrupts. Upon receipt of an interrupt, the kernel stub may run an interrupt service routine and write information to shared memory. Control is passed to the user-mode module by a reflector. The user-mode module may then read the information from the shared memory to continue servicing the interrupt.

Abstract: A computer configured to operate in diagnostic mode during which the operating system is suspended. During the diagnostic mode, tests can be performed on the computer system, including hardware, and the tests do not disrupt the operating system and are not disrupted by the operating system. When diagnostic mode is triggered, execution of the operating system is suspended. When the diagnostic tests are completed, the operating system may resume operation and test data may be made available within the operating system environment. Upon resuming, the state of the computer prior to entering diagnostic mode may be restored, preventing any changes made during diagnostic mode from interfering with operation of the operating system or application components.

Abstract: A piston for an internal combustion engine has a piston head and a piston skirt spaced apart from the piston head by a ring-shaped recess. The piston has at least one pin bore for accommodating a piston pin. A ring-shaped circumferential cooling channel for a coolant is provided in the piston head, which channel is closed off by a cover ring that consists of at least two segments. At least one region of the cover ring projects at least partially into the clear opening of the at least one pin bore, in such a manner that the cover ring simultaneously forms the retaining element for the piston pin.

Abstract: A system, methodology and/or computer architecture that facilitates processing device interrupts (including level-triggered interrupts) in a user-mode process is provided. The kernel interrupt handler can cause a dedicated thread in the process to wake and invoke the driver interrupt service routine. This thread can then return control to the kernel interrupt handler. In addition to processing interrupts in an isolated mode, the context switching technique could be used in any isolated environment to process interrupts via dedicated execution context methods.

Abstract: A piston for an internal combustion engine has a piston head and a piston skirt spaced apart from the piston head by a ring-shaped recess. The piston has at least one pin bore for accommodating a piston pin. A ring-shaped circumferential cooling channel for a coolant is provided in the piston head, which channel is closed off by a cover ring that consists of at least two segments. At least one region of the cover ring projects at least partially into the clear opening of the at least one pin bore, in such a manner that the cover ring simultaneously forms the retaining element for the piston pin.

Abstract: When multiple contacts are detected for a phone number of an incoming call, a notification that multiple contacts matched the phone number is displayed. When the display area for displaying the notification is adequate to display a full list of the contacts that correspond to the phone number of the incoming call, the full list is displayed. When the display area is inadequate to display the full list, a scrollable list of the multiple contacts is displayed. Alternatively, when the display area is inadequate, a multiple contacts message is displayed that notifies a user that multiple stored contacts matched the phone number of the incoming phone call.

Abstract: A system that facilitates the storage of data using a write barrier. The system interfaces to a hardware component that stores data, and includes a write barrier component that dynamically employs instructions compatible with the hardware component to ensure data integrity during storage of the data. The write barrier component is independent of at least an operating system and an application and can operate in a least one of a user mode and a kernel mode. The write barrier component includes at least one of software instructions, routines, and methods, the selection of one or more of which is based on hardware data extracted from the hardware component. A selection component interrogates the hardware component for hardware data to facilitate selection of one or more instructions most suitable for interfacing to the hardware component. A coalescing component combines cache synchronization requests into a single set of instructions, which set is processed to flush a disk cache in one process.

Abstract: A system, methodology and/or computer architecture that facilitates processing device interrupts (including level-triggered interrupts) in a user-mode process is provided. The kernel interrupt handler can cause a dedicated thread in the process to wake and invoke the driver interrupt service routine. This thread can then return control to the kernel interrupt handler. In addition to processing interrupts in an isolated mode, the context switching technique could be used in any isolated environment to process interrupts via dedicated execution context methods.