G06F11/141

Hardware-supported memory temporal copy
09798630 · 2017-10-24 · ·

Providing a snapshot of a physical memory region as of a specified time includes: sending, from a first processor to a second processor, a request to generate a snapshot of the physical memory region as of the specified time; and generating, using the second processor, the snapshot of the physical memory region based at least in part on a known state of the physical memory region and log information about update activity of the physical memory region.

Techniques for logging addresses of high-availability data via a non-blocking channel

A technique for operating a data processing system includes determining whether a cache line that is to be victimized from a cache includes high availability (HA) data that has not been logged. In response determining that the cache line that is to be victimized from the cache includes HA data that has not been logged, an address for the HA data is written to an HA dirty address data structure, e.g., a dirty address table (DAT), in a first memory via a first non-blocking channel. The cache line that is victimized from the cache is written to a second memory via a second non-blocking channel.

Data processing apparatus and data processing method

A data processing apparatus includes a storage unit configured to store plural data processing programs and a corresponding error processing program for when an error occurs with a first data processing program; and a processor configured to record to memory before executing the first data processing program, information of the error processing program that corresponds to the first data processing program; update and record in the memory after the first data processing program ends, information of a second data processing program scheduled to be executed next; and switch to any one among the first data processing program that corresponds to information recorded in the memory and the error processing program, when program processing is started next.

Optical module link negotiation information obtaining method, device, and system
11256635 · 2022-02-22 · ·

An optical module link negotiation information obtaining method, a device, and a system are provided to include: obtain first information of an optical module readable partition; when the partition indicated by the first information is different from a partition that stores link negotiation information in the optical module, and a recorded quantity of optical module link negotiation information obtaining times does not reach a preset threshold, modify the first information of the optical module readable partition into information indicating the partition that stores the link negotiation information to make the partition that stores the link negotiation information as an updated optical module readable partition; and re-obtain second information of the updated optical module readable partition, and when the updated partition indicated by the second information is the same as the partition that stores the link negotiation information in the optical module, obtain optical module link negotiation information.

Apparatus and method for controlling level 0 cache

Disclosed herein is an apparatus and method for controlling level 0 caches, capable of delivering data to a processor without errors and storing error-free data in the caches even when soft errors occur in the processor and caches. The apparatus includes: a level 0 cache #0 connected to the load/store unit of a first processor; a level 0 cache #1 connected to the load/store unit of a second processor; and a fault detection and recovery unit for reading from and writing to tag memory, data memory, and valid bit memory of the level 0 cache #0 and the level 0 cache #1, performing the write-back and flush of the level 0 cache #0 and the level 0 cache #1 based on information stored therein, and instructing the load/store units of the first and second processors to stall a pipeline and to restart an instruction #n.

System and method for fault identification and fault handling in a multiport power sourcing device

System and method for fault identification and fault handling in MPSD are provided. The system includes: a multi-port power sourcing device including multiple ports, a master is configured to: send a slave discovery request to multiple slave ports, receive a slave discovery response from the multiple slave ports; reset the watchdog timer in the multiple ports by sending watchdog refresh instruction periodically; each of the multiple ports experience watchdog timer timeout upon failing to receive the watchdog refresh instruction, generate their corresponding port reset upon watchdog timer timeout, to resolve one or more faults associated with the corresponding port; the multiple ports include a role change staggered timer which is triggered upon the corresponding watchdog timer timeout, and reset upon receiving the watchdog refresh instruction from master; the slave ports for which role change staggered timer times out first, changes the role to start functioning as the new master port.

MRAM smart bit write algorithm with error correction parity bits

Some embodiments relate to a system that includes write circuitry, read circuitry, and comparison circuitry. The write circuitry is configured to attempt to write an expected multi-bit word to a memory location in a memory device. The read circuitry is configured to read an actual multi-bit word from the memory location. The comparison circuitry is configured to compare the actual multi-bit word read from the memory location with the expected multi-bit word which was previously written to the memory location to distinguish between a number of erroneous bits in the actual multi-bit word and a number of correct bits in the actual multi-bit word. The write circuitry is further configured to re-write the number of erroneous bits to the memory location without attempting to re-write the number of correct bits to the memory location.

Techniques to support multiple interconnect protocols for a common set of interconnect connectors

Embodiments may be generally direct to apparatuses, systems, method, and techniques to determine a configuration for a plurality of connectors, the configuration to associate a first interconnect protocol with a first subset of the plurality of connectors and a second interconnect protocol with a second subset of the plurality of connectors, the first interconnect protocol and the second interconnect protocol are different interconnect protocols and each comprising one of a serial link protocol, a coherent link protocol, and an accelerator link protocol, cause processing of data for communication via the first subset of the plurality of connectors in accordance with the first interconnect protocol, and cause processing of data for communication via the second subset of the plurality of connector in accordance with the second interconnect protocol.

Reducing memory overhead associated with memory protected by a fault protection scheme

A memory request initiates access to a memory location in the memory. The memory location is evaluated to determine whether the memory location is located within a first portion of the memory or within a second portion of the memory. In response to determining that the memory location is located within the first portion and that the memory request is a read request, the memory location located within the first portion is accessed. In response to determining that the memory request is a write request and the memory location is located within the first portion, the memory location located within the first portion and a duplicate of the memory location is accessed. When the memory location is located within the second portion, the memory location located within the second portion using a redundant array of independent disks (RAID) memory mechanism, in response to the memory request being the write request.

Transactional execution of native methods

Approaches for more efficiently executing calls to native code from within a managed execution environment are described. The techniques involve attempting to execute a native call, such as a call to a C function from within Java code, using a single hardware transaction. Not only is the native code executed in a hardware transaction, but also various transitional operations needed for transitioning between managed execution mode and native execution mode. If the hardware transaction is successful, at least some of the operations that would normally be performed during transitions between modes may be omitted or simplified. If the hardware transaction is unsuccessful, the native calls may be performed as they normally would, outside of hardware transactions.