Patent classifications
G06F13/32
Method and system for processing data conflict
A method and a system for processing a data conflict are provided that relate to the field of signal interface technologies of an integrated circuit, where the method includes sending a power management bus (PMBus) command to a slave device by using a PMBus, so as to perform power management; when the PMBus command fails to be sent, determining whether the number of times that the PMBus command fails to be sent is greater than or equal to a preset value, where the preset value is configured in advance during system initialization; starting timing if the number of times that the PMBus command fails to be sent is less than the preset value; and resending the PMBus command when timing duration reaches resending time. The present invention is applicable to a scenario in which multiple master devices (Masters) send the PMBus command by using the PMBus.
Event specific page faults for interrupt handling
Various embodiments are generally directed to instrumenting an interrupt service routine. A non-executable address may be provisioned and added to an execution stack to cause a page fault on a known address after execution of an interrupt service routine. The page fault on the known address can be used to trigger instrumentation operations and also to return to the interrupted process.
Interrupt controller
An interrupt controller includes a fabric slave that can receive MMIO operation requests, a plurality of output interrupt lines, a plurality of interrupt registers with each interrupt register corresponding to an output interrupt line, a MMIO routing circuit in communication with the fabric slave and the interrupt registers, a plurality of input interrupt lines for receiving line interrupts, and a line interrupt routing circuit in communication with the input interrupt lines and the interrupt registers. The interrupt registers store data for an interrupt that serves as an indication of the source of the interrupt and/or what task(s) need to be done for the interrupt.
Forced detaching of applications from DMA-capable PCI mapped devices
A mechanism is provided in a data processing system comprising at least one processor and at least one memory, the at least one memory comprising instructions that are executed by the at least one processor and configure the at least one processor to implement a device context device driver for forced detaching of an application from mapped devices. The device context device driver receives a command to detach an application, wherein the command specifies a process descriptor associated with the application. The device context device driver identifies a plurality of matching device context entries in a list of open device contexts maintained by the device context device driver that match the process descriptor. The device context device driver marks the plurality of matching device context entries as detached. The device context device driver invalidates mapped memory areas associated with the plurality of matching device context entries. The device context device driver shuts down all device contexts associated with the plurality of matching device context entries.
Forced detaching of applications from DMA-capable PCI mapped devices
A mechanism is provided in a data processing system comprising at least one processor and at least one memory, the at least one memory comprising instructions that are executed by the at least one processor and configure the at least one processor to implement a device context device driver for forced detaching of an application from mapped devices. The device context device driver receives a command to detach an application, wherein the command specifies a process descriptor associated with the application. The device context device driver identifies a plurality of matching device context entries in a list of open device contexts maintained by the device context device driver that match the process descriptor. The device context device driver marks the plurality of matching device context entries as detached. The device context device driver invalidates mapped memory areas associated with the plurality of matching device context entries. The device context device driver shuts down all device contexts associated with the plurality of matching device context entries.
SR-IOV-SUPPORTED STORAGE RESOURCE ACCESS METHOD AND STORAGE CONTROLLER AND STORAGE DEVICE
An SR-IOV-supported storage resource access method is disclosed, the method includes: consolidating a storage medium as a unified storage resource, and dividing the unified storage resource into multiple storage sub-resources; allocating the storage sub-resources to at least one of a PF or a VF according to a preset allocation rule, and maintaining a resource allocation table including a mapping relationship between the storage sub-resources and at least one of PF or VF; receiving a host command sent by a virtual machine to a destination VF or by a virtual machine monitor to a destination PF; and searching the resource allocation table according to destination VF or destination PF, and performing, on a storage sub-resource corresponding to destination PF or destination VF and according to the mapping relationship between the storage sub-resources and the PF or the VF in the resource allocation table, an operation corresponding to the host command.
SR-IOV-SUPPORTED STORAGE RESOURCE ACCESS METHOD AND STORAGE CONTROLLER AND STORAGE DEVICE
An SR-IOV-supported storage resource access method is disclosed, the method includes: consolidating a storage medium as a unified storage resource, and dividing the unified storage resource into multiple storage sub-resources; allocating the storage sub-resources to at least one of a PF or a VF according to a preset allocation rule, and maintaining a resource allocation table including a mapping relationship between the storage sub-resources and at least one of PF or VF; receiving a host command sent by a virtual machine to a destination VF or by a virtual machine monitor to a destination PF; and searching the resource allocation table according to destination VF or destination PF, and performing, on a storage sub-resource corresponding to destination PF or destination VF and according to the mapping relationship between the storage sub-resources and the PF or the VF in the resource allocation table, an operation corresponding to the host command.
PRODUCER/CONSUMER REMOTE SYNCHRONIZATION
Remotely synchronizing data communicated in an electronic computing system. Ordered writing of a data set of discrete data packets (data) and a following associated semaphore packet (semaphore) from a source electronic device (source) to a bridge interface device (bridge). Relaxed writing of the data set from the bridge to discrete target memory addresses (targets) of a data-consuming electronic device (consumer), wherein the order of the data and the semaphore written to the targets is different than the order of the data and semaphore written with the ordered writing. Monitoring, by the consumer, the relaxed writing of the semaphore to one of the targets. Issuing a synchronization command to the bridge upon detection of the semaphore having been written to the one target. Sending a synchronization confirmation reply from the bridge after all of the data has been written to the targets.
DATA COMMUNICATION INTERFACE FOR PROCESSING DATA IN LOW POWER SYSTEMS
Improvements over existing data collection interfaces disclosed herein include, among other things, additional logic blocks (and associated timers, state machines, and registers) to off-load data collection and data processing prior to waking a microprocessor from a sleep mode. For example, an improved data collection interface collects a predetermined number of sensor values from a sensor while maintaining active a single communication session with the sensor over a pin of the interface. The microprocessor remains in the sleep mode for an entire duration of the single communication session. The data collection interface can reduce the likelihood of false starts of the microprocessor by using the logic blocks to verify that data meet preconditions prior to interrupting the microprocessor. The data collection interface can reduce the overall power consumption of a chip in which the microprocessor is integrated by a factor of at least about 2× (i.e., 50% reduction in power consumption).
DATA COMMUNICATION INTERFACE FOR PROCESSING DATA IN LOW POWER SYSTEMS
Improvements over existing data collection interfaces disclosed herein include, among other things, additional logic blocks (and associated timers, state machines, and registers) to off-load data collection and data processing prior to waking a microprocessor from a sleep mode. For example, an improved data collection interface collects a predetermined number of sensor values from a sensor while maintaining active a single communication session with the sensor over a pin of the interface. The microprocessor remains in the sleep mode for an entire duration of the single communication session. The data collection interface can reduce the likelihood of false starts of the microprocessor by using the logic blocks to verify that data meet preconditions prior to interrupting the microprocessor. The data collection interface can reduce the overall power consumption of a chip in which the microprocessor is integrated by a factor of at least about 2× (i.e., 50% reduction in power consumption).