Region-based processing

By dividing HDR images into regions and adjusting the encoding amount according to brightness and foreground/background characteristics, the bandwidth and power consumption problems of HDR content transmission in wireless displays are solved, achieving efficient resource utilization and maintenance of image quality.

CN108694696BActive Publication Date: 2024-11-29INTEL CORP
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN201810315252.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2018-04-10
Publication Date
2024-11-29
Estimated Expiration
2038-04-10

AI Technical Summary

Technical Problem

In wireless displays, the encoding and transmission of video signals for high dynamic range (HDR) content increases wireless link bandwidth usage, power consumption, and cost, especially when the video signal contains HDR content, a problem that current technologies have failed to effectively address.

Method used

By dividing an HDR image into multiple regions and dynamically adjusting the amount of coding based on the brightness level and foreground/background characteristics of each region, link bandwidth consumption and power consumption can be reduced while maintaining image quality.

Benefits of technology

It effectively reduces link bandwidth and power consumption during wireless transmission while maintaining image quality. In particular, it optimizes resource utilization by encoding less of the high-brightness and foreground areas and more of the low-brightness or background areas.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN108694696B_ABST
    Figure CN108694696B_ABST
Patent Text Reader

Abstract

The present invention relates to region-based processing. Systems, devices, and methods can provide a technique that divides a high dynamic range (HDR) image into a plurality of regions and determines a brightness level of the HDR image on a per-region basis. Additionally, the technique can select an encoding amount for each of the plurality of regions based on brightness level on a per-image basis.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments generally relate to graphics processing architectures. More particularly, embodiments relate to region-based processing in graphics processing architectures. Background Art

[0002] In a wireless display setting, a source platform (e.g., a game console, a computer) may encode (e.g., compress) a video signal such as a movie or a three-dimensional (3D) game for wireless transmission to a display. Each frame of the video signal may be encoded in a uniform manner and placed in a frame buffer, which is synchronized to the display output. The uniform encoding of frames may increase wireless link bandwidth usage, power consumption, and / or cost, particularly if the video signal contains high dynamic range (HDR) content. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Various advantages of the embodiments will become apparent to those skilled in the art upon reading the following description and appended claims and by referring to the following drawings, in which:

[0004] Figure 1 is a block diagram illustrating a computer system configured to implement one or more aspects of the embodiments described herein;

[0005] Figure 2A-2D Figure illustrates a parallel processor assembly according to an embodiment;

[0006] Figure 3A-3B is a block diagram of a graphics multiprocessor according to an embodiment;

[0007] Figure 4A-4F Figure illustrates an exemplary architecture in which multiple GPUs are communicatively coupled to multiple multi-core processors;

[0008] Figure 5 The figure illustrates a graphics processing pipeline according to an embodiment;

[0009] Fig. 6A is an illustration of an example of a high dynamic range (HDR) image divided into a plurality of regions according to an embodiment;

[0010] Figure 6B is an illustration of an example of an HDR image divided into a foreground area and a background area according to an embodiment;

[0011] Figure 7 is a block diagram of an example of a region-based processing architecture according to an embodiment;

[0012] Fig. 8A is a flowchart of an example of a method of operating a semiconductor packaging apparatus according to an embodiment;

[0013] Figure 8Bis a flowchart of an example of a method for selecting an encoding amount based on a brightness level according to an embodiment;

[0014] Figure 8C is a flowchart of an example of a method of selecting encoding amounts for background and foreground areas according to an embodiment;

[0015] Fig. 9 is a block diagram of an example of a computing system according to an embodiment;

[0016] Fig.10 is a diagram of an example of a semiconductor packaging device according to an embodiment;

[0017] Fig.11 is a block diagram of an example of a display having localized backlight capability according to an embodiment;

[0018] Fig. 12A is a block diagram of an example of a data processing device according to an embodiment;

[0019] Fig. 12B is an illustration of an example of distance determination according to an embodiment;

[0020] Fig.13 is a block diagram of an example of a layered display architecture according to an embodiment;

[0021] Fig.14 is a block diagram of an example of a display architecture including a plurality of display units according to an embodiment; and

[0022] Fig.15 is a block diagram of an example of a cloud-assisted media delivery architecture according to an embodiment;

[0023] Figure 16-18 is a block diagram of an example of an overview of a data processing system according to an embodiment;

[0024] Fig.19 is a block diagram of an example of a graphics processing engine according to an embodiment;

[0025] Figure 20-22 is a block diagram of an example of an execution unit according to an embodiment;

[0026] Fig.23 is a block diagram of an example of a graphics pipeline according to an embodiment;

[0027] Figure 24A-24B is a block diagram of an example of graphics pipeline programming according to an embodiment;

[0028] Fig.25 is a block diagram of an example of a graphics software architecture according to an embodiment;

[0029] Fig.26is a block diagram of an example of an intellectual property (IP) core development system according to an embodiment; and

[0030] Fig. 27 is a block diagram of an example of a system on a chip integrated circuit according to an embodiment. DETAILED DESCRIPTION

[0031] In the following description, many specific details are set forth to provide a more comprehensive understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced without one or more of these specific details. In other examples, well-known features are not described in order to avoid obscuring the present invention.

[0032] System Overview

[0033] Figure 1 1 is a block diagram of a computing system 100 configured to implement one or more aspects of the embodiments described herein. The computing system 100 includes a processing subsystem 101 having one or more processors 102 and a system memory 104 that communicate via an interconnect path, which may include a memory hub 105. The memory hub 105 may be a separate component within a chipset component, or may be integrated within the one or more processors 102. The memory hub 105 is coupled to an I / O subsystem 111 via a communication link 106. The I / O subsystem 111 includes an I / O hub 107, which may enable the computing system 100 to receive input from one or more input devices 108. In addition, the I / O hub 107 may enable a display controller that may be included in the one or more processors 102 to provide output to one or more display devices 110A. In one embodiment, the one or more display devices 110A coupled to the I / O hub 107 may include local, internal, or embedded display devices.

[0034] In one embodiment, the processing subsystem 101 includes one or more parallel processors 112 coupled to the memory hub 105 via a bus or other communication link 113. The communication link 113 can be one of any number of standard-based communication link technologies or protocols, such as but not limited to PCI Express, or can be a vendor-specific communication interface or communication structure. In one embodiment, the one or more parallel processors 112 form a computationally focused parallel or vector processing system that includes a large number of processing cores and / or processing clusters, such as many integrated core (MIC) processors. In one embodiment, the one or more parallel processors 112 form a graphics processing subsystem that can output pixels to one of one or more display devices 110A coupled via the I / O hub 107. The one or more parallel processors 112 may also include a display controller and display interface (not shown) to enable direct connection to one or more display devices 110B.

[0035] Within the I / O subsystem 111, a system storage unit 114 may be connected to the I / O hub 107 to provide a storage mechanism for the computing system 100. An I / O switch 116 may be used to provide an interface mechanism to enable connection between the I / O hub 107 and other components that may be integrated into the platform, such as a network adapter 118 and / or a wireless network adapter 119, as well as various other devices that may be added via one or more plug-in devices 120. The network adapter 118 may be an Ethernet adapter or another wired network adapter. The wireless network adapter 119 may include one or more of Wi-Fi, Bluetooth, near field communication (NFC), or other network devices including one or more wireless radios.

[0036] The computing system 100 may include other components not explicitly shown, including USB or other port connections, optical storage drives, video capture devices, etc., which may also be connected to the I / O hub 107. Figure 1 The communication paths interconnecting the various components in the system may be implemented using any suitable protocol such as a PCI (Peripheral Component Interconnect) based protocol (e.g., PCI-Express) or any other bus or point-to-point communication interface and / or protocol(s) (such as the NV-Link high-speed interconnect or an interconnect protocol known in the art).

[0037] In one embodiment, one or more parallel processors 112 incorporate circuits optimized for graphics and video processing, including, for example, video output circuits, and constitute a graphics processing unit (GPU). In another embodiment, one or more parallel processors 112 incorporate circuits optimized for general-purpose processing while retaining the underlying computing architecture, which is described in more detail herein. In yet another embodiment, the components of the computing system 100 may be integrated with one or more other system elements on a single integrated circuit. For example, one or more parallel processors 112, a memory hub 105, (one or more) processors 102, and an I / O hub 107 may be integrated into a system-on-chip (SoC) integrated circuit. Alternatively, the components of the computing system 100 may be integrated into a single package to form a system-in-package (SIP) configuration. In one embodiment, at least a portion of the components of the computing system 100 may be integrated into a multi-chip module (MCM), which may be interconnected with other multi-chip modules into a modular computing system.

[0038] It should be understood that the computing system 100 shown herein is illustrative, and variations and modifications are possible. The connection topology including the number and arrangement of bridges, the number of (one or more) processors 102, and the number of (one or more) parallel processors 112 can be modified as needed. For example, in some embodiments, the system memory 104 is not directly connected to the (one or more) processors 102 through a bridge, while other devices communicate with the system memory 104 via the memory hub 105 and the (one or more) processors 102. In other alternative topologies, (one or more) parallel processors 112 are connected to the I / O hub 107 or directly to one of the one or more processors 102, rather than to the memory hub 105. In other embodiments, the I / O hub 107 and the memory hub 105 can be integrated into a single chip. Some embodiments may include two or more sets of (one or more) processors 102 attached via multiple sockets, which can be coupled with two or more instances of (one or more) parallel processors 112.

[0039] Some specific components shown herein are optional and may not be included in all implementations of computing system 100. For example, any number of plug-in cards or peripherals may be supported, or some components may be eliminated. In addition, some architectures may be specific to the Figure 1 Different terminology is used for components that are similar to those illustrated in FIG. 1. For example, the memory hub 105 may be referred to as a north bridge in some architectures, while the I / O hub 107 may be referred to as a south bridge.

[0040] Figure 2AThe figure shows a parallel processor 200 according to one embodiment. The various components of the parallel processor 200 may be implemented using one or more integrated circuit devices such as a programmable processor, an application specific integrated circuit (ASIC), or a field programmable gate array (FPGA). According to an embodiment, the illustrated parallel processor 200 is Figure 1 A variation of one or more parallel processors 112 is shown in .

[0041] In one embodiment, parallel processor 200 includes parallel processing unit 202. Parallel processing unit includes I / O unit 204, which is capable of communicating with other devices including other instances of parallel processing unit 202. I / O unit 204 can be directly connected to other devices. In one embodiment, I / O unit 204 is connected to other devices via the use of a hub or switch interface such as memory hub 105. The connection between memory hub 105 and I / O unit 204 forms communication link 113. Within parallel processing unit 202, I / O unit 204 is connected to host interface 206 and memory cross switch 216, wherein host interface 206 receives commands directed to perform processing operations and memory cross switch 216 receives commands directed to perform memory operations.

[0042] When the host interface 206 receives the command buffer via the I / O unit 204, the host interface 206 can direct the work operations to execute those commands to the front end 208. In one embodiment, the front end 208 is coupled with a scheduler 210, which is configured to distribute commands or other work items to the processing cluster array 212. In one embodiment, the scheduler 210 ensures that the processing cluster array 212 is properly configured and is in a valid state before tasks are distributed to the processing clusters of the processing cluster array 212. In one embodiment, the scheduler 210 is implemented via firmware logic executed on a microcontroller. The microcontroller-implemented scheduler 210 can be configured to perform complex scheduling and work distribution operations at coarse and fine granularity, achieving fast preemption and context switching of threads executing on the processing array 212. In one embodiment, the host software can prove the workload for scheduling on the processing array 212 via one of a plurality of graphics processing doorbells. The workload can then be automatically distributed on the processing array 212 by the scheduler 210 logic within the scheduler microcontroller.

[0043] The processing cluster array 212 may include up to "N" processing clusters (e.g., cluster 214A, cluster 214B, up to cluster 214N). Each cluster 214A-214N of the processing cluster array 212 may execute a large number of concurrent threads. The scheduler 210 may use various scheduling and / or work distribution algorithms to assign work to the clusters 214A-214N of the processing cluster array 212, which may vary depending on the workload generated for each type of program or calculation. Scheduling may be handled dynamically by the scheduler 210, or may be assisted in part by compiler logic during the compilation of program logic configured to be executed by the processing cluster array 212. In one embodiment, different clusters 214A-214N of the processing cluster array 212 may be assigned to process different types of programs or to perform different types of calculations.

[0044] Processing cluster array 212 may be configured to perform various types of parallel processing operations. In one embodiment, processing cluster array 212 is configured to perform general-purpose parallel computing operations. For example, processing cluster array 212 may include logic to perform processing tasks including filtering of video and / or audio data, performing modeling operations including physical operations, and performing data transformations.

[0045] In one embodiment, processing cluster array 212 is configured to perform parallel graphics processing operations. In embodiments where parallel processor 200 is configured to perform graphics processing operations, processing cluster array 212 may include additional logic to support the execution of such graphics processing operations, including but not limited to texture sampling logic to perform texture operations, and tessellation logic and other vertex processing logic. In addition, processing cluster array 212 may be configured to execute shader programs associated with graphics processing, such as but not limited to vertex shaders, tessellation shaders, geometry shaders, and pixel shaders. Parallel processing unit 202 may transfer data from system memory via I / O unit 204 for processing. During processing, the transferred data may be stored to on-chip memory (e.g., parallel processor memory 222) during processing and then written back to system memory.

[0046] In one embodiment, when parallel processing unit 202 is used to perform graphics processing, scheduler 210 can be configured to divide the processing workload into tasks of approximately equal size to better distribute graphics processing operations to multiple clusters 214A-214N of processing cluster array 212. In some embodiments, portions of processing cluster array 212 can be configured to perform different types of processing. For example, a first portion can be configured to perform vertex shading and topology generation, a second portion can be configured to perform tessellation and geometry shading, and a third portion can be configured to perform pixel shading or other screen space operations to produce a rendered image for display. Intermediate data generated by one or more of clusters 214A-214N can be stored in a buffer to allow the intermediate data to be transferred between clusters 214A-214N for further processing.

[0047] During operation, the processing cluster array 212 may receive processing tasks to be executed via the scheduler 210, which receives commands defining the processing tasks from the front end 208. For graphics processing operations, the processing tasks may include indices of data to be processed, such as surface (patch) data, primitive data, vertex data, and / or pixel data, and state parameters and commands defining how the data is to be processed (e.g., what program is to be executed). The scheduler 210 may be configured to obtain an index corresponding to a task, or may receive an index from the front end 208. The front end 208 may be configured to ensure that the processing cluster array 212 is configured to be in a valid state before a workload specified by an incoming command buffer (e.g., a batch-buffer, a push buffer, etc.) is initiated.

[0048] Each of the one or more instances of the parallel processing unit 202 may be coupled to a parallel processor memory 222. The parallel processor memory 222 may be accessed via a memory crossbar 216, which may receive memory requests from the processing cluster array 212 and the I / O unit 204. The memory crossbar 216 may access the parallel processor memory 222 via a memory interface 218. The memory interface 218 may include a plurality of partition units (e.g., partition unit 220A, partition unit 220B, up to partition unit 220N), each of which may be coupled to a portion (e.g., memory cells) of the parallel processor memory 222. In one implementation, the number of partition units 220A-220N is configured to be equal to the number of memory cells, such that the first partition unit 220A has a corresponding first memory cell 224A, the second partition unit 220B has a corresponding memory cell 224B, and the Nth partition unit 220N has a corresponding Nth memory cell 224N. In other embodiments, the number of partition units 220A-220N may not be equal to the number of memory devices.

[0049] In various embodiments, the memory units 224A-224N may include various types of memory devices, including dynamic random access memory (DRAM) or graphics random access memory such as synchronous graphics random access memory (SGRAM), which includes graphics double data rate (GDDR) memory. In one embodiment, the memory units 224A-224N may also include 3D stacked memory, including but not limited to high bandwidth memory (HBM). Those skilled in the art will appreciate that the specific implementation of the memory units 224A-224N may vary and may be selected from one of a variety of conventional designs. Rendering targets such as frame buffers or texture maps may be stored on the memory units 224A-224N, allowing the partition units 220A-220N to write to portions of each rendering target in parallel to efficiently use the available bandwidth of the parallel processor memory 222. In some embodiments, a unified memory design of the system memory may be used in conjunction with a local cache memory to eliminate local instances of the parallel processor memory 222.

[0050] In one embodiment, any of the clusters 214A-214N of the processing cluster array 212 can process data to be written to any memory unit 224A-224N within the parallel processor memory 222. The memory crossbar 216 can be configured to transmit the output of each cluster 214A-214N to any partition unit 220A-220N or another cluster 214A-214N, which can perform additional processing operations on the output. Each cluster 214A-214N can communicate with the memory interface 218 through the memory crossbar 216 to read or write to various external memory devices. In one embodiment, the memory crossbar 216 has a connection to the memory interface 218 to communicate with the I / O unit 204, as well as a connection to the local instance of the parallel processor memory 222, so that the processing units within different processing clusters 214A-214N can communicate with the system memory or other memory that is not local to the parallel processing unit 202. In one embodiment, the memory crossbar switch 216 may use virtual channels to separate traffic flows between the clusters 214A-214N and the partition units 220A-220N.

[0051] Although a single instance of parallel processing unit 202 is illustrated in parallel processor 200, any number of instances of parallel processing unit 202 may be included. For example, multiple instances of parallel processing unit 202 may be provided on a single plug-in card, or multiple plug-in cards may be interconnected. Even if different instances have different numbers of processing cores, different numbers of local parallel processor memories, and / or other configuration differences, different instances of parallel processing unit 202 may also be configured to interoperate. For example and in one embodiment, some instances of parallel processing unit 202 may include higher precision floating point units relative to other instances. Systems incorporating one or more instances of parallel processing unit 202 or parallel processor 200 may be implemented with various configurations and form factors, including but not limited to desktop computers, laptop computers or handheld personal computers, servers, workstations, game consoles, and / or embedded systems.

[0052] Figure 2B is a block diagram of a partition unit 220 according to one embodiment. In one embodiment, the partition unit 220 is Figure 2A 20A-20N。 As shown, the partition unit 220 includes an L2 cache 221, a frame buffer interface 225 and an ROP 226 (raster operation unit). The L2 cache 221 is a read / write cache that is configured to perform load and store operations received from the memory crossbar switch 216 and the ROP 226. Read misses and urgent write-back requests are output by the L2 cache 221 to the frame buffer interface 225 for processing. Updates can also be sent to the frame buffer via the frame buffer interface 225 for processing. In one embodiment, the frame buffer interface 225 interfaces with one of the memory units in the parallel processor memory, such as the memory units 224A-224N of Figure 2 (e.g., within the parallel processor memory 222).

[0053] In graphics applications, ROP 226 is a processing unit that performs raster operations such as stenciling, z-testing, blending, etc. ROP 226 then outputs processed graphics data that is stored in graphics memory. In some embodiments, ROP 226 includes compression logic to compress depth or color data written to memory and decompress depth or color data read from memory. The compression logic can be lossless compression logic that uses one or more of a variety of compression algorithms. The type of compression performed by ROP 226 can vary based on the statistical characteristics of the data to be compressed. For example, in one embodiment, incremental color compression is performed on depth and color data on a per-tile basis.

[0054] In some embodiments, ROP 226 is included within each processing cluster (e.g., clusters 214A-214N of FIG. 2 ) rather than within partition unit 220. In such embodiments, read and write requests for pixel data, rather than pixel fragment data, are transmitted through memory crossbar 216. The processed graphics data may be displayed on a display such as Figure 1 on a display device of one of the one or more display devices 110, routed for further processing by the processor(s) 102, or routed for Figure 2A One of the processing entities within parallel processor 200 further processes.

[0055] Figure 2C 2 is a block diagram of a processing cluster 214 within a parallel processing unit according to one embodiment. In one embodiment, the processing cluster is an instance of one of the processing clusters 214A-214N of FIG. 2. The processing cluster 214 can be configured to execute multiple threads in parallel, wherein the term "thread" refers to an instance of a specific program executed on a specific input data set. In some embodiments, single instruction multiple data (SIMD) instruction issuance technology is used to support the parallel execution of a large number of threads without providing multiple independent instruction units. In other embodiments, a common instruction unit configured to issue instructions to a group of processing engines within each processing cluster is used, and a single instruction multiple thread (SIMT) technology is used to support the parallel execution of a large number of threads that are usually synchronized. Unlike the SIMD execution regime in which all processing engines usually execute the same instruction, SIMT execution allows different threads to more easily follow the forked execution path through a given thread program. It will be understood by those skilled in the art that the SIMD processing regime represents a functional subset of the SIMT processing regime.

[0056] The operation of the processing cluster 214 can be controlled via a pipeline manager 232 that distributes processing tasks to SIMT parallel processors. The pipeline manager 232 receives instructions from the scheduler 210 of Figure 2 and manages the execution of those instructions via the graphics multiprocessor 234 and / or the texture unit 236. The illustrated graphics multiprocessor 234 is an exemplary instance of a SIMT parallel processor. However, various types of SIMT parallel processors of different architectures can be included in the processing cluster 214. One or more instances of the graphics multiprocessor 234 can be included in the processing cluster 214. The graphics multiprocessor 234 can process data, and the data crossbar 240 can be used to distribute the processed data to one of multiple possible destinations including other shading units. The pipeline manager 232 can facilitate the distribution of processed data by specifying a destination for the processed data to be distributed via the data crossbar 240.

[0057] Each graphics multiprocessor 234 within a processing cluster 214 may include an identical set of function execution logic (e.g., arithmetic logic units, load store units, etc.). The function execution logic may be configured in a pipelined manner, in which new instructions may be issued before previous instructions are completed. The function execution logic supports a variety of operations, including integer and floating point arithmetic, comparison operations, Boolean operations, displacements, and calculations of various algebraic functions. In one embodiment, the same functional unit hardware may be utilized to perform different operations, and any combination of functional units may be present.

[0058] The instructions transmitted to the processing cluster 214 constitute threads. A group of threads executed on the group of parallel processing engines is a thread group. A thread group executes the same program on different input data. Each thread in the thread group can be assigned to a different processing engine in the graphics multiprocessor 234. The thread group can include fewer threads than the number of processing engines in the graphics multiprocessor 234. When the thread group includes fewer threads than the number of processing engines, one or more of the processing engines may be idle during the cycle of processing the thread group. The thread group can also include more threads than the number of processing engines in the graphics multiprocessor 234. When the thread group includes more threads than the number of processing engines in the graphics multiprocessor 234, processing can be performed on continuous clock cycles. In one embodiment, multiple thread groups can be executed simultaneously on the graphics multiprocessor 234.

[0059] In one embodiment, the graphics multiprocessor 234 includes an internal cache memory to perform load and store operations. In one embodiment, the graphics multiprocessor 234 can abandon the internal cache and use the cache memory (e.g., L1 cache 308) within the processing cluster 214. Each graphics multiprocessor 234 can also access the L2 cache within the partition unit (e.g., the partition unit 220A-220N of Figure 2), which is shared between all processing clusters 214 and can be used to transfer data between threads. The graphics multiprocessor 234 can also access the off-chip global memory, which can include one or more of the local parallel processor memory and / or system memory. Any memory external to the parallel processing unit 202 can be used as global memory. In which the processing cluster 214 includes multiple instances of the graphics multiprocessor 234, the embodiment can share common instructions and data that can be stored in the L1 cache 308.

[0060] Each processing cluster 214 may include an MMU 245 (memory management unit) configured to map virtual addresses to physical addresses. In other embodiments, one or more instances of the MMU 245 may reside within the memory interface 218 of FIG. 2 . The MMU 245 includes a set of page table entries (PTEs) used to map virtual addresses to physical addresses of tiles (more on tile tiling) and optional cache line indexes. The MMU 245 may include an address translation lookaside buffer (TLB) or cache that may reside within the graphics multiprocessor 234 or L1 cache or processing cluster 214. Physical addresses are processed to distribute surface data access locality to allow efficient request interleaving between partition units. The cache line index may be used to determine whether a request for a cache line is a hit or a miss.

[0061] In graphics and computing applications, the processing clusters 214 can be configured such that each graphics multiprocessor 234 is coupled to a texture unit 236 for performing texture mapping operations, such as determining texture sample locations, reading texture data, and filtering texture data. Texture data is read from an internal texture L1 cache (not shown) or in some embodiments from an L1 cache within the graphics multiprocessor 234, and retrieved from an L2 cache, local parallel processor memory, or system memory as needed. Each graphics multiprocessor 234 outputs processed tasks to a data crossbar 240 to provide the processed tasks to another processing cluster 214 for further processing or to store the processed tasks in an L2 cache, local parallel processor memory, or system memory via a memory crossbar 216. A PreROP 242 (pre-raster operation unit) is configured to receive data from the graphics multiprocessor 234, direct the data to a ROP unit, which may be located within a partition unit (e.g., partition units 220A-220N of FIG. 2 ) as described herein. The preROP 242 unit may perform optimizations for color blending, organize pixel color data, and perform address translations.

[0062] It should be understood that the core architecture described herein is illustrative and that various variations and modifications are possible. Any number of processing units, such as graphics multiprocessor 234, texture unit 236, PreROP 242, etc., may be included in processing cluster 214. In addition, although only one processing cluster 214 is shown, the parallel processing unit described herein may include any number of instances of processing cluster 214. In one embodiment, each processing cluster 214 may be configured to operate independently of other processing clusters 214 using separate and different processing units, L1 caches, etc.

[0063] Figure 2DA graphics multiprocessor 234 is shown according to one embodiment. In such an embodiment, the graphics multiprocessor 234 is coupled to a pipeline manager 232 of a processing cluster 214. The graphics multiprocessor 234 has an execution pipeline including, but not limited to, an instruction cache 252, an instruction unit 254, an address mapping unit 256, a register file 258, one or more general purpose graphics processing unit (GPGPU) cores 262, and one or more load / store units 266. The GPGPU cores 262 and the load / store units 266 are coupled to a cache memory 272 and a shared memory 270 via a memory and cache interconnect 268.

[0064] In one embodiment, the instruction cache 252 receives a stream of instructions to be executed from the pipeline manager 232. The instructions are cached in the instruction cache 252 and dispatched by the instruction unit 254 for execution. The instruction unit 254 can dispatch instructions into thread groups (e.g., warps), where each thread of the thread group is assigned to a different execution unit within the GPGPU core 262. The instruction can access any of the local, shared, or global address spaces by specifying an address within the unified address space. The address mapping unit 256 can be used to convert addresses in the unified address space into different memory addresses that can be accessed by the load / store unit 266.

[0065] Register file 258 provides a set of registers for the functional units of graphics multiprocessor 324. Register file 258 provides temporary storage for operands for data paths of functional units (e.g., GPGPU core 262, load / store unit 266) connected to graphics multiprocessor 324. In one embodiment, register file 258 is divided between each functional unit so that each functional unit is assigned a dedicated portion of register file 258. In one embodiment, register file 258 is divided between different warps executed by graphics multiprocessor 324.

[0066] The GPGPU cores 262 may each include a floating point unit (FPU) and / or an integer arithmetic logic unit (ALU) for executing instructions of the graphics multiprocessor 324. The GPGPU cores 262 may be similar in architecture or may be different in architecture according to the embodiment. For example and in one embodiment, the first part of the GPGPU core 262 includes a single-precision FPU and an integer ALU, while the second part of the GPGPU core includes a double-precision FPU. In one embodiment, the FPU may implement the IEEE 754-2008 standard for floating-point arithmetic or enable variable-precision floating-point arithmetic. The graphics multiprocessor 324 may additionally include one or more fixed-function or special-function units to perform specific functions such as copying rectangles or pixel blending operations. In one embodiment, one or more GPGPU cores may also include fixed or special function logic.

[0067] In one embodiment, GPGPU core 262 includes SIMD logic capable of executing a single instruction to multiple sets of data. In one embodiment, GPGPU core 262 can physically execute SIMD4, SIMD8 and SIMD16 instructions, and logically execute SIMD1, SIMD2 and SIMD32 instructions. SIMD instructions for GPGPU core can be generated by a shader compiler at compile time, or automatically generated when executing a program written and compiled for a single program multiple data (SPMD) or SIMT architecture. Multiple threads of a program configured for a SIMT execution model can be executed via a single SIMD instruction. For example and in one embodiment, eight SIMT threads performing the same or similar operation can be executed in parallel via a single SIMD8 logic unit.

[0068] The memory and cache interconnect 268 is an interconnect network that connects each functional unit of the graphics multiprocessor 324 to the register file 258 and the shared memory 270. In one embodiment, the memory and cache interconnect 268 is a crossbar interconnect that allows the load / store unit 266 to implement load and store operations between the shared memory 270 and the register file 258. The register file 258 can operate at the same frequency as the GPGPU core 262, so the data transfer between the GPGPU core 262 and the register file 258 is very low latency. The shared memory 270 can be used to implement communication between threads executed on the functional units within the graphics multiprocessor 234. For example, the cache memory 272 can be used as a data cache to cache texture data transferred between the functional unit and the texture unit 236. The shared memory 270 can also be used as a program management cache. In addition to the automatically cached data stored in the cache memory 272, threads executing on the GPGPU core 262 can also programmatically store data in the shared memory.

[0069] Figure 3A-3B The figure shows additional graphics multiprocessors according to an embodiment. The illustrated graphics multiprocessors 325, 350 are Figure 2C The illustrated graphics multiprocessors 325, 350 may be configured as streaming multiprocessors (SMs) capable of executing a large number of execution threads simultaneously.

[0070] Figure 3A FIG. 3 shows a graphics multiprocessor 325 according to another embodiment. The graphics multiprocessor 325 includes a Figure 2D The graphics multiprocessor 325 may include multiple additional instances of execution resource units of the graphics multiprocessor 234. For example, the graphics multiprocessor 325 may include multiple instances of instruction units 332A-332B, register files 334A-334B, and (one or more) texture units 344A-344B. The graphics multiprocessor 325 also includes multiple groups of graphics or compute execution units (e.g., GPGPU cores 336A-336B, GPGPU cores 337A-337B, GPGPU cores 338A-338B) and multiple groups of load / store units 340A-340B. In one embodiment, the execution resource units have a common instruction cache 330, texture and / or data cache memory 342, and shared memory 346.

[0071] Various components may communicate via interconnect structure 327. In one embodiment, interconnect structure 327 includes one or more crossbar switches to enable communication between various components of graphics multiprocessor 325. In one embodiment, interconnect structure 327 is a separate high-speed network fabric layer on which each component of graphics multiprocessor 325 is stacked. Components of graphics multiprocessor 325 communicate with remote components via interconnect structure 327. For example, GPGPU cores 336A-336B, 337A-337B, and 3378A-338B may each communicate with shared memory 346 via interconnect structure 327. Interconnect structure 327 may arbitrate communications within graphics multiprocessor 325 to ensure fair bandwidth allocation between components.

[0072] Figure 3B FIG. 3 shows a graphics multiprocessor 350 according to another embodiment. The graphics processor includes multiple sets of execution resources 356A-356D, wherein each set of execution resources includes multiple instruction units, register files, GPGPU cores, and load storage units, such as Figure 2D and Figure 3A . While sharing the instruction cache 354 and shared memory 362, the execution resources 356A-356D can work in conjunction with (one or more) texture units 360A-360D for texture operations. In one embodiment, the execution resources 356A-356D can share the instruction cache 354 and shared memory 362, as well as multiple instances of texture and / or data cache memories 358A-358B. The various components can be connected via Figure 3A The interconnect structure 327 communicates with a similar interconnect structure 352 .

[0073] Those skilled in the art will understand that Figure 1 , Figure 2A-2D and Figure 3A-3B The architecture described in is illustrative and does not limit the scope of the present embodiments. Therefore, the techniques described herein can be implemented on any appropriately configured processing unit, including but not limited to one or more mobile application processors, one or more desktop or server central processing units (CPUs) including multi-core CPUs, one or more parallel processing units such as parallel processing unit 202 of FIG. 2, and one or more graphics processors or special processing units without departing from the scope of the embodiments described herein.

[0074] In some embodiments, a parallel processor or GPGPU as described herein is communicatively coupled to a host / processor core to accelerate graphics operations, machine learning operations, pattern analysis operations, and various general-purpose GPU (GPGPU) functions. The GPU can be communicatively coupled to the host processor / core via a bus or other interconnect (e.g., a high-speed interconnect such as PCIe or NVLink). In other embodiments, the GPU can be integrated on the same package or chip as the core and communicatively coupled to the core via an internal processor bus / interconnect (i.e., inside the package or chip). Regardless of how the GPU is connected, the processor core can assign work to the GPU in the form of a sequence of commands / instructions contained in a work descriptor. The GPU then uses dedicated circuits / logic to efficiently process these commands / instructions.

[0075] Technologies for interconnecting GPUs with host processors

[0076] Figure 4A The figure shows an exemplary architecture in which multiple GPUs 410-413 are communicatively coupled to multiple multi-core processors 405-406 via high-speed links 440-443 (e.g., buses, point-to-point interconnects, etc.). In one embodiment, the high-speed links 440-443 support 4GB / s, 30GB / s, 80GB / s, or higher communication throughputs, depending on the implementation. Various interconnect protocols may be used, including but not limited to PCIe 4.0 or 5.0 and NVLink 2.0. However, the underlying principles of the invention are not limited to any particular communication protocol or throughput.

[0077] Additionally, in one embodiment, two or more GPUs 410-413 are interconnected via high-speed links 444-445, which may be implemented using the same or different protocols / links as used for high-speed links 440-443. Similarly, two or more of multi-core processors 405-406 may be connected via high-speed link 433, which may be a symmetric multiprocessor (SMP) bus running at 20 GB / s, 30 GB / s, 120 GB / s, or higher. Alternatively, Figure 4A All communications between the various system components shown in can be accomplished using the same protocol / links (eg, through a common interconnect structure). However, as mentioned, the underlying principles of the invention are not limited to any particular type of interconnect technology.

[0078] In one embodiment, each multi-core processor 405-406 is communicatively coupled to processor memory 401-402 via memory interconnects 430-431, respectively, and each GPU 410-413 is communicatively coupled to GPU memory 420-423 via GPU memory interconnects 450-453, respectively. Memory interconnects 430-431 and 450-453 may utilize the same or different memory access technologies. By way of example and not limitation, processor memory 401-402 and GPU memory 420-423 may be volatile memory such as dynamic random access memory (DRAM) (including stacked DRAM), graphics DDR SDRAM (GDDR) (e.g., GDDR5, GDDR6), or high bandwidth memory (HBM) and / or may be non-volatile memory such as 3D XPoint or Nano-Ram. In one embodiment, a portion of the memory may be volatile memory and another portion may be non-volatile memory (e.g., using a two-level memory (2LM) hierarchical structure).

[0079] As described below, although the various processors 405-406 and GPUs 410-413 may be physically coupled to specific memories 401-402, 420-423, respectively, a unified memory architecture may be implemented in which the same virtual system address space (also referred to as an "effective address" space) is distributed across all of the various physical memories. For example, the processor memories 401-402 may each include 64GB of system memory address space, and the GPU memories 420-423 may each include 32GB of system memory address space (resulting in a total of 256GB of addressable memory in this example).

[0080] Figure 4B The figure shows additional details for the interconnection between the multi-core processor 407 and the graphics acceleration module 446 according to one embodiment. The graphics acceleration module 446 may include one or more GPU chips integrated on a line card coupled to the processor 407 via the high-speed link 440. Alternatively, the graphics acceleration module 446 may be integrated on the same package or chip as the processor 407.

[0081] The illustrated processor 407 includes a plurality of cores 460A-460D, each core having a translation lookaside buffer 461A-461D and one or more caches 462A-462D. The core may include various other components for executing instructions and processing data, which are not illustrated to avoid obscuring the basic principles of the present invention (e.g., instruction fetch unit, branch prediction unit, decoder, execution unit, reorder buffer, etc.). The caches 462A-462D may include level 1 (L1) and level 2 (L2) caches. In addition, one or more shared caches 426 may be included in the cache hierarchy and shared by multiple groups of cores 460A-460D. For example, one embodiment of the processor 407 includes 24 cores, each core having its own L1 cache, 12 shared L2 caches, and 12 shared L3 caches. In this embodiment, one of the L2 and L3 caches is shared by two adjacent cores. Processor 407 and graphics accelerator integrated module 446 are connected to system memory 441, which may include processor memory 401-402

[0082] Coherence is maintained for data and instructions stored in the various caches 462A-462D, 456, and the system memory 441 via inter-core communications over the coherence bus 464. For example, each cache may have cache coherence logic / circuitry associated therewith to communicate over the coherence bus 464 in response to detecting a read or write to a particular cache line. In one implementation, a cache snooping protocol is implemented on the coherence bus 464 to snoop cache accesses. Cache snooping / coherence techniques are well known to those skilled in the art and are not described in detail herein to avoid obscuring the underlying principles of the present invention.

[0083] In one embodiment, the proxy circuit 425 communicatively couples the graphics acceleration module 446 to the coherence bus 464, allowing the graphics acceleration module 446 to participate in the cache coherence protocol as a peer of the core. In particular, the interface 435 provides connectivity to the proxy circuit 425 via a high-speed link 440 (e.g., a PCIe bus, NVLink, etc.), and the interface 437 connects the graphics acceleration module 446 to the link 440.

[0084] In one implementation, the accelerator integrated circuit 436 provides cache management, memory access, context management, and interrupt management services on behalf of the multiple graphics processing engines 431, 432, N of the graphics acceleration module 446. The graphics processing engines 431, 432, N may each include an independent graphics processing unit (GPU). Alternatively, the graphics processing engines 431, 432, N may include different types of graphics processing engines within the GPU, such as a graphics execution unit, a media processing engine (e.g., a video encoder / decoder), a sampler, and a blit engine. In other words, the graphics acceleration module may be a GPU having multiple graphics processing engines 431-432, N or the graphics processing engines 431-432, N may be individual GPUs integrated on a common package, line card, or chip.

[0085] In one embodiment, the accelerator integrated circuit 436 includes a memory management unit (MMU) 439 for performing various memory management functions such as virtual to physical memory translation (also known as effective to real memory translation) and a memory access protocol for accessing the system memory 441. The MMU 439 may also include a translation lookaside buffer (TLB) (not shown) for caching virtual / effective to physical / real address translations. In one implementation, the cache 438 stores commands and data for efficient access by the graphics processing engines 431-432, N. In one embodiment, the data stored in the cache 438 and the graphics memory 433-434, N is kept consistent with the core caches 462A-462D, 456 and the system memory 411. As mentioned, this may be accomplished via proxy circuitry 425 participating in cache coherence mechanisms on behalf of cache 438 and memories 433-434, N (e.g., sending updates to cache 438 involving modifications / accesses of cache lines on processor caches 462A-462D, 456 and receiving updates from cache 438).

[0086] A set of registers 445 stores context data for threads executed by the graphics processing engines 431-432, N, and context management circuitry 448 manages thread contexts. For example, context management circuitry 448 may perform save and restore operations to save and restore contexts of various threads during context switches (e.g., where a first thread is saved and a second thread is stored so that the second thread can be executed by the graphics processing engine). For example, upon context switch, context management circuitry 448 may store current register values ​​to a designated area in memory (e.g., identified by a context pointer). It may then restore the register values ​​upon returning to context. In one embodiment, interrupt management circuitry 447 receives and processes interrupts received from system devices.

[0087] In one implementation, the virtual / effective address from the graphics processing engine 431 is converted by the MMU 439 to an actual / physical address in the system memory 411. One embodiment of the accelerator integrated circuit 436 supports multiple (e.g., 4, 8, 16) graphics accelerator modules 446 and / or other accelerator devices. The graphics accelerator module 446 may be dedicated to a single application executed on the processor 407, or may be shared between multiple applications. In one embodiment, a virtualized graphics execution environment is presented in which the resources of the graphics processing engines 431-432, N are shared with multiple applications or virtual machines (VMs). The resources may be subdivided into "slices" assigned to different VMs and / or applications based on the processing requirements and priorities associated with the VMs and / or applications.

[0088] Thus, the accelerator integrated circuit acts as a bridge to the system for the graphics acceleration module 446 and provides address translation and system memory cache services. In addition, the accelerator integrated circuit 436 can provide virtualization facilities for the host processor to manage virtualization of the graphics processing engine, interrupts, and memory management.

[0089] Because the hardware resources of the graphics processing engines 431-432, N are explicitly mapped to the actual address space seen by the host processor 407, any host processor can directly address these resources using effective address values. In one embodiment, one function of the accelerator integrated circuit 436 is the physical separation of the graphics processing engines 431-432, N so that they appear to the system as independent units.

[0090] As mentioned, in the illustrated embodiment, one or more graphics memories 433-434, M are respectively coupled to each of the graphics processing engines 431-432, N. The graphics memories 433-434, M store instructions and data processed by each of the graphics processing engines 431-432, N. The graphics memories 433-434, M may be volatile memories such as DRAM (including stacked DRAM), GDDR memories (e.g., GDDR5, GDDR6), or HBM and / or may be non-volatile memories such as 3DXPoint or Nano-Ram.

[0091] In one embodiment, to reduce data traffic on link 440, biasing techniques are used to ensure that data stored in graphics memory 433-434, M is data that will be used most frequently by graphics processing engines 431-432, N and is preferably not used (at least not frequently) by cores 460A-460D. Similarly, the biasing mechanism attempts to keep data needed by a core (and preferably not graphics processing engines 431-432, N) within the core's cache 462A-462D, 456 and system memory 411.

[0092] Figure 4C The figure shows another embodiment in which an accelerator integrated circuit 436 is integrated into the processor 407. In this embodiment, the graphics processing engines 431-432, N communicate directly with the accelerator integrated circuit 436 via the high-speed link 440 via the interface 437 and the interface 435 (which may also utilize any form of bus or interface protocol). The accelerator integrated circuit 436 can perform operations related to Figure 4B The same operations are described, but assumed to be closer to the coherency bus 462 and caches 462A-462D, 426, potentially at higher throughput.

[0093] One embodiment supports different programming models including a dedicated process programming model (without graphics acceleration module virtualization) and a shared programming model (with virtualization). The latter may include a programming model controlled by the accelerator integrated circuit 436 and a programming model controlled by the graphics acceleration module 446.

[0094] In one embodiment of a dedicated process model, graphics processing engines 431-432, N are dedicated to a single application or process under a single operating system. A single application can funnel other application requests to graphics engines 431-432, N, thereby providing virtualization within a VM / partition.

[0095] In a dedicated process programming model, graphics processing engines 431-432, N can be shared by multiple VM / application partitions. The shared model requires the hypervisor to virtualize the graphics processing engines 431-432, N to allow each operating system to access. For a single partition system without a hypervisor, graphics processing engines 431-432, N are owned by the operating system. In both cases, the operating system can virtualize the graphics processing engines 431-432, N to provide access to each process or application.

[0096] For the shared programming model, the graphics acceleration module 446 or the individual graphics processing engines 431-432, N use a process handle to select a process element. In one embodiment, the process elements are stored in the system memory 411 and can be addressed using the effective address to real address conversion techniques described herein. The process handle can be an implementation-specific value provided to the host process when registering its context with the graphics processing engine 431-432, N (i.e., calling the system software to add the process element to the process element linked list). The lower 16 bits of the process handle can be the offset of the process element within the process element linked list.

[0097] Figure 4D The figure shows an exemplary accelerator integrated slice 490. As used herein, a "slice" includes a specified portion of the processing resources of the accelerator integrated circuit 436. The application effective address space 482 within the system memory 411 stores process elements 483. In one embodiment, in response to a GPU dispatch 481 from an application 480 executed on the processor 407, the process element 483 is stored. The process element 483 contains a process state for the corresponding application 480. The work descriptor (WD) 484 contained in the process element 483 can be a single job requested by the application or can contain a pointer to a job queue. In the latter case, WD 484 is a pointer to a job request queue in the application address space 482.

[0098] Graphics acceleration module 446 and / or individual graphics processing engines 431-432, N may be shared by all or a subset of processes in the system. Embodiments of the present invention include infrastructure for establishing process state and sending WD 484 to graphics acceleration module 446 to start a job in a virtual environment.

[0099] In one implementation, the dedicated process programming model is implementation specific. In this model, a single process owns the graphics acceleration module 446 or individual graphics processing engine 431. Since the graphics acceleration module 446 is owned by a single process, at the time when the graphics acceleration module 446 is assigned, the hypervisor initializes the accelerator integrated circuit 436 for the owned partition and the operating system initializes the accelerator integrated circuit 436 for the owned process.

[0100] In operation, the WD acquisition unit 491 in the accelerator integrated slice 490 acquires the next WD 484, which includes an indication of the work to be performed by one of the graphics processing engines of the graphics acceleration module 446. The data from the WD 484 can be stored in the register 445 and used by the MMU 439, the interrupt management circuit 447 and / or the context management circuit 446 as shown. For example, one embodiment of the MMU 439 includes a segment / page walk circuit for accessing the segment / page table 486 within the OS virtual address space 485. The interrupt management circuit 447 can handle the interrupt event 492 received from the graphics acceleration module 446. When performing graphics operations, the effective address 493 generated by the graphics processing engine 431-432, N is converted to an actual address by the MMU 439.

[0101] In one embodiment, the same set of registers 445 is replicated for each graphics processing engine 431-432, N and / or graphics acceleration module 446 and can be initialized by a hypervisor or operating system. Each of these replicated registers can be included in an accelerator integrated slice 490. Exemplary registers that can be initialized by a hypervisor are shown in Table 1.

[0102] Table 1 - Registers initialized by the hypervisor

[0103] 1 Slice Control Register 2 Real Address (RA) Dispatch Process Area Pointer 3 Permission Mask Override Register 4 Interrupt vector table entry offset 5 Interrupt vector table entry restrictions 6 Status Register 7 Logical Partition ID 8 Real Address (RA) Hypervisor Accelerator Utilization Record Pointer 9 Storage Description Register

[0104] Example registers that may be initialized by the operating system are shown in Table 2.

[0105] Table 2 - Registers initialized by the operating system

[0106] 1 Process and thread identities 2 Effective Address (EA) context save / restore pointer 3 Virtual Address (VA) Accelerator Utilization Record Pointer 4 Virtual Address (VA) stores the segment table pointer 5 Permission masking 6 Job Descriptor

[0107] In one embodiment, each WD 484 is specific to a particular graphics acceleration module 446 and / or graphics processing engine 431-432, N. It contains all the information needed by the graphics processing engine 431-432, N to do its work or it can be a pointer to a memory location where the application has set up a command queue for work to be done.

[0108] Figure 4E The figure shows additional details for one embodiment of the sharing model. This embodiment includes a hypervisor real address space 498 in which a process element list 499 is stored. The hypervisor real address space 498 is accessible via a hypervisor 496, which virtualizes a graphics acceleration module engine for an operating system 495.

[0109] The shared programming model allows all processes or a subset of processes from all partitions or a subset of partitions in the system to use the graphics acceleration module 446. There are two programming models where the graphics acceleration module 446 is shared by multiple processes and partitions: time-sliced ​​sharing and graphics-oriented sharing.

[0110] In this model, the hypervisor 496 owns the graphics acceleration module 446 and makes its functionality available to all operating systems 495. In order for the graphics acceleration module 446 to support virtualization of the hypervisor 496, the graphics acceleration module 446 may follow the following requirements: 1) The application's job request must be autonomous (i.e., no state needs to be maintained between jobs), or the graphics acceleration module 446 must provide a context save and restore mechanism. 2) The application's job request is guaranteed by the graphics acceleration module 446 to be completed within a specified amount of time, including any conversion errors, or the graphics acceleration module 446 provides the ability to preempt job processing. 3) When operating in a directional sharing programming model, the graphics acceleration module 446 must ensure fairness between processes.

[0111] In one embodiment, for the shared model, the application 480 is required to make an operating system 495 system call with a graphics acceleration module 446 type, a work descriptor (WD), an authority mask register (AMR) value, and a context save / restore region pointer (CSRP). The graphics acceleration module 446 type describes the target acceleration function for the system call. The graphics acceleration module 446 type can be a system-specific value. The WD is formatted specifically for the graphics acceleration module 446 and can take the form of a graphics acceleration module 446 command, an effective address pointer to a user-defined structure, an effective address pointer to a command queue, or any other data structure used to describe the work to be done by the graphics acceleration module 446. In one embodiment, the AMR value is the AMR state for the current process. The value passed to the operating system is similar to the application that sets the AMR. If the implementation of the accelerator integrated circuit 436 and the graphics acceleration module 446 does not support the user authority mask override register (UAMOR), the operating system can apply the current UAMOR value to the AMR value before passing the AMR in the hypervisor call. The hypervisor 496 may optionally apply the current privilege mask overlay register (AMOR) value before placing the AMR into the process element 483. In one embodiment, the CSRP is one of the registers 445 for the graphics acceleration module 446 that contains the effective address of a region in the application address space 482 to save and restore context state. This pointer is optional if state does not need to be saved between jobs or when a job is preempted. The context save / restore area may be fixed system memory.

[0112] Upon receiving the system call, the operating system 495 can verify that the application 480 has been registered and authorized to use the graphics acceleration module 446. The operating system 495 then calls the hypervisor 496 with the information shown in Table 3.

[0113] Table 3 - OS to Hypervisor call parameters

[0114] 1 Job Descriptor (WD) 2 Authority Mask Register (AMR) value (may be masked). 3 Effective Address (EA) Context Save / Restore Region Pointer (CSRP) 4 Process ID (PID) and optional thread ID (TID) 5 Virtual Address (VA) Accelerator Utilization Record Pointer (AURP) 6 Virtual address of the storage segment table pointer (SSTP) 7 Logical Interrupt Service Number (LISN)

[0115] Upon receiving the hypervisor call, the hypervisor 496 verifies that the operating system 495 has registered and is authorized to use the graphics acceleration module 446. The hypervisor 496 then places the process element 483 into a linked list of process elements for the corresponding type of graphics acceleration module 446. The process element may include the information shown in Table 4.

[0116] Table 4 - Process element information

[0117] 1 Job Descriptor (WD) 2 Authority Mask Register (AMR) value (may be masked). 3 Effective Address (EA) Context Save / Restore Region Pointer (CSRP) 4 Process ID (PID) and optional thread ID (TID) 5 Virtual Address (VA) Accelerator Utilization Record Pointer (AURP) 6 Virtual address of the storage segment table pointer (SSTP) 7 Logical Interrupt Service Number (LISN) 8 The interrupt vector table is derived from the hypervisor call parameters. 9 Status Register (SR) Value 10 Logical Partition ID (LPID) 11 Real Address (RA) Hypervisor Accelerator Utilization Record Pointer 12 Storage Descriptor Register (SDR)

[0118] In one embodiment, the hypervisor initializes the plurality of accelerator integrated slice 490 registers 445 .

[0119] like Figure 4F As illustrated in , one embodiment of the present invention employs a unified memory addressable via a common virtual memory address space for accessing physical processor memory 401-402 and GPU memory 420-423. In this implementation, operations executed on GPUs 410-413 utilize the same virtual / effective memory address space to access processor memory 401-402, and vice versa, thereby simplifying programmability. In one embodiment, a first portion of the virtual / effective address space is allocated to processor memory 401, a second portion is allocated to second processor memory 402, a third portion is allocated to GPU memory 420, and so on. The entire virtual / effective memory space (sometimes referred to as the effective address space) is thereby distributed across each processor memory 401-402 and GPU memory 420-423, allowing any processor or GPU to access any physical memory - having a virtual address mapped to that memory.

[0120] In one embodiment, bias / coherency management circuitry 494A-494E within one or more MMUs 439A-439E ensures cache coherency between the cache of a host processor (e.g., 405) and GPUs 410-413 and implements a biasing technique that indicates where certain types of data should be stored. Figure 4F4. Multiple instances of bias / consistency management circuits 494A-494E are illustrated in , but the bias / consistency circuits may be implemented within an MMU of one or more host processors 405 and / or within an accelerator integrated circuit 436.

[0121] One embodiment allows the GPU-attached memory 420-423 to be mapped as part of the system memory and accessed using shared virtual memory (SVM) technology, but without suffering from the typical performance drawbacks associated with full system cache coherence. The ability to access the GPU-attached memory 420-423 as system memory without heavy cache coherence overhead provides a beneficial operating environment for GPU offload. This arrangement allows the host processor 405 software to set up operands and access calculation results without the overhead of traditional I / O DMA data copies. These traditional copies involve driver calls, interrupts, and memory mapped I / O (MMIO) accesses, which are all inefficient relative to simple memory accesses. At the same time, the ability to access the GPU-attached memory 420-423 without cache coherence overhead may be critical to the execution time of the offloaded calculation. For example, in the case of a large number of streaming write memory services, the cache coherence overhead can significantly reduce the effective write bandwidth seen by the GPU 410-413. The efficiency of operand set-up, the efficiency of result access, and the efficiency of GPU calculation all play a role in determining the effectiveness of GPU offload.

[0122] In one implementation, the selection between GPU bias and host processor bias is driven by a bias tracker data structure. For example, a bias table may be used, which may be a page granular structure comprising 1 or 2 bits per GPU-attached memory page (i.e., controlled at the granularity of a memory page). The bias table may be implemented in the stolen memory range of one or more GPU-attached memories 420-423 - with or without a bias cache in the GPUs 410-413 (e.g., to cache frequently / recently used bias table entries). Alternatively, the entire bias table may be maintained within the GPU.

[0123] In one implementation, the bias table entry associated with each access to the GPU-attached memory 420-423 is accessed before the GPU memory is actually accessed, resulting in the following operations. First, local requests from GPUs 410-413 to find their pages in the GPU bias are forwarded directly to the corresponding GPU memory 420-423. Local requests from GPUs to find their pages in the host bias are forwarded to processor 405 (e.g., via a high-speed link as discussed above). In one embodiment, requests from processor 405 to find the requested page in the host processor bias complete the request like a normal memory read. Alternatively, requests directed to GPU bias pages can be forwarded to GPUs 410-413. If the GPU is not currently using the page, the GPU can then transfer the page to the host processor bias.

[0124] The bias state of a page can be changed by a software-based mechanism, a hardware-assisted software-based mechanism, or - for a limited set of cases - a purely hardware-based mechanism.

[0125] One mechanism for changing the bias state employs an API call (e.g., OpenCL), which in turn calls the GPU's device driver, which in turn sends a message (or queues a command descriptor) to the GPU to direct it to change the bias state, and for some transfers, performs a cache flush operation in the host. The cache flush operation is necessary for a transfer from the host processor 405 bias to the GPU bias, but not necessary for the reverse transfer.

[0126] In one embodiment, cache coherency is maintained by temporarily rendering GPU-biased pages that are not cacheable by host processor 405. To access these pages, processor 405 may request access from GPU 410, which may or may not immediately grant access, depending on the implementation. Therefore, to reduce communication between processor 405 and GPU 410, it is advantageous to ensure that GPU-biased pages are pages that are needed by the GPU but not by the host processor 405, and vice versa.

[0127] Graphics processing pipeline

[0128] Figure 5 The figure shows a graphics processing pipeline 500 according to one embodiment. In one embodiment, a graphics processor can implement the illustrated graphics processing pipeline 500. The graphics processor can be included in the parallel processing subsystem described herein, such as the parallel processor 200 of FIG. 2, which, in one embodiment, is Figure 12 . As described herein, various parallel processing systems may implement the graphics processing pipeline 500 via one or more instances of a parallel processing unit (e.g., parallel processing unit 202 of FIG. 2 ). For example, a shader unit (e.g., graphics multiprocessor 234 of FIG. 3 ) may be configured to perform one or more functions of a vertex processing unit 504, a tessellation control processing unit 508, a tessellation evaluation processing unit 512, a geometry processing unit 516, and a fragment / pixel processing unit 524. The functions of the data assembler 502, the primitive assemblers 506, 514, 518, the tessellation unit 510, the rasterizer 522, and the raster operation unit 526 may also be performed by other processing engines within a processing cluster (e.g., processing cluster 214 of FIG. 3 ) and a corresponding partition unit (e.g., partition units 220A-220N of FIG. 2 ). The graphics processing pipeline 500 may also be implemented using dedicated processing units for one or more functions. In one embodiment, one or more portions of graphics processing pipeline 500 may be executed by parallel processing logic within a general purpose processor (e.g., a CPU). In one embodiment, one or more portions of graphics processing pipeline 500 may access on-chip memory (e.g., parallel processor memory 222 in FIG. 2 ) via memory interface 528 , which may be an example of memory interface 218 in FIG. 2 .

[0129] In one embodiment, data assembler 502 is a processing unit that collects vertex data for surfaces and primitives. Data assembler 502 then outputs the vertex data including vertex attributes to vertex processing unit 504. Vertex processing unit 504 is a programmable execution unit that executes vertex shader programs, lighting, and transforming vertex data specified by vertex shader programs. Vertex processing unit 504 reads data stored in cache, local or system memory for use in processing vertex data, and can be programmed to transform vertex data from an object-based coordinate representation to a world space coordinate space or a normalized device coordinate space.

[0130] A first instance of primitive assembler 506 receives vertex attributes from vertex processing unit 504. Primitive assembler 506 reads the stored vertex attributes as needed and builds graphics primitives for processing by tessellation control processing unit 508. Graphics primitives include triangles, line segments, points, patches, etc., as supported by various graphics processing application programming interfaces (APIs).

[0131] The tessellation control processing unit 508 treats the input vertices as control points for the geometric patch. The control points are transformed from an input representation from the patch (e.g., a basis for the patch) to a representation suitable for use in a surface evaluation performed by the tessellation evaluation processing unit 512. The tessellation control processing unit 508 may also calculate tessellation factors for the edges of the geometric patch. The tessellation factors apply to a single edge and quantify the viewpoint-dependent level of detail associated with the edge. The tessellation unit 510 is configured to receive the tessellation factors for the edges of the patch and tessellate the patch into a plurality of geometric primitives, such as line, triangle, or quadrilateral primitives, which are transmitted to the tessellation evaluation processing unit 512. The tessellation evaluation processing unit 512 operates on the parameterized coordinates of the tessellated patch to generate a surface representation and vertex attributes for each vertex associated with the geometric primitive.

[0132] A second instance of primitive assembler 514 receives vertex attributes from tessellation evaluation processing unit 512, reads stored vertex attributes as needed, and constructs graphics primitives for processing by geometry processing unit 516. Geometry processing unit 516 is a programmable execution unit that executes geometry shader programs to transform graphics primitives specified by geometry shader programs received from primitive assembler 514. In one embodiment, geometry processing unit 516 is programmed to tessellate the graphics primitives into one or more new graphics primitives and calculate parameters for rasterizing the new graphics primitives.

[0133] In some embodiments, the geometry processing unit 516 may add or delete elements in the geometry stream. The geometry processing unit 516 outputs parameters and vertices specifying new graphics primitives to the primitive assembler 518. The primitive assembler 518 receives the parameters and vertices from the geometry processing unit 516 and constructs graphics primitives for processing by the viewport scaling, culling, and clipping unit 520. The geometry processing unit 516 reads data stored in the parallel processor memory or the system memory for use in processing the geometry data. The viewport scaling, culling, and clipping unit 520 performs clipping, culling, and viewport scaling, and outputs the processed graphics primitives to the rasterizer 522.

[0134] The rasterizer 522 may perform depth culling and other depth-based optimizations. The rasterizer 522 also performs scan conversion on new graphics primitives to generate fragments and outputs these fragments and associated coverage data to the fragment / pixel processing unit 524. The fragment / pixel processing unit 524 is a programmable execution unit that is configured to execute a fragment shader program or a pixel shader program. The fragment / pixel processing unit 524 transforms fragments or pixels received from the rasterizer 522 as specified by the fragment or pixel shader program. For example, the fragment / pixel processing unit 524 may be programmed to perform operations including but not limited to texture mapping, shading, blending, texture correction, and perspective correction to produce shaded fragments or pixels that are output to the raster operation unit 526. The fragment / pixel processing unit 524 may read data stored in a parallel processor memory or system memory for use in processing fragment data. The fragment or pixel shader program may be configured to shade at a sampling, pixel, tile, or other granularity depending on the sampling rate configured for the processing unit.

[0135] Raster operations unit 526 is a processing unit that performs raster operations including but not limited to stencil printing, z-testing, blending, etc., and outputs pixel data as processed graphics data for storage in graphics memory (e.g., parallel processor memory 222 in FIG. 2 and / or as Figure 1 The raster operations unit 526 may be configured to compress the z or color data written to the memory and to decompress the z or color data read from the memory.

[0136] Region-based processing

[0137] Now go to Fig. 6A, a high dynamic range (HDR) image 600 (e.g., a still image, a video frame) is shown. The HDR image 600 may also be referred to as an enhanced dynamic range (EDR) and / or wide dynamic range (WDR) image, and the HDR image 600 may typically be part of a visual content presented to a user in conjunction with a three-dimensional (3D) game, a virtual reality (VR) environment, an augmented reality (AR) environment, and the like. For example, the HDR image 600 may be transmitted from a source device to a head mounted display (HMD) system worn by a user via a wireless link (e.g., Bluetooth, WiFi) to provide a real-time, immersive VR experience. In another example, the HDR image 600 may be transmitted to a fixed display system that the user is watching via a wired link (e.g., Universal Serial Bus / USB) to replay a movie. The image 600 may be considered to be formatted in HDR to the extent that it reproduces a larger dynamic luminance range than is possible with standard digital imaging or photography techniques. Therefore, the HDR image 600 may have a brightness range similar to that experienced by the human visual system, which is constantly adjusted to accommodate the wide brightness range present in the environment. The brain can continuously interpret this information, allowing the user / viewer to view under a wide range of light conditions.

[0138] In the illustrated example, the HDR image 600 is divided into a plurality of regions by a source device, wherein the brightness level can be automatically measured for each region. For example, a first region 602 and a second region 604 can be determined to have a relatively high brightness level, while one or more remaining regions 606 can be determined to have a relatively low brightness level. As will be discussed in more detail, regions 602, 604, 606 can be independently encoded (e.g., compressed) before being transmitted over a link based on their respective brightness levels. More specifically, brighter regions such as regions 602, 604 can receive less encoding / compression in order to retain HDR content. In contrast, darker regions such as the remaining region 606 can receive more encoding / compression in order to reduce link bandwidth consumption and / or power consumption. It is particularly noteworthy that due to the lack of HDR content in the remaining region 606, increasing the amount of encoding in the relatively dark remaining region 606 may have little or imperceptible effect on image quality.

[0139] Figure 6BAnother HDR image 620 is shown, which can also be part of the visual content presented to the user in a 3D game, VR environment, AR environment, etc. In the illustrated example, the HDR image is divided into a foreground area 622 and a background area 624 by the source device. Areas 622, 624 can be independently encoded before transmission on the link based on their depth in the scene (e.g., foreground / background status). More specifically, closer areas such as the foreground area 622 can receive less encoding / compression to ensure the visual quality of the more important parts of the scene. In contrast, farther areas such as the background area 624 can receive more encoding / compression to reduce link bandwidth and / or power consumption.

[0140] In fact, it can be combined Fig. 6A 624. For example, even if relatively high brightness is detected in background region 624, background region 624 may be encoded / compressed at a higher level. Similarly, even if relatively low brightness is detected in foreground region 622, foreground region 622 may be encoded / compressed at a lower level.

[0141] Figure 7 A processing architecture 700 using region-based processing as described herein is shown. In the illustrated example, a device driver 702 receives an HDR image 704 (e.g., a still image, a video frame), divides the HDR image 704 into a plurality of regions, and determines a brightness level of the HDR image 704 on a per-region basis. The device driver 702 may also determine whether each region is a foreground region and / or a background region. The illustrated device driver 702 also sends region-specific encoding amounts 706 to a media pipeline 708 (e.g., of a graphics processor not shown), which uses a codec 710 to encode the region of the HDR image 704 according to the region-specific encoding amounts 706. The device driver 702 may also trigger one or more graphics processor interrupts to switch the codec 710 between encoding schemes. The encoded data may be sent to a transmitter 712, which outputs the encoded data to a wireless display 714 (e.g., including a receiver, not shown). Alternatively, the encoded data may be output to a non-wireless display (not shown) via a wired link. In either case, the illustrated architecture 700 can reduce link bandwidth consumption, power consumption, and cost while maintaining image quality from a user perspective (e.g., human visual system). The operations of the device driver 702 can be performed by one or more other components such as, for example, a display pipeline (e.g., including a local adaptive contrast enhancement / LACE component, not shown).

[0142] Fig. 8AA method 800 of operating a semiconductor packaging device is shown. The method 800 may be implemented as one or more modules in a set of logic instructions stored in a non-transitory machine or computer readable storage medium such as a random access memory (RAM), a read only memory (ROM), a programmable ROM (PROM), firmware, flash memory, etc., in configurable logic such as, for example, a programmable logic array (PLA), a field programmable gate array (FPGA), a complex programmable logic device (CPLD), in fixed function hardware logic using circuit technology such as, for example, an application specific integrated circuit (ASIC), complementary metal oxide semiconductor (CMOS), or transistor-transistor logic (TTL) technology, or any combination thereof.

[0143] For example, computer program code for performing the operations shown in method 800 may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as JAVA, SMALLTALK, C++, etc., and traditional procedural programming languages ​​such as the "C" programming language or similar programming languages. In addition, the logic instructions may include assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, state setting data, configuration data for integrated circuits, state information that personalizes electronic circuits and / or other structural components native to hardware (e.g., main processors, central processing units / CPUs, microcontrollers, etc.).

[0144] The illustrated configurable logic block 802 is provided for dividing the HDR image into a plurality of regions. Block 802 may include retrieving partition data from a control register or other suitable storage location, generating partition data on a per-image / frame basis or for a plurality of images / frames, and the like. The spacing / size of the partitions may vary from case to case. In addition, the brightness level of the HDR image may be determined on a per-region basis at block 804. Block 804 may include generating a brightness histogram for the HDR image. More specifically, a brightness bin may be defined, wherein the percentage of the region falling into each bin may be determined. For example, 75% of the first region may fall into a brightness bin of X candela per square meter (X cd / m2), and 25% of the first region may fall into a brightness bin of Y cd / m2, where Y>X. In contrast, 5% of the second region may fall into the X brightness bin, and 95% of the second region may fall into the Y brightness bin. In such an example, the first region may be considered to contain HDR content, while the second region may be considered to not contain HDR content. Illustrated block 806 selects an amount of encoding for each of the plurality of regions based on the brightness level on a per region basis.

[0145] Figure 8BA method 820 for selecting the amount of encoding based on the brightness level is shown. The method 820 can therefore be incorporated into the block 806 ( Fig. 8A ). This can typically be done in, for example, architecture 700 ( Figure 7 ) processing architecture. More specifically, the method 820 may be implemented as one or more modules in a set of logic instructions stored in a non-transitory machine or computer readable storage medium such as RAM, ROM, PROM, firmware, flash memory, etc., in configurable logic such as, for example, PLA, FPGA, CPLD, in fixed-function hardware logic using circuit technology such as, for example, ASIC, CMOS or TTL technology, or any combination thereof.

[0146] The illustrated processing block 822 may be provided for initializing a first threshold and a second threshold, wherein the second threshold is greater than or equal to the first threshold. At block 824, it may be determined whether the brightness level of the area in question exceeds the second threshold. For example, the brightness level may include a brightness bin with a highest percentage, a weighted average of brightness bins, and the like. If the second threshold is exceeded, block 826 may reduce the amount of coding, wherein reducing the amount of coding reduces image compression (e.g., and subsequently increases image quality). Block 826 may include selecting a coding scheme (e.g., H.264, H.265, etc.) and / or a quantization parameter (QP) that results in the selected amount of coding. Thus, the reduction may be based on available quantization levels and / or other coding constraints. The illustrated block 828 encodes the area with the selected amount of coding. In one example, block 828 includes instructing the codec to encode the area.

[0147] If it is determined at block 824 that the second threshold has not been exceeded, block 830 may be provided for determining whether the brightness level (e.g., the brightness bin with the highest percentage, the weighted average of the brightness bins, etc.) has not exceeded the first threshold. If the brightness level does not exceed the first threshold, the illustrated block 832 increases the amount of code, which increases image compression. Increasing image compression may also reduce image quality (e.g., if lossy compression is used). Block 832 may also include selecting a coding scheme and / or QP that results in a selected amount of code, wherein the increase may be based on available quantization levels and / or other coding constraints. Once the amount of code is increased, the illustrated block 828 encodes the region with the selected amount of code. In addition, block 828 may encode a first region of a plurality of regions with a first amount of code, and encode a second region of a plurality of regions with a second amount of code. Initializing the second threshold to a value greater than the value of the first threshold may provide a hysteresis-type effect that eliminates continuous switching between high brightness control and low brightness control.

[0148] Figure 8CA method 840 for selecting the amount of encoding for the background and foreground regions of an HDR image is shown. The method 840 can thus be used in conjunction with, for example, the method 820 already discussed ( Figure 8B ) are merged into the already discussed block 806 ( Fig. 8A More specifically, method 840 may be implemented as one or more modules in a set of logic instructions stored in a non-transitory machine or computer readable storage medium such as RAM, ROM, PROM, firmware, flash memory, etc., in configurable logic such as, for example, PLA, FPGA, CPLD, in fixed function hardware logic using circuit technology such as, for example, ASIC, CMOS or TTL technology, or any combination thereof.

[0149] The illustrated processing block 842 provides for detecting a foreground region among a plurality of regions. Depending on the circumstances, the determination of block 842 may be made based on operating system (OS) information (e.g., focus region "hints", eye tracking data, etc.) and / or other information. The illustrated block 844 reduces the amount of code in response to detecting the foreground region, wherein reducing the amount of code reduces image compression (e.g., and in turn increases image quality). Once the amount of code is reduced, block 850 may encode the region at the selected amount of code. In one example, block 850 includes instructing a codec to encode the region.

[0150] If no foreground region is detected at block 842, it may be determined at block 846 whether the region in question is a background region. If so, block 848 may increase the amount of code, wherein increasing the amount of code increases image compression. As already noted, increasing image compression may also reduce image quality (e.g., if lossy compression is used). In this regard, increasing the amount of code may have a negligible effect on perceived image quality because the region is in the background (e.g., not the center of focus). Once the amount of code is increased, the illustrated block 850 encodes the region at the selected amount of code.

[0151] Fig. 9A performance enhanced computing system 900 is shown. In the illustrated example, a host processor 902 includes an integrated memory controller (IMC) 904 that communicates with a system memory 906 (e.g., DRAM). The host processor 902 may be coupled to a graphics processor 908 and an input / output (IO) module 910 (e.g., via a peripheral component interconnect / PCI bus). The IO module 910 may be coupled to a network controller 912 (e.g., wireless and / or wired), a display 914 (e.g., a fixed or head-mounted liquid crystal display / LCD, a light emitting diode / LED display, etc., to visually present a three-dimensional / 3D scene), and a mass storage 918 (e.g., flash memory, an optical disk, a solid state drive / SSD). The illustrated graphics processor 908 includes a media pipeline 920 and is coupled to a graphics memory 916 (e.g., a dedicated graphics RAM).

[0152] Media pipeline 920 may include a codec, such as, for example, codec 710 ( Figure 7 In addition, the system memory 906 and / or the mass storage 918 may include a set of instructions 922 (eg, device driver instructions) that, when executed by the host processor 902 and / or the graphics processor 908, cause the system 900 to implement the method 800 discussed above ( Fig. 8A )、Method 820( Figure 8B ) and / or Method 840 ( Figure 8C ). Thus, execution of instruction 922 may cause system 900 to divide the HDR image into a plurality of regions, determine a brightness level of the HDR image on a per-region basis, and select an encoding amount for each of the plurality of regions based on the brightness level on a per-region basis. Additionally, execution of instruction 922 may cause system 900 to selectively encode foreground and background regions.

[0153] Fig.10 A semiconductor package device 1000 (e.g., a chip) is shown including a substrate 1002 (e.g., silicon, sapphire, gallium arsenide) and logic 1004 (e.g., transistor arrays and other integrated circuit / IC components) coupled to the substrate 1002. The logic 1004, which may be implemented, for example, in configurable logic and / or fixed-function hardware logic, may generally implement the method 800 discussed above ( Fig. 8A )、Method 820( Figure 8B ) and / or Method 840 ( Figure 8C ). Thus, the logic 1004 may divide the HDR image into a plurality of regions, determine a brightness level of the HDR image on a per-region basis, and select an encoding amount for each of the plurality of regions based on the brightness level on a per-region basis. Additionally, the logic 1004 may selectively encode foreground and background regions.

[0154] Display Technology

[0155] Now go to Fig.11 , a performance-enhanced computing system 1100 is shown. In the illustrated example, a processor 1110 is coupled to a display 1120. The processor 1110 can generally produce an image to be displayed on an LCD panel 1150 of the display 1120. In one example, the processor 1110 includes a communication interface, such as, for example, a video graphics array (VGA), a display port (DP) interface, an embedded display port (eDP) interface, a high-definition multimedia interface (HDMI), a digital video interface (DVI), etc. The processor 1110 can be a graphics processor (e.g., a graphics processing unit / GPU) that processes graphics data and generates an image (e.g., a video frame, a still image) displayed on the LCD panel 1150. In addition, the processor 1110 can include one or more image processing pipelines that generate pixel data. The image processing pipeline can conform to the OPENGL architecture or other suitable architecture. In addition, the processor 1110 can be connected to a host processor (e.g., a central processing unit / CPU), where the host processor executes one or more device drivers that control the processor 1110 and / or interact with the processor 1110.

[0156] The illustrated display 1120 includes a timing controller (TCON) 1130 that can individually address different pixels in the LCD panel 1150 and update each individual pixel in the LCD panel 1150 every refresh cycle. In this regard, the LCD panel 1150 can include a plurality of liquid crystal elements, such as, for example, liquid crystals and integrated color filters. Each pixel of the LCD panel 1150 can include a triple liquid crystal element with red, green, and blue color filters, respectively. The LCD panel 1150 can arrange pixels in a two-dimensional (2D) array controlled via a row driver 1152 and a column driver 1154 to update the image displayed by the LCD panel 1150. Therefore, the TCON 1130 can drive the row driver 1152 and the column driver 1154 to address specific pixels of the LCD panel 1150. The TCON 1130 can also adjust the voltage provided to the liquid crystal element in the pixel to change the intensity of light passing through each of the three liquid crystal elements, and thus change the color of the pixel displayed on the surface of the LCD panel 1150.

[0157] The backlight 1160 may include a plurality of light emitting elements, such as, for example, light emitting diodes (LEDs), arranged at the edges of the LCD panel 1150. Thus, the light generated by the LEDs may be dispersed through the LCD panel 1150 by a diffuser (not shown). In another example, since each LED disperses light through one or more corresponding pixels of the LCD panel 1150 located in front of the LED, the LEDs are arranged in a 2D array directly behind the LCD panel 1150 in one configuration, which is sometimes referred to as direct backlighting. The light emitting elements may also include compact fluorescent lamps (CFLs) arranged along one or more edges of the LCD panel 1150. To eliminate multiple edges, the combination of edges may be varied to achieve selective illumination of an area, wherein less than the total set of lighting elements are used at a lower power.

[0158] The light emitting element may also include one or more sheets of electroluminescent material placed behind the LCD panel 1150. In this case, light from the surface of the sheet may be dispersed through the pixels of the LCD panel 1150. In addition, the sheet may be divided into multiple regions, such as quadrants, for example. In one example, each region is individually controlled to illuminate only a portion of the LCD panel 1150. Other backlighting solutions may also be used.

[0159] The illustrated display 1120 also includes a backlight controller (BLC) 1140 that provides voltage to the light emitting elements of the backlight 1160. For example, the BLC 1140 may include a pulse width modulation (PWM) driver (not shown) to generate a PWM signal that activates at least a portion of the light emitting elements of the backlight 1160. The duty cycle and frequency of the PWM signal may cause the light generated by the light emitting elements to dim. For example, a 100% duty cycle may correspond to a light emitting element being fully turned on, and a 0% duty cycle may correspond to a light emitting element being fully turned off. Therefore, intermediate duty cycles (e.g., 25%, 50%) typically cause the light emitting elements to be turned on for a portion of a cycle that is proportional to the percentage of the duty cycle. The cycle may be fast enough that the flickering of the light emitting elements is not noticeable to the human eye. In addition, the effect on the user may be that the level of light emitted by the backlight 1160 is lower than when the backlight 1160 is fully activated. The BLC 1140 may be separate from or incorporated into the TCON 1130.

[0160] Alternatively, an emissive display system may be used, where the LCD panel 1150 would be replaced by an emissive display panel (e.g., organic light emitting diode / OLED), the backlight 1160 would be omitted, and the row and column drivers 1152 and 1154 could be used to directly modulate the color and brightness of the pixels, respectively.

[0161] Display resolution based on distance

[0162] Fig. 12A A scenario is shown in which a user 1218 interacts with a data processing device 1200 that includes a display unit 1228. The display processing device 1200 may include, for example, a notebook computer, a desktop computer, a tablet computer, a convertible tablet computer, a mobile Internet device (MID), a personal digital assistant (PDA), a wearable device (e.g., a head mounted display / HMD), a media player, etc. or any combination thereof. The illustrated data processing device 1200 includes a processor 1224 (e.g., an embedded controller, a microcontroller, a host processor, a graphics processor) coupled to a memory 1222, which may include storage locations addressable by the processor 1224. As will be discussed in more detail, the distance sensor 1210 may enable a distance-based display resolution relative to the display unit 1228.

[0163] The illustrated memory 1222 includes display data 1226 to be rendered on a display unit 1228. In one example, the processor 1224 performs a data transformation on the display data 1226 before presenting the display data 1226 on the display unit 1228. The post-processing engine 1214 may be executed on the processor 1224 to receive the display data 1226 and the output of the distance sensor 1210. The post-processing engine 1214 may modify the display data 1226 to enhance readability of screen content on the display unit 1228, reduce power consumption in the data processing device 1200, etc., or any combination thereof.

[0164] In addition to the operating system 1212 and the applications 1220, the illustrated memory 1222 stores a display resolution setting 1216. The display resolution setting 1216 may specify the number of pixels of the display data 1226 to be presented on the display unit 1228 along the length dimension and the width dimension. If the display data 1226 generated by the application 1220 is not compatible with the format of the display unit 1228, the processor 1224 may configure the scaling of the display data 1226 to match the format of the display unit 1228. In this regard, the display resolution setting 1216 may be associated with and / or incorporated into configuration data defining other settings for the display unit 1228. Furthermore, the display resolution setting 1216 may be defined in terms of unit distance or area (e.g., pixels per inch / PPI) or other suitable parameters.

[0165] The application 1220 can generate a user interface, wherein the user 1218 can interact with the user interface to select a display resolution setting 1216 from one or more options provided through the user interface, input the display resolution setting 1216 as a request value, etc. Thus, the display data 1226 can be resized to fit the display resolution setting 1216 before being rendered on the display unit 1228.

[0166] The distance sensor 1210 may track the distance between the user 1218 and the display unit 1228, wherein the distance sensing may be triggered by a physical button associated with the data processing device 1200 / display unit 1228, by a user interface provided by the application 1220 and / or the loading of the operating system 1220, etc. For example, during booting of the data processing device 1200, the operating system 1212 may implement an automatic process to trigger distance sensing in the background or foreground. The distance sensing may be implemented periodically or continuously.

[0167] Fig. 12B An example of a distance sensing scenario is shown. In the illustrated example, the distance sensor 1210 uses a transceiver 1208 to transmit an electromagnetic beam 1202 in the direction of a user 1218. Thus, the transceiver 1202 can be positioned on a forward-facing surface of the data processing device 1200 ( Fig. 12A ). Electromagnetic beam 1202 may impact user 1218 and reflect / scatter from user 1218 as return electromagnetic beam 1204. Return electromagnetic beam 1204 may be processed by, for example, processor 1224 ( Fig. 12A ) and / or post-processing engine 1214 ( Fig. 12A ) analyzes to determine that the user 1218 is in contact with the display unit 1228 ( Fig. 12A ) between the two images 1206. The distance 1206 can be used to adjust the display resolution setting 1216.

[0168] Display Layer

[0169] Now go to Fig.13, a display system 1300 is shown in which cascaded display layers 1361, 1362, and 1363 are used to implement spatial / temporal super-resolution in a display accessory 1360. In the illustrated example, the processor 1310 provides original graphics data 1334 (e.g., video frames, still images) to the system 1300 via the bus 1320. The cascaded display program 1331 can be stored in the memory 1330, where the cascaded display program 1331 can be part of a display driver associated with the display accessory 1360. The illustrated memory 1330 also includes the original graphics data 1334 and the factored graphics data 1335. In one example, the cascaded display program 1331 includes a temporal factorization component 1332 and a spatial factorization component 1333. The temporal factorization component 1332 can perform temporal factorization calculations, and the spatial factorization component can perform spatial factorization calculations. The cascaded display program 1331 can derive factorized graphics data 1335 for presentation on each display layer 1361 , 1362 , and 1363 based on the user configuration and the original graphics data 1334 .

[0170] Display accessory 1360 may be implemented as an LCD (liquid crystal display) for use in, for example, head mounted display (HMD) applications. More particularly, display accessory 1360 may include a stack of LCD panel interface boards, lens attachments, and the like. Each panel may be operated at, for example, a native resolution of 1280×800 pixels and a 60 Hz refresh rate. Other native resolutions, refresh rates, display panel technologies, and / or layer configurations may be used.

[0171] Multiple display units

[0172] Fig.14 A graphical display system 1400 is shown that includes a set of display units 1430 (1430a-1430n) that can generally be used to output a wide screen (e.g., panoramic) presentation 1440 of coordinated content that includes a cohesive and structured topological form. In the illustrated example, a data processing device 1418 includes a processor 1415 that applies a logic function 1424 to hardware profile data 1402 received from the set of display units 1430 over a network 1420. Applying the logic function 1424 to the hardware profile data 1402 can create a set of automatic topology settings 1406 when the hardware profile data does not match a set of settings in a hardware profile lookup table 1412. The illustrated set of automatic topology settings 1406 is transmitted from the display processing device 1418 to the display unit 1430 over the network 1420.

[0173] The processor 1415 may perform and execute the logic function 1424 upon receiving the logic function 1424 from the display driver 1410. In this regard, the display driver 1410 may include an automatic topology module 1408 that automatically configures and constructs the topology of the display unit 1432 to create the presentation 1440. In one example, the display driver 1410 is a set of instructions that, when executed by the processor 1415, causes the data processing device 1418 to communicate with the display unit 1430, a video card, etc., and implement automatic topology generation operations.

[0174] Data processing device 1418 may include, for example, a server, a desktop computer, a notebook computer, a tablet computer, a convertible tablet computer, a MID, a PDA, a wearable device, a media player, and the like. Thus, display processing device 1418 may include hardware control module 1416, storage device 1414, random access memory (RAM, not shown), controller cards including one or more video controller cards, and the like. In one example, display unit 1430 is a flat panel display (e.g., liquid crystal, active matrix, plasma, etc.), HMD, video projection device, and the like that coordinate with each other to produce presentation 1440. In addition, presentation 1440 may be generated based on media files stored in storage device 1414, where the media files may include, for example, movies, video clips, animations, advertisements, and the like, or any combination thereof.

[0175] The term "topology" may be considered to be the number, scaling, shape, and / or other configuration parameters of the first display unit 1430a, the second display unit 1430b, the third display unit 1430n, and the like. Thus, the topology of the display unit 1430 may enable the presentation 1440 to be visually presented consistently, such that the various portions of the presentation 1440 are proportional to and compatible with the original dimensions and extent of the media played through the display unit 1430. Thus, the topology may constitute spatial relationships and / or geometric properties that are not affected by continuous changes in the shape or size of the content rendered in the presentation 1440. In one example, the automatic topology module 1408 includes a timing module 1426, a control module 1428, a signal monitoring module 1432, and a signal display module 1434. The timing module 1426 may designate a particular display unit in the set of display units 1430 as a sample display unit. In this case, the timing module 1426 may designate the remaining display units 1430 as additional display units. In one example, the timing module 1426 automatically sets the form factor to be compatible with the hardware profile data 1402 , where the rendering 1440 is automatically initiated by the graphics signal sequence 1422 .

[0176] In one example, the control module 1428 modifies the set of automatic topology settings 1406. In addition, the signal monitoring module 1432 can automatically monitor the graphic signal sequence 1422 and trigger the storage device 1414 to associate the set of automatic topology settings 1406 with the hardware profile lookup table 1412. In addition, the signal monitoring module 1432 can automatically detect changes in the set of display units 1430 according to a set of change criteria and automatically generate a new topology profile corresponding to the changes in the set of display units 1430. Therefore, the new topology profile can be applied to the set of display units 1430. If the graphic signal sequence 1422 does not meet the set of criteria, the signal monitoring module 1432 can also trigger the signal display module 1434 to reapply the set of automatic topology settings 1406. If the hardware profile data 1402 does not support the automatic topology display of the graphic signal sequence 1422, the data processing device 1418 can report an error and record the error in the error log 1413.

[0177] Cloud-assisted media delivery

[0178] Now go to Fig.15 , the cloud gaming system 1500 includes a client 1540 coupled to a server 1520 via a network 1510. The client 1540 may typically be a consumer of graphics (e.g., games, virtual reality / VR, augmented reality / AR) content that is hosted, processed, and rendered on the server 1520. The illustrated server 1520 may be scalable, having the ability to provide graphics content to multiple clients simultaneously (e.g., by utilizing parallel and shared processing and rendering resources). In one example, the scalability of the server 1520 is limited by the capacity of the network 1510. Therefore, there may be a certain threshold number of clients above which service to all clients is degraded.

[0179] In one example, the server 1520 includes a graphics processor (e.g., GPU) 1530, a host processor (e.g., CPU) 1524, and a network interface card (NIC) 1522. The NIC 1522 can receive requests for graphics content from a client 1540. The request from the client 1540 can cause the graphics content to be retrieved from a memory via an application executed on the host processor 1524. The host processor 1524 can perform high-level operations, such as, for example, determining the position, collision, and motion of objects in a given scene. Based on the high-level operations, the host processor 1524 can generate rendering commands that are combined with the scene data and executed by the graphics processor 1530. The rendering commands can cause the graphics processor 1530 to define scene geometry, shading, lighting, motion, textures, camera parameters, etc. for the scene for presentation via the client 1540.

[0180] More specifically, the illustrated graphics processor 1530 includes a graphics renderer 1532 that performs a rendering process according to rendering commands generated by the host processor 1524. The output of the graphics renderer 1532 may be a stream of native video frames that is provided to a frame capturer 1534. The illustrated frame capturer 1534 is coupled to an encoder 1536 that may compress / format the native video stream for transmission over the network 1510. The encoder 1536 may use a variety of video compression algorithms, such as, for example, the H.264 standard from the International Telecommunication Union Telecommunication Standardization Sector (ITUT), the MPEG4 Advanced Video Coding (AVC) standard from the International Organization for Standardization / International Electrotechnical Commission (ISO / IEC), and the like.

[0181] The illustrated client 1540 may be a desktop computer, a notebook computer, a tablet computer, a convertible tablet computer, a wearable device, a MID, a PDA, a media player, etc., which includes a NIC 1542 to receive the video stream transmitted from the server 1520. The NIC 1522 may include the basis of the physical layer and the software layer for the network interface in the client 1540 to facilitate communication over the network 1510. The client 1540 may also include a decoder 1544, which adopts the same formatting / compression scheme as the encoder 1536. Therefore, the decompressed video stream can be provided from the decoder 1544 to the video renderer 1546. The illustrated video renderer 1546 is coupled to a display 1548 that visually presents the graphical content.

[0182] As already mentioned, the graphical content may include gaming content. In this regard, the client 1540 may implement real-time interactive streaming, which involves collecting user input from the input device 1550 and delivering the user input to the server 1520 via the network 1510. This real-time interactive component of cloud gaming may present challenges with respect to latency.

[0183] Additional System Overview Examples

[0184] Fig.16 is a block diagram of a processing system 1600 according to one embodiment. In various embodiments, system 1600 includes one or more processors 1602 and one or more graphics processors 1608, and may be a single-processor desktop system, a multi-processor workstation system, or a server system with a large number of processors 1602 or processor cores 1607. In one embodiment, system 1600 is a processing platform incorporated within a system-on-chip (SoC) integrated circuit for use in a mobile, handheld, or embedded device.

[0185] Embodiments of system 1600 may include or be incorporated into a server-based gaming platform, a gaming console including a gaming and media console, a mobile gaming console, a handheld gaming console, or an online gaming console. In some embodiments, system 1600 is a mobile phone, a smart phone, a tablet computing device, or a mobile Internet device. Data processing system 1600 may also include a wearable device, coupled to a wearable device, or integrated into a wearable device, such as a smart watch wearable device, a smart glasses device, an augmented reality device, or a virtual reality device. In some embodiments, data processing system 1600 is a television or set-top box device having one or more processors 1602 and a graphical interface generated by one or more graphics processors 1608.

[0186] In some embodiments, one or more processors 1602 each include one or more processor cores 1607 for processing instructions that, when executed, perform operations for system and user software. In some embodiments, each of the one or more processor cores 1607 is configured to process a specific instruction set 1609. In some embodiments, the instruction set 1609 may facilitate complex instruction set computing (CISC), reduced instruction set computing (RISC), or computing via very long instruction words (VLIW). Multiple processor cores 1607 may each process a different instruction set 1609, which may include instructions that facilitate the emulation of other instruction sets. The processor core 1607 may also include other processing devices, such as a digital signal processor (DSP).

[0187] In some embodiments, the processor 1602 includes a cache memory 1604. Depending on the architecture, the processor 1602 may have a single internal cache or multiple levels of internal cache. In some embodiments, the cache memory is shared between various components of the processor 1602. In some embodiments, the processor 1602 also uses an external cache (e.g., a level 3 (L3) cache or a final level cache (LLC)) (not shown), which may be shared between the processor cores 1607 using known cache coherence techniques. A register file 1606 is additionally included in the processor 1602, which may include different types of registers (e.g., integer registers, floating point registers, status registers, and instruction pointer registers) for storing different types of data. Some registers may be general purpose registers, while other registers may be specific to the design of the processor 1602.

[0188] In some embodiments, the processor 1602 is coupled to a processor bus 1610 to transmit communication signals such as address, data, or control signals between the processor 1602 and other components in the system 1600. In one embodiment, the system 1600 uses an exemplary "hub" system architecture that includes a memory controller hub 1616 and an input-output (I / O) controller hub 1630. The memory controller hub 1616 facilitates communication between memory devices and other components of the system 1600, while the I / O controller hub (ICH) 1630 provides connections to I / O devices via a local I / O bus. In one embodiment, the logic of the memory controller hub 1616 is integrated within the processor.

[0189] The memory device 1620 may be a dynamic random access memory (DRAM) device, a static random access memory (SRAM) device, a flash memory device, a phase change memory device, or some other memory device with suitable performance for use as processing memory. In one embodiment, the memory device 1620 may operate as system memory for the system 1600 to store data 1622 and instructions 1621 for use when one or more processors 1602 execute applications or processes. The memory controller hub 1616 is also coupled to an optional external graphics processor 1612, which may communicate with one or more graphics processors 1608 in the processor 1602 to perform graphics and media operations.

[0190] In some embodiments, the ICH 1630 enables peripheral devices to connect to the memory device 1620 and the processor 1602 via a high-speed I / O bus. The I / O peripheral devices include, but are not limited to, an audio controller 1646, a firmware interface 1628, a wireless transceiver 1626 (e.g., Wi-Fi, Bluetooth), a data storage device 1624 (e.g., a hard drive, flash memory, etc.), and a traditional I / O controller 1640 for coupling traditional (e.g., Personal System 2 (PS / 2)) devices to the system. One or more Universal Serial Bus (USB) controllers 1642 connect input devices such as a keyboard and mouse 1644 combination. A network controller 1634 may also be coupled to the ICH 1630. In some embodiments, a high-performance network controller (not shown) is coupled to the processor bus 1610. It will be appreciated that the system 1600 shown is exemplary and not limiting, as other types of data processing systems in different configurations may also be used. For example, I / O controller hub 1630 may be integrated within one or more processors 1602 , or memory controller hub 1616 and I / O controller hub 1630 may be integrated into a separate external graphics processor, such as external graphics processor 1612 .

[0191] Fig.17 17 is a block diagram of an embodiment of a processor 1700 having one or more processor cores 1702A-1702N, an integrated memory controller 1714, and an integrated graphics processor 1708. Elements having the same reference numerals (or names) as elements in any other figure herein Fig.17 Those elements may operate or function in any manner similar to that described elsewhere herein, but are not limited thereto. Processor 1700 may include additional cores, up to and including additional core 1702N represented by a dashed box. Each of processor cores 1702A-1702N includes one or more internal cache units 1704A-1704N. In some embodiments, each processor core may also have access to one or more shared cache units 1706.

[0192] Internal cache units 1704A-1704N and shared cache unit 1706 represent a cache memory hierarchy within processor 1700. The cache memory hierarchy may include at least one level of instruction and data cache in each processor core and one or more levels of shared mid-level cache, such as level 2 (L2), level 3 (L3), level 4 (L4), or other levels of cache, where the highest level cache before external memory is classified as LLC. In some embodiments, cache coherence logic maintains coherence between the various cache units 1706 and 1704A-1704N.

[0193] In some embodiments, the processor 1700 may also include a set of one or more bus controller units 1716 and a system agent core 1710. The one or more bus controller units 1716 manage a set of peripheral buses, such as one or more peripheral component interconnect buses (e.g., PCI, PCI Express). The system agent core 1710 provides management functionality for various processor components. In some embodiments, the system agent core 1710 includes one or more integrated memory controllers 1714 to manage access to various external memory devices (not shown).

[0194] In some embodiments, one or more of the processor cores 1702A-1702N include support for simultaneous multithreading. In such embodiments, the system agent core 1710 includes components for coordinating and operating the cores 1702A-1702N during multithreaded processing. The system agent core 1710 may additionally include a power control unit (PCU) that includes logic and components to regulate the power state of the processor cores 1702A-1702N and the graphics processor 1708.

[0195] In some embodiments, the processor 1700 additionally includes a graphics processor 1708 to perform graphics processing operations. In some embodiments, the graphics processor 1708 is coupled to the set of shared cache units 1706 and a system agent core 1710 including one or more integrated memory controllers 1714. In some embodiments, a display controller 1711 is coupled to the graphics processor 1708 to drive the graphics processor output to one or more coupled displays. In some embodiments, the display controller 1711 can be a separate module coupled to the graphics processor via at least one interconnect, or can be integrated within the graphics processor 1708 or the system agent core 1710.

[0196] In some embodiments, a ring-based interconnect unit 1712 is used to couple the internal components of the processor 1700. However, alternative interconnect units may be used, such as point-to-point interconnects, switched interconnects, or other technologies including those known in the art. In some embodiments, the graphics processor 1708 is coupled to the ring interconnect 1712 via an I / O link 1713.

[0197] Exemplary I / O links 1713 represent at least one of a variety of I / O interconnects, including packaged I / O interconnects that facilitate communication between various processor components and high-performance embedded memory modules 1718, such as eDRAM modules. In some embodiments, each of processor cores 1702-1702N and graphics processor 1708 uses embedded memory module 1718 as a shared last-level cache.

[0198] In some embodiments, the processor cores 1702A-1702N are homogeneous cores that execute the same instruction set architecture. In another embodiment, the processor cores 1702A-1702N are heterogeneous in terms of instruction set architecture (ISA), where one or more processor cores 1702A-N execute a first instruction set, while at least one of the other cores executes a subset of the first instruction set or a different instruction set. In one embodiment, the processor cores 1702A-1702N are heterogeneous in terms of microarchitecture, where one or more cores with relatively high power consumption are coupled with one or more power cores with lower power consumption. In addition, the processor 1700 can be implemented on one or more chips or as a SoC integrated circuit having the components shown in addition to other components.

[0199] Fig.181 is a block diagram of a graphics processor 1800, which may be a discrete graphics processing unit, or may be a graphics processor integrated with multiple processing cores. In some embodiments, the graphics processor communicates via a memory-mapped I / O interface to registers on the graphics processor and using commands placed in processor memory. In some embodiments, the graphics processor 1800 includes a memory interface 1814 to access memory. The memory interface 1814 may be an interface to local memory, one or more internal caches, one or more shared external caches, and / or to system memory.

[0200] In some embodiments, the graphics processor 1800 also includes a display controller 1802 to drive display output data to a display device 1820. The display controller 1802 includes hardware for one or more overlay planes for display and combination of multiple layers of video or user interface elements. In some embodiments, the graphics processor 1800 includes a video codec engine 1806 to encode media to, decode from, or transcode between one or more media coding formats, including but not limited to Moving Picture Experts Group (MPEG) formats such as MPEG-2, Advanced Video Coding (AVC) formats such as H.264 / MPEG-4 AVC, and Society of Motion Picture and Television Engineers (SMPTE) 421M / VC-1 and Joint Photographic Experts Group (JPEG) formats such as JPEG formats and Motion JPEG (MJPEG) formats.

[0201] In some embodiments, graphics processor 1800 includes a block image transfer (BLIT) engine 1804 to perform two-dimensional (2D) rasterizer operations, including, for example, bit boundary block transfers. However, in one embodiment, 2D graphics operations are performed using one or more components of a graphics processing engine (GPE) 1810. In some embodiments, graphics processing engine 1810 is a compute engine for performing graphics operations including three-dimensional (3D) graphics operations and media operations.

[0202] In some embodiments, GPE 1810 includes a 3D pipeline 1812 for performing 3D operations, such as rendering three-dimensional images and scenes using processing functions that act on 3D primitive shapes (e.g., rectangles, triangles, etc.). 3D pipeline 1812 includes programmable and fixed function elements that perform various tasks within the element and / or yield execution threads to 3D / media subsystem 1815. While 3D pipeline 1812 can be used to perform media operations, embodiments of GPE 1810 also include a media pipeline 1816 specifically for performing media operations such as video post-processing and image enhancement.

[0203] In some embodiments, the media pipeline 1816 includes fixed-function or programmable logic units to perform one or more specialized media operations, such as video decoding acceleration, video deinterlacing, and video encoding acceleration, instead of or on behalf of the video codec engine 1806. In some embodiments, the media pipeline 1816 additionally includes a thread spawning unit to spawn threads for execution on the 3D / media subsystem 1815. The spawned threads perform calculations for media operations on one or more graphics execution units included in the 3D / media subsystem 1815.

[0204] In some embodiments, 3D / media subsystem 1815 includes logic for executing threads produced by 3D pipeline 1812 and media pipeline 1816. In one embodiment, the pipeline sends thread execution requests to 3D / media subsystem 1815, which includes thread dispatch logic for arbitrating and dispatching various requests to available thread execution resources. Execution resources include an array of graphics execution units for processing 3D and media threads. In some embodiments, 3D / media subsystem 1815 includes one or more internal caches for thread instructions and data. In some embodiments, the subsystem also includes shared memory, including registers and addressable memory, for sharing data between threads and storing output data.

[0205] 3D / Media Processing

[0206] Fig.19 is a block diagram of a graphics processing engine 1910 of a graphics processor according to some embodiments. In one embodiment, GPE 1910 is Fig.18 A version of the GPE 1810 is shown in FIG. Elements having the same reference numerals (or names) as elements in any other figure herein Fig.19 The elements of may operate or function in any manner similar to that described elsewhere herein, but are not limited thereto.

[0207] In some embodiments, the GPE 1910 is coupled to a command streamer 1903, which provides a command stream to the GPE 3D and media pipelines 1912, 1916. In some embodiments, the command streamer 1903 is coupled to a memory, which can be a system memory or one or more internal cache memories and shared cache memories. In some embodiments, the command streamer 1903 receives commands from the memory and sends the commands to the 3D pipeline 1912 and / or the media pipeline 1916. The command is an instruction obtained from a ring buffer storing commands for the 3D and media pipelines 1912, 1916. In one embodiment, the ring buffer may additionally include a batch command buffer storing a batch of multiple commands. The 3D and media pipelines 1912, 1916 process the commands by performing operations via logic within the corresponding pipeline or by dispatching one or more execution threads to the execution unit array 1914. In some embodiments, execution unit array 1914 is scalable such that the array includes a variable number of execution units based on the target power and performance level of GPE 1910 .

[0208] In some embodiments, sampling engine 1930 is coupled to memory (e.g., cache memory or system memory) and execution unit array 1914. In some embodiments, sampling engine 1930 provides a memory access mechanism for execution unit array 1914 that allows execution array 1914 to read graphics and media data from memory. In some embodiments, sampling engine 1930 includes logic to perform specialized image sampling operations for media.

[0209] In some embodiments, the specialized media sampling logic in the sampling engine 1930 includes a denoising / de-interlacing module 1932, a motion estimation module 1934, and an image scaling and filtering module 1936. In some embodiments, the denoising / de-interlacing module 1932 includes logic for performing one or more denoising or de-interlacing algorithms on decoded video data. The de-interlacing logic combines alternating fields of interlaced video content into a single video frame. The denoising logic reduces or removes data noise from video and image data. In some embodiments, the denoising logic and the de-interlacing logic are motion adaptive and use spatial or temporal filtering based on the amount of motion detected in the video data. In some embodiments, the denoising / de-interlacing module 1932 includes dedicated motion detection logic (e.g., within the motion estimation engine 1934).

[0210] In some embodiments, the motion estimation engine 1934 provides hardware acceleration for video operations by performing video acceleration functions such as motion vector estimation and prediction on video data. The motion estimation engine determines motion vectors that describe the transformation of image data between consecutive video frames. In some embodiments, the graphics processor media codec uses the video motion estimation engine 1934 to perform operations on the video at the macroblock level that may otherwise be too computationally intensive to be performed with a general purpose processor. In some embodiments, the motion estimation engine 1934 is generally available to the graphics processor component to assist video decoding and processing functions that are sensitive to or adapted to the direction or magnitude of motion within the video data.

[0211] In some embodiments, the image scaling and filtering module 1936 performs image processing operations to enhance the visual quality of the generated images and videos. In some embodiments, the scaling and filtering module 1936 processes the image and video data during sampling operations before providing the data to the execution unit array 1914.

[0212] In some embodiments, GPE 1910 includes a data port 1944 that provides an additional mechanism for the graphics subsystem to access memory. In some embodiments, data port 1944 facilitates memory access for operations including render target writes, constant buffer reads, temporary memory space reads / writes, and media surface accesses. In some embodiments, data port 1944 includes a cache memory space for caching accesses to memory. The cache memory can be a single data cache, or can be divided into multiple caches (e.g., render buffer cache, constant buffer cache, etc.) for multiple subsystems that access memory via the data port. In some embodiments, threads executing on execution units in execution unit array 1914 communicate with the data port by exchanging messages via a data distribution interconnect that couples each subsystem of GPE 1910.

[0213] Execution Unit

[0214] Fig. 20 is a block diagram of another embodiment of a graphics processor 2000. Elements having the same reference numerals (or names) as elements in any other figure herein Fig. 20 The elements of may operate or function in any manner similar to that described elsewhere herein, but are not limited thereto.

[0215] In some embodiments, graphics processor 2000 includes ring interconnect 2002, pipeline front end 2004, media engine 2037, and graphics cores 2080A-2080N. In some embodiments, ring interconnect 2002 couples the graphics processor to other processing units, including other graphics processors or one or more general-purpose processor cores. In some embodiments, the graphics processor is one of many processors integrated into a multi-core processing system.

[0216] In some embodiments, the graphics processor 2000 receives batches of commands via a ring interconnect 2002. Incoming commands are interpreted by a command streamer 2003 in a pipeline front end 2004. In some embodiments, the graphics processor 2000 includes scalable execution logic to perform 3D geometry processing and media processing via (one or more) graphics cores 2080A-2080N. For 3D geometry processing commands, the command streamer 2003 supplies the commands to a geometry pipeline 2036. For at least some media processing commands, the command streamer 2003 supplies the commands to a video front end 2034 coupled to a media engine 2037. In some embodiments, the media engine 2037 includes a video quality engine (VQE) 2030 for video and image post-processing and a multi-format encoding / decoding (MFX) 2033 engine to provide hardware accelerated media data encoding and decoding. In some embodiments, the geometry pipeline 2036 and the media engine 2037 each generate execution threads for thread execution resources provided by at least one graphics core 2080A.

[0217] In some embodiments, the graphics processor 2000 includes scalable thread execution resource feature modular cores 2080A-2080N (sometimes referred to as core slices), each of which has multiple sub-cores 2050A-2050N, 2060A-2060N (sometimes referred to as core sub-slices). In some embodiments, the graphics processor 2000 can have any number of graphics cores 2080A to 2080N. In some embodiments, the graphics processor 2000 includes a graphics core 2080A having at least a first sub-core 2050A and a second core sub-core 2060A. In other embodiments, the graphics processor is a low-power processor with a single sub-core (e.g., 2050A). In some embodiments, the graphics processor 2000 includes multiple graphics cores 2080A-2080N, each of which includes a set of first sub-cores 2050A-2050N and a set of second sub-cores 2060A-2060N. Each sub-core in the set of first sub-cores 2050A-2050N includes at least a first set of execution units 2052A-2052N and a media / texture sampler 2054A-2054N. Each sub-core in the set of second sub-cores 2060A-2060N includes at least a second set of execution units 2062A-2062N and a sampler 2064A-2064N. In some embodiments, each sub-core 2050A-2050N, 2060A-2060N shares a set of shared resources 2070A-2070N. In some embodiments, the shared resources include a shared cache memory and pixel operation logic. Other shared resources may also be included in various embodiments of the graphics processor.

[0218] Fig.21 The figure shows thread execution logic 2100 including an array of processing elements employed in some embodiments of a GPE. Elements having the same reference numerals (or names) as elements in any other figure herein Fig.21 The elements of may operate or function in any manner similar to that described elsewhere herein, but are not limited thereto.

[0219] In some embodiments, the thread execution logic 2100 includes a pixel shader 2102, a thread dispatcher 2104, an instruction cache 2106, a scalable execution unit array including a plurality of execution units 2108A-2108N, a sampler 2110, a data cache 2112, and a data port 2114. In one embodiment, the included components are interconnected via an interconnect structure linked to each component. In some embodiments, the thread execution logic 2100 includes one or more connections to a memory such as a system memory or a cache memory through one or more of the instruction cache 2106, the data port 2114, the sampler 2110, and the execution unit array 2108A-2108N. In some embodiments, each execution unit (e.g., 2108A) is an individual vector processor capable of executing multiple concurrent threads and processing multiple data elements in parallel for each thread. In some embodiments, the execution unit array 2108A-2108N includes any number of individual execution units.

[0220] In some embodiments, execution unit arrays 2108A-2108N are primarily used to execute "shader" programs. In some embodiments, the execution units in arrays 2108A-2108N execute an instruction set that includes native support for many standard 3D graphics shader instructions, allowing shader programs from graphics libraries (e.g., Direct 3D and OpenGL) to be executed with minimal conversion. The execution units support vertex and geometry processing (e.g., vertex programs, geometry programs, vertex shaders), pixel processing (e.g., pixel shaders, fragment shaders), and general processing (e.g., compute and media shaders).

[0221] Each execution unit in the execution unit array 2108A-2108N operates on an array of data elements. The number of data elements is the "execution size" or number of lanes for the instruction. An execution lane is a logical execution unit for data element access, masking, and flow control within an instruction. The number of lanes may be independent of the number of physical arithmetic logic units (ALUs) or floating point units (FPUs) for a particular graphics processor. In some embodiments, the execution units 2108A-2108N support integer and floating point data types.

[0222] The execution unit instruction set includes single instruction multiple data (SIMD) instructions. Various data elements can be stored in registers as packed data types, and the execution unit will process various elements based on the data size of the element. For example, when operating on a vector of 256 bits of width, 256 bits of the vector are stored in registers, and the execution unit operates on the vector as four separate 64-bit packed data elements (data elements of quadword (QW) size), 8 separate 32-bit packed data elements (data elements of doubleword (DW) size), 16 separate 16-bit packed data elements (data elements of word (W) size), or 32 separate 8-bit data elements (data elements of byte (B) size). However, different vector widths and register sizes are possible.

[0223] One or more internal instruction caches (e.g., 2106) are included in the thread execution logic 2100 to cache thread instructions for the execution unit. In some embodiments, one or more data caches (e.g., 2112) are included to cache thread data during thread execution. In some embodiments, a sampler 2110 is included to provide texture sampling for 3D operations and media sampling for media operations. In some embodiments, the sampler 2110 includes specialized texture or media sampling functionality to process texture or media data during the sampling process before providing the sampled data to the execution unit.

[0224] During execution, the graphics and media pipelines send thread initiation requests to the thread execution logic 2100 via thread yielding and dispatching logic. In some embodiments, the thread execution logic 2100 includes a local thread dispatcher 2104 that arbitrates thread initiation requests from the graphics and media pipelines and instantiates the requested threads on one or more execution units 2108A-2108N. For example, the geometry pipeline (e.g., Fig. 20 2036) dispatches vertex processing, tessellation or geometry processing threads to thread execution logic 2100 ( Fig.21 ). In some embodiments, thread dispatcher 2104 may also process runtime thread yield requests from executing shader programs.

[0225] Once the group of geometric objects has been processed and rasterized into pixel data, the pixel shader 2102 is dispatched to further calculate output information and cause the results to be written to an output surface (e.g., a color buffer, a depth buffer, a stencil buffer, etc.). In some embodiments, the pixel shader 2102 calculates the values ​​of various vertex attributes to be interpolated on the rasterized object. In some embodiments, the pixel shader 2102 then executes a pixel shader program supplied by an application programming interface (API). To execute the pixel shader program, the pixel shader 2102 dispatches threads to execution units (e.g., 2108A) via a thread dispatcher 2104. In some embodiments, the pixel shader 2102 uses texture sampling logic in a sampler 2110 to access texture data in a texture map stored in memory. Arithmetic operations on the texture data and the input geometric data calculate pixel color data for each geometric fragment, or discard one or more pixels for further processing.

[0226] In some embodiments, data port 2114 provides a memory access mechanism for thread execution logic 2100 to output processed data to memory for processing on the graphics processor output pipeline. In some embodiments, data port 2114 includes or is coupled to one or more cache memories (e.g., data cache 2112) to cache data for memory access via the data port.

[0227] Fig. 22 2200 is a block diagram illustrating a graphics processor instruction format 2200 according to some embodiments. In one or more embodiments, the graphics processor execution unit supports an instruction set having instructions in multiple formats. Solid line blocks illustrate components that are typically included in the execution unit instructions, while dashed lines include optional components or components that are only included in a subset of the instructions. In some embodiments, the described and illustrated instruction format 2200 are macroinstructions because they are instructions that are supplied to the execution unit - as opposed to micro-operations that are generated from instruction decode once the instruction is processed.

[0228] In some embodiments, the graphics processor execution unit natively supports instructions in 128-bit format 2210. Based on the selected instructions, instruction options, and the number of operands, a 64-bit compact instruction format 2230 may be used for some instructions. The native 128-bit format 2210 provides access to all instruction options, while some options and operations are restricted to 64-bit format 2230. The native instructions available in 64-bit format 2230 vary from embodiment to embodiment. In some embodiments, instructions are compressed using, in part, a set of index values ​​in index field 2213. The execution unit hardware references a set of compression tables based on the index values ​​and uses the compression table output to reconstruct the native instructions in 128-bit format 2210.

[0229] For each format, the instruction opcode 2212 defines the operation to be performed by the execution unit. The execution unit executes each instruction in parallel on multiple data elements of each operand. For example, in response to an add instruction, the execution unit performs a simultaneous add operation on each color channel representing a texture element or a picture element. By default, the execution unit executes each instruction on all data channels of the operand. In some embodiments, the instruction control field 2214 enables control over certain execution options, such as channel selection (e.g., prediction) and data channel order (e.g., deployment). For 128-bit instructions 2210, the execution size field 2216 limits the number of data channels that will be executed in parallel. In some embodiments, the execution size field 2216 is not available for use in a 64-bit compact instruction format 2230.

[0230] Some execution unit instructions have up to three operands, including two source operands src0 2220, src1 2222, and one destination 2218. In some embodiments, the execution unit supports dual destination instructions, where one of the destinations is implicit. Data manipulation instructions may have a third source operand (e.g., SRC2 2224), where the instruction opcode 2212 determines the number of source operands. The last source operand of an instruction may be an immediate (e.g., hard-coded) value passed with the instruction.

[0231] In some embodiments, the 128-bit instruction format 2210 includes access / addressing mode information 2226 that specifies, for example, whether direct register addressing mode or indirect register addressing mode is used. When direct register addressing mode is used, the register address of one or more operands is provided directly by bits in the instruction 2210.

[0232] In some embodiments, the 128-bit instruction format 2210 includes an access / addressing mode field 2226 that specifies an addressing mode and / or access mode for the instruction. In one embodiment, the access mode is used to define the data access alignment for the instruction. Some embodiments support access modes including 16-byte aligned access modes and 1-byte aligned access modes, wherein the byte alignment of the access mode determines the access alignment of the instruction operand. For example, when in a first mode, the instruction 2210 can use byte-aligned addressing for source operands and destination operands, and when in a second mode, the instruction 2210 can use 16-byte aligned addressing for all source operands and destination operands.

[0233] In one embodiment, the addressing mode portion of the access / addressing mode field 2226 determines whether the instruction uses direct addressing or indirect addressing. When direct register addressing mode is used, the bits in the instruction 2210 directly provide the register address of one or more operands. When indirect register addressing mode is used, the register address of one or more operands can be calculated based on the address register value and the address immediate field in the instruction.

[0234] In some embodiments, instructions are grouped based on the opcode 2212 bit field to simplify opcode decoding 2240. For 8-bit opcodes, bits 4, 5, and 6 allow the execution unit to determine the type of opcode. The precise opcode grouping shown is just an example. In some embodiments, the move and logic opcode group 2242 includes data movement and logic instructions (e.g., move (mov), compare (cmp)). In some embodiments, the move and logic group 2242 shares five most significant bits (MSBs), where the move (mov) instruction is in the form of 0000xxxxb, and the logic instruction is in the form of 0001xxxxb. The flow control instruction group 2244 (e.g., call, jump (jmp)) includes instructions in the form of 0010xxxxb (e.g., 0x20). The miscellaneous instruction group 2246 includes a mixture of instructions, which includes synchronization instructions (e.g., wait, send) in the form of 0011xxxxb (e.g., 0x30). The parallel math instruction group 2248 includes component-wise arithmetic instructions (e.g., addition, multiplication (mul)) of the form 0100xxxxb (e.g., 0x40). The parallel math group 2248 performs arithmetic operations in parallel on the data path. The vector math group 2250 includes arithmetic instructions (e.g., dp4) of the form 0101xxxxb (e.g., 0x50). The vector math group performs arithmetic operations on vector operands, such as dot product calculations.

[0235] Graphics Pipeline

[0236] Fig.23 is a block diagram of another embodiment of a graphics processor 2300. Elements having the same reference numerals (or names) as elements in any other figure herein Fig.23 The elements of may operate or function in any manner similar to that described elsewhere herein, but are not limited thereto.

[0237] In some embodiments, the graphics processor 2300 includes a graphics pipeline 2320, a media pipeline 2330, a display engine 2340, a thread execution logic 2350, and a rendering output pipeline 2370. In some embodiments, the graphics processor 2300 is a graphics processor within a multi-core processing system that includes one or more general-purpose processing cores. The graphics processor is controlled by register writes to one or more control registers (not shown) or by commands issued to the graphics processor 2300 via the ring interconnect 2302. In some embodiments, the ring interconnect 2302 couples the graphics processor 2300 to other processing components such as other graphics processors or general-purpose processors. Commands from the ring interconnect 2302 are interpreted by a command streamer 2303, which supplies instructions to various components of the graphics pipeline 2320 or the media pipeline 2330.

[0238] In some embodiments, command streamer 2303 directs the operation of vertex fetcher 2305, which reads vertex data from memory and executes vertex processing commands provided by command streamer 2303. In some embodiments, vertex fetcher 2305 provides vertex data to vertex shader 2307, which performs coordinate space transformation and lighting operations on each vertex. In some embodiments, vertex fetcher 2305 and vertex shader 2307 execute vertex processing instructions by dispatching execution threads to execution units 2352A, 2352B via thread dispatcher 2331.

[0239] In some embodiments, execution units 2352A, 2352B are arrays of vector processors with instruction sets for performing graphics and media operations. In some embodiments, execution units 2352A, 2352B have an attached L1 cache 2351 that is dedicated to each array or shared between arrays. The cache can be configured as a data cache, an instruction cache, or partitioned into a single cache containing data and instructions in different partitions.

[0240] In some embodiments, the graphics pipeline 2320 includes a tessellation component to perform hardware accelerated tessellation of 3D objects. In some embodiments, the programmable shell shader 2311 configures the tessellation operation. The programmable domain shader 2317 provides back-end evaluation of the tessellation output. The tessellation 2313 operates at the direction of the shell shader 2311 and contains dedicated logic to generate a set of detailed geometric objects based on the rough geometric model provided as input to the graphics pipeline 2320. In some embodiments, if tessellation is not used, the tessellation components 2311, 2313, 2317 can be bypassed.

[0241] In some embodiments, the complete geometric object may be processed by the geometry shader 2319 via one or more threads dispatched to the execution units 2352A, 2352B, or may proceed directly to the clipper 2329. In some embodiments, the geometry shader operates on the entire geometric object, rather than on vertices or vertex patches as in previous stages of the graphics pipeline. If tessellation is disabled, the geometry shader 2319 receives input from the vertex shader 2307. In some embodiments, the geometry shader 2319 may be programmed by a geometry shader program to perform geometry tessellation when the tessellation unit is disabled.

[0242] Before rasterization, the clipper 2329 processes the vertex data. The clipper 2329 can be a fixed function clipper or a programmable clipper with clipping and geometry shader functions. In some embodiments, the rasterizer 2373 (e.g., a depth test component) in the render output pipeline 2370 dispatches a pixel shader to convert the geometric object into its per-pixel representation. In some embodiments, the pixel shader logic is included in the thread execution logic 2350. In some embodiments, the application can bypass the rasterizer 2373 and access the unrasterized vertex data via the outflow unit 2323.

[0243] The graphics processor 2300 has an interconnect bus, interconnect structure, or some other interconnect mechanism that allows data and messages to be passed between the main components of the processor. In some embodiments, the execution units 2352A, 2352B and associated cache(s) 2351, texture and media samplers 2354, and texture / sampler cache 2358 are interconnected via data ports 2356 to perform memory accesses and communicate with the rendering output pipeline components of the processor. In some embodiments, the samplers 2354, caches 2351, 2358, and execution units 2352A, 2352B each have separate memory access paths.

[0244] In some embodiments, the rendering output pipeline 2370 includes a rasterizer 2373 that converts vertex-based objects into associated pixel-based representations. In some embodiments, the rasterizer logic includes a windower / masker unit that performs fixed-function triangle and line rasterization. An associated renderer cache 2378 and depth cache 2379 are also available in some embodiments. The pixel operation component 2377 performs pixel-based operations on data, but in some cases, pixel operations associated with 2D operations (e.g., bit-block image transfer with blending) are performed by the 2D engine 2341, or replaced by the display controller 2343 using an overlay display plane at display time. In some embodiments, a shared L3 cache 2375 is available to all graphics components, allowing data to be shared without using main system memory.

[0245] In some embodiments, the graphics processor media pipeline 2330 includes a media engine 2337 and a video front end 2334. In some embodiments, the video front end 2334 receives pipeline commands from the command streamer 2303. In some embodiments, the media pipeline 2330 includes a separate command streamer. In some embodiments, the video front end 2334 processes media commands before sending the commands to the media engine 2337. In some embodiments, the media engine 2337 includes thread yielding functionality to yield threads for dispatching to the thread execution logic 2350 via the thread dispatcher 2331.

[0246] In some embodiments, the graphics processor 2300 includes a display engine 2340. In some embodiments, the display engine 2340 is external to the processor 2300 and is coupled to the graphics processor via the ring interconnect 2302 or some other interconnect bus or structure. In some embodiments, the display engine 2340 includes a 2D engine 2341 and a display controller 2343. In some embodiments, the display engine 2340 contains dedicated logic that can operate independently of the 3D pipeline. In some embodiments, the display controller 2343 is coupled to a display device (not shown), which can be a system integrated display device such as in a laptop computer, or an external display device attached via a display device connector.

[0247] In some embodiments, the graphics pipeline 2320 and the media pipeline 2330 can be configured to perform operations based on multiple graphics and media programming interfaces, and are not specific to any one application programming interface (API). In some embodiments, the driver software for the graphics processor converts API calls that are specific to a specific graphics or media library into commands processed by the graphics processor. In some embodiments, support is provided for the Open Graphics Library (OpenGL) and Open Computing Language (OpenCL) from the Khronos Group, the Direct3D library from Microsoft, or support can be provided for both OpenGL and D3D. Support can also be provided for the open source computer vision library (OpenCV). If a mapping from the pipeline of a future API to the pipeline of a graphics processor can be performed, future APIs with compatible 3D pipelines will also be supported.

[0248] Graphics Pipeline Programming

[0249] Fig.24A is a block diagram illustrating a graphics processor command format 2400 according to some embodiments. Fig. 24B is a block diagram illustrating a graphics processor command sequence 2410 according to an embodiment. Fig.24A The solid line boxes in show components that are typically included in the graphics commands, while the dashed lines include optional components or components that are included only in a subset of the graphics commands. Fig.24A An exemplary graphics processor command format 2400 may include a data field to identify the target client 2402 of the command, a command operation code (opcode) 2404, and associated data for the command 2406. In some commands, a sub-opcode 2405 and a command size 2408 are also included.

[0250] In some embodiments, client 2402 specifies the client unit of the graphics device that processes the command data. In some embodiments, the graphics processor command parser checks the client field of each command to adjust the further processing of the command and routes the command data to the appropriate client unit. In some embodiments, the graphics processor client unit includes a memory interface unit, a rendering unit, a 2D unit, a 3D unit, and a media unit. Each client unit has a corresponding processing pipeline for processing commands. Once the client unit receives the command, the client unit reads the opcode 2404 and the sub-opcode 2405, if any, to determine the operation to be performed. The client unit uses the information in the data field 2406 to execute the command. For some commands, an explicit command size 2408 is expected to specify the size of the command. In some embodiments, the command parser automatically determines the size of at least some commands based on the command opcode. In some embodiments, the command is aligned via multiple double words.

[0251] Fig. 24B An exemplary graphics processor command sequence 2410 is shown in the flowchart in FIG. In some embodiments, software or firmware of a data processing system featuring an embodiment of a graphics processor uses a version of the command sequence shown to set up, execute, and terminate a set of graphics operations. The example command sequence is shown and described for purposes of example only, as embodiments are not limited to these particular commands or to the command sequence. Furthermore, commands may be issued as batch commands in a command sequence so that the graphics processor will process the command sequence at least partially simultaneously.

[0252] In some embodiments, the graphics processor command sequence 2410 may begin with a pipeline dump clear command 2412 to cause any active graphics pipeline to complete currently pending commands for that pipeline. In some embodiments, the 3D pipeline 2422 and the media pipeline 2424 do not operate simultaneously. The pipeline dump clear is performed to cause the active graphics pipeline to complete any pending commands. In response to the pipeline dump clear, the command parser for the graphics processor will suspend command processing until the active drawing engine completes pending operations and the associated read cache is invalidated. Optionally, any data marked as "dirty" in the renderer cache may be dumped to memory. In some embodiments, the pipeline dump clear command 2412 may be used before placing the graphics processor in a low power state or for pipeline synchronization.

[0253] In some embodiments, pipeline select command 2413 is used when a command sequence requires the graphics processor to explicitly switch between pipelines. In some embodiments, pipeline select command 2413 is only required once in an execution context before issuing pipeline commands - unless the context is to issue commands for both pipelines. In some embodiments, pipeline flush command 2412 is required immediately before a pipeline switch via pipeline select command 2413.

[0254] In some embodiments, pipeline control commands 2414 configure the graphics pipeline for operation and are used to program 3D pipeline 2422 and media pipeline 2424. In some embodiments, pipeline control commands 2414 configure the pipeline state for the active pipeline. In one embodiment, pipeline control commands 2414 are used for pipeline synchronization and to clean up data from one or more cache memories within the active pipeline before processing batch commands.

[0255] In some embodiments, return buffer state command 2416 is used to configure a set of return buffers for a corresponding pipeline to write data. Some pipeline operations require allocating, selecting or configuring one or more return buffers into which the operation writes intermediate data during processing. In some embodiments, the graphics processor also uses one or more return buffers to store output data and perform cross-thread communication. In some embodiments, return buffer state 2416 includes selecting the size and number of return buffers for a set of pipeline operations.

[0256] The remaining commands in the command sequence differ based on the active pipeline for operation.Based on the pipeline determination 2420 , the command sequence is customized for either the 3D pipeline 2422 starting with the 3D pipeline state 2430 or the media pipeline 2424 starting with the media pipeline state 2440 .

[0257] The commands for 3D pipeline state 2430 include 3D state setting commands for vertex buffer state, vertex element state, constant color state, depth buffer state, and other state variables to be configured before processing 3D primitive commands. The values ​​of these commands are determined based at least in part on the specific 3D API being used. In some embodiments, 3D pipeline state 2430 commands can also selectively disable or bypass certain pipeline elements if they are not going to be used.

[0258] In some embodiments, 3D primitives 2432 commands are used to submit 3D primitives to be processed by the 3D pipeline. The commands and associated parameters passed to the graphics processor via the 3D primitive 2432 commands are forwarded to the vertex extraction function in the graphics pipeline. The vertex extraction function uses the 3D primitive 2432 command data to generate a vertex data structure. The vertex data structure is stored in one or more return buffers. In some embodiments, 3D primitives 2432 commands are used to perform vertex operations on 3D primitives via vertex shaders. In order to process the vertex shader, the 3D pipeline 2422 dispatches the shader execution thread to the graphics processor execution unit.

[0259] In some embodiments, the 3D pipeline 2422 is triggered via an execution 2434 command or event. In some embodiments, a register write triggers the command execution. In some embodiments, the execution is triggered via a "go" or "kick" command in a command sequence. In one embodiment, a pipeline synchronization command is used to trigger the command execution to clear the command sequence through the graphics pipeline dump. The 3D pipeline will perform geometry processing for 3D primitives. Once the operation is completed, the resulting geometric objects are rasterized and the pixel engine colors the resulting pixels. Additional commands to control pixel shading and pixel backend operations may also be included for these operations.

[0260] In some embodiments, when performing media operations, the graphics processor command sequence 2410 follows the media pipeline 2424 path. In general, the specific use and programming of the media pipeline 2424 depends on the media or computing operation to be performed. During media decoding, specific media decoding operations can be offloaded to the media pipeline. In some embodiments, the media pipeline can also be bypassed, and the media decoding can be performed in whole or in part using resources provided by one or more general-purpose processing cores. In one embodiment, the media pipeline also includes elements for general-purpose graphics processor unit (GPGPU) operations, where the graphics processor is used to perform SIMD vector operations using compute shader programs that are not explicitly related to the rendering of graphics primitives.

[0261] In some embodiments, the media pipeline 2424 is configured in a similar manner to the 3D pipeline 2422. A set of media pipeline state commands 2440 are dispatched or placed into the command queue prior to the media object commands 2442. In some embodiments, the media pipeline state commands 2440 include data that configures the media pipeline elements that will be used to process the media objects. This includes data that configures the video decoding and video encoding logic within the media pipeline, such as encoding or decoding formats. In some embodiments, the media pipeline state commands 2440 also support the use of one or more pointers to "indirect" state elements that contain batch state settings.

[0262] In some embodiments, media object commands 2442 supply pointers to media objects for processing by the media pipeline. The media object includes a memory buffer containing video data to be processed. In some embodiments, all media pipeline states must be valid before issuing media object commands 2442. Once the pipeline state is configured and the media object commands 2442 are queued, the media pipeline 2424 is triggered via an execute command 2444 or an equivalent execution event (e.g., a register write). The output from the media pipeline 2424 can then be post-processed by the 3D pipeline 2422 or the operations provided by the media pipeline 2424. In some embodiments, GPGPU operations are configured and executed in a manner similar to media operations.

[0263] Graphics software architecture

[0264] Fig.25The figure illustrates an exemplary graphics software architecture for a data processing system 2500 according to some embodiments. In some embodiments, the software architecture includes a 3D graphics application 2510, an operating system 2520, and at least one processor 2530. In some embodiments, the processor 2530 includes a graphics processor 2532 and one or more general purpose processor cores 2534. The graphics application 2510 and the operating system 2520 are each executed in a system memory 2550 of the data processing system.

[0265] In some embodiments, the 3D graphics application 2510 includes one or more shader programs that include shader instructions 2512. The shader language instructions may be a high-level shader language, such as a high-level shader language (HLSL) or an OpenGL shader language (GLSL). The application also includes executable instructions 2514 in a machine language suitable for execution by a general purpose processor core 2534. The application also includes graphics objects 2516 defined by vertex data.

[0266] In some embodiments, operating system 2520 is a Microsoft® Windows® operating system from Microsoft Corporation, a proprietary UNIX-like operating system, or an open source UNIX-like operating system using a variant of the Linux kernel. When Direct3D API is used, operating system 2520 uses a front-end shader compiler 2524 to compile any shader instruction 2512 in HLSL into a lower-level shader language. Compilation can be just-in-time (JIT) compilation or the application can perform shader precompilation. In some embodiments, high-level shaders are compiled into low-level shaders during the compilation of 3D graphics application 2510.

[0267] In some embodiments, the user mode graphics driver 2526 includes a backend shader compiler 2527 to convert shader instructions 2512 into hardware specific representations. When the OpenGL API is used, the shader instructions 2512 in the GLSL high-level language are passed to the user mode graphics driver 2526 for compilation. In some embodiments, the user mode graphics driver 2526 uses the operating system kernel mode function 2528 to communicate with the kernel mode graphics driver 2529. In some embodiments, the kernel mode graphics driver 2529 communicates with the graphics processor 2532 to dispatch commands and instructions.

[0268] IP Core Implementation

[0269] One or more aspects of at least one embodiment may be implemented by representative code stored on a machine-readable medium, which represents and / or defines logic within an integrated circuit such as a processor. For example, a machine-readable medium may include instructions representing various logics within a processor. When read by a machine, the instructions may cause the machine to manufacture logic for performing the techniques described herein. Such representations, referred to as "IP cores," are reusable units of logic for an integrated circuit that may be stored on a tangible machine-readable medium as a hardware model describing the structure of the integrated circuit. The hardware model may be supplied to various customers or manufacturing facilities, which load the hardware model on a manufacturing machine that manufactures the integrated circuit. The integrated circuit may be manufactured so that the circuit performs the operations described in association with any of the embodiments described herein.

[0270] Fig.26 26 is a block diagram illustrating an IP core development system 2600 that can be used to manufacture an integrated circuit to perform an operation according to an embodiment. The IP core development system 2600 can be used to generate modular, reusable designs that can be incorporated into a larger design or used to build an entire integrated circuit (e.g., a SOC integrated circuit). The design facility 2630 can generate a software simulation 2610 of the IP core design in a high-level programming language (e.g., C / C++). The software simulation 2610 can be used to design, test, and verify the behavior of the IP core. A register transfer level (RTL) design can then be created or synthesized from the simulation model 2600. The RTL design 2615 is an abstraction of the behavior of an integrated circuit that models the digital signal flow between hardware registers including associated logic executed using modeled digital signals. In addition to the RTL design 2615, a low-level design at the logic level or transistor level can also be created, designed, or synthesized. Therefore, the specific details of the initial design and simulation can vary.

[0271] The RTL design 2615 or equivalent may be further synthesized by the design facility into a hardware model 2620, which may be a hardware description language (HDL) or some other representation of physical design data. The HDL may be further simulated or tested to verify the IP core design. The IP core design may be stored using a non-volatile memory 2640 (e.g., a hard disk, flash memory, or any non-volatile storage medium) for delivery to a third-party manufacturing facility 2665. Alternatively, the IP core design may be transmitted via a wired connection 2650 or a wireless connection 2660 (e.g., via the Internet). The manufacturing facility 2665 may then manufacture an integrated circuit based at least in part on the IP core design. The manufactured integrated circuit may be configured to perform operations according to at least one embodiment described herein.

[0272] Fig. 272700, which may be manufactured using one or more IP cores according to an embodiment. The exemplary integrated circuit includes one or more application processors 2705 (e.g., CPUs), at least one graphics processor 2710, and may additionally include an image processor 2715 and / or a video processor 2720, any of which may be modular IP cores from the same or more different design facilities. The integrated circuit includes peripheral or bus logic, which includes a USB controller 2725, a UART controller 2730, an SPI / SDIO controller 2735, and an I 2 S / I 2 C controller 2740. In addition, the integrated circuit may include a display device 2745, which is coupled to one or more high-definition multimedia interface (HDMI) controllers 2750 and mobile industry processor interface (MIPI) display interfaces 2755. Storage can be provided by a flash subsystem 2760 including flash memory and a flash controller. A memory interface can be provided via a memory controller 2765 to access SDRAM or SRAM memory devices. Some integrated circuits additionally include an embedded security engine 2770.

[0273] Additionally, other logic and circuitry may be included in the processor of integrated circuit 2700, including additional graphics processors / cores, peripheral interface controllers, or general purpose processor cores.

[0274] In one example, processor 1110 ( Fig.11 ) outputs the encoded HDR image to the display 1120 ( Fig.11 ), such as about Figure 6A-10 and as described in the examples below.

[0275] Additional Notes and Examples

[0276] Example 1 may include a performance-enhanced computing system, including: a transmitter for outputting a high dynamic range (HDR) image; a memory including a set of instructions; and a processor, wherein when executed by the processor, the instructions cause the system to divide the HDR image into a plurality of regions; determine a brightness level of the HDR image on a per-region basis; and

[0277] An encoding amount is selected for each of the plurality of regions based on a brightness level on a per region basis.

[0278] Example 2 may include a system according to Example 1, wherein the instructions, when executed, cause the computing system to initialize a first threshold and a second threshold, wherein the second threshold is greater than or equal to the first threshold; if the brightness level exceeds the second threshold, reduce the amount of encoding, wherein the reduced amount of encoding is used to reduce image compression; and if the brightness level does not exceed the first threshold, increase the amount of encoding, wherein the increased amount of encoding is used to increase image compression.

[0279] Example 3 may include the system of Example 1, further comprising a codec for encoding a first region of the plurality of regions with a first encoding amount and encoding a second region of the plurality of regions with a second encoding amount.

[0280] Example 4 may include a system according to Example 1, wherein the instructions, when executed, cause the computing system to detect one or more foreground regions among a plurality of regions; and reduce an amount of encoding in the one or more foreground regions, wherein the reduced amount of encoding is used to reduce image compression.

[0281] Example 5 may include a system according to Example 1, wherein the instructions, when executed, cause the computing system to detect one or more background regions among the plurality of regions; and increase the amount of coding in the one or more background regions, wherein the increased amount of coding is used to increase image compression.

[0282] Example 6 may include the system of any of Examples 1-5, wherein the instructions, when executed, cause the computing system to generate a luminance histogram for an HDR image.

[0283] Example 7 may include a semiconductor package device including a substrate; and logic coupled to the substrate, wherein the logic is implemented in one or more of configurable logic or fixed-function hardware logic, the logic being used to divide a high dynamic range (HDR) image into a plurality of regions; determine a brightness level of the HDR image on a per-region basis; and select an encoding amount for each of the plurality of regions based on the brightness level on a per-region basis.

[0284] Example 8 may include a device according to Example 7, wherein the logic is used to initialize a first threshold and a second threshold, wherein the second threshold is greater than or equal to the first threshold; if the brightness level exceeds the second threshold, reduce the amount of encoding, wherein the reduced amount of encoding is used to reduce image compression; and if the brightness level does not exceed the first threshold, increase the amount of encoding, wherein the increased amount of encoding is used to increase image compression.

[0285] Example 9 may include the apparatus of Example 7, wherein the logic is to encode a first region of the plurality of regions with a first amount of encoding; and encode a second region of the plurality of regions with a second amount of encoding.

[0286] Example 10 may include an apparatus according to Example 7, wherein the logic is used to detect one or more foreground regions among the plurality of regions; and reduce the amount of encoding in the one or more foreground regions, wherein the reduced amount of encoding is used to reduce image compression.

[0287] Example 11 may include a device according to Example 7, wherein the logic is used to detect one or more background regions in the plurality of regions; and increase the amount of code in the one or more background regions, wherein the increased amount of code is used to increase image compression.

[0288] Example 12 may include the apparatus of any of Examples 7-11, wherein the logic is to generate a luminance histogram for an HDR image.

[0289] Example 13 may include a method of operating a semiconductor packaging device, comprising: dividing a high dynamic range (HDR) image into a plurality of regions; determining a brightness level of the HDR image on a per-region basis; and selecting an encoding amount for each of the plurality of regions based on the brightness level on a per-region basis.

[0290] Example 14 may include a method according to Example 13, wherein selecting the encoding level includes initializing a first threshold and a second threshold, wherein the second threshold is greater than or equal to the first threshold; if the brightness level exceeds the second threshold, reducing the encoding amount, wherein the reduced encoding amount reduces image compression; and if the brightness level does not exceed the first threshold, increasing the encoding amount, wherein the increased encoding amount increases image compression.

[0291] Example 15 may include the method according to Example 13, further comprising encoding a first region of the plurality of regions with a first encoding amount; and encoding a second region of the plurality of regions with a second encoding amount.

[0292] Example 16 may include the method according to Example 13, further comprising detecting one or more foreground regions among the multiple regions; and reducing the amount of encoding in the one or more foreground regions, wherein the reduced amount of encoding reduces image compression.

[0293] Example 17 may include the method according to Example 13, further comprising detecting one or more background regions in the plurality of regions; and increasing the amount of coding in the one or more background regions, wherein the increased amount of coding increases image compression.

[0294] Example 18 may include a method as in any of Examples 13-17, wherein determining the brightness level comprises generating a brightness histogram for the HDR image.

[0295] Example 19 may include at least one computer-readable storage medium comprising a set of instructions that, when executed by a computing system, cause the computing system to divide a high dynamic range (HDR) image into a plurality of regions; determine a brightness level of the HDR image on a per-region basis; and select an encoding amount for each of the plurality of regions based on the brightness level on a per-region basis.

[0296] Example 20 may include at least one computer-readable storage medium of Example 19, wherein the instructions, when executed, cause the computing system to initialize a first threshold and a second threshold, wherein the second threshold is greater than or equal to the first threshold; if the brightness level exceeds the second threshold, reduce the amount of encoding, wherein the reduced amount of encoding reduces image compression; and if the brightness level does not exceed the first threshold, increase the amount of encoding, wherein the increased amount of encoding increases image compression.

[0297] Example 21 may include at least one computer-readable storage medium of Example 19, wherein the instructions, when executed, cause the computing system to encode a first region of the plurality of regions with a first encoding amount; and encode a second region of the plurality of regions with a second encoding amount.

[0298] Example 22 may include at least one computer-readable storage medium of Example 19, wherein the instructions, when executed, cause a computing system to detect one or more foreground regions among a plurality of regions; and reduce an amount of encoding in the one or more foreground regions, wherein the reduced amount of encoding reduces image compression.

[0299] Example 23 may include at least one computer-readable storage medium of Example 19, wherein the instructions, when executed, cause a computing system to detect one or more background regions among a plurality of regions; and increase an amount of encoding in the one or more background regions, wherein the increased amount of encoding increases image compression.

[0300] Example 24 may include the at least one computer-readable storage medium of any of Examples 19-23, wherein the instructions when executed cause a computing system to generate a luminance histogram for an HDR image.

[0301] Example 25 may include a semiconductor package device comprising a device for dividing a high dynamic range (HDR) image into a plurality of regions; a device for determining a brightness level of the HDR image on a per-region basis; and a device for selecting an encoding amount for each of the plurality of regions based on the brightness level on a per-region basis.

[0302] Example 26 may include an apparatus according to Example 25, wherein the means for selecting the encoding level comprises means for initializing a first threshold and a second threshold, wherein the second threshold is greater than or equal to the first threshold; means for reducing the amount of encoding if the brightness level exceeds the second threshold, wherein the reduced amount of encoding reduces image compression; and means for increasing the amount of encoding if the brightness level does not exceed the first threshold, wherein the increased amount of encoding increases image compression.

[0303] Example 27 may include the apparatus according to Example 25, further comprising a device for encoding a first region of the plurality of regions with a first encoding amount; and a device for encoding a second region of the plurality of regions with a second encoding amount.

[0304] Example 28 may include an apparatus according to Example 25, further comprising a device for detecting one or more foreground regions among a plurality of regions; and a device for reducing an amount of encoding in the one or more foreground regions, wherein the reduced amount of encoding reduces image compression.

[0305] Example 29 may include an apparatus according to Example 25, further comprising a device for detecting one or more background regions among the plurality of regions; and a device for increasing the amount of code in the one or more background regions, wherein the increased amount of code increases image compression.

[0306] Example 30 may include an apparatus according to any of Examples 25-29, wherein the means for determining the brightness level comprises means for generating a brightness histogram for the HDR image.

[0307] The term "coupled" may be used herein to refer to any type of direct or indirect relationship between the components in question, and may apply to electrical, mechanical, fluid, optical, electromagnetic, electromechanical or other connections. In addition, unless otherwise indicated, the terms "first", "second", etc. may be used herein only to facilitate discussion and do not carry a particular time or timing significance. In addition, it should be understood that the indefinite article "a" or "an" carries the meaning of "one or more" or "at least one".

[0308] As used in this application and in the claims, a list of items connected by the term "one or more of..." may mean any combination of the listed items. For example, the phrase "one or more of A, B, or C" may mean A, B, C; A and B; A and C; B and C; or A, B, and C.

[0309] The embodiments have been described above with reference to specific embodiments. However, it will be appreciated by those skilled in the art that various modifications and changes may be made thereto without departing from the broader spirit and scope of the embodiments as set forth in the appended claims. Therefore, the foregoing description and accompanying drawings are to be considered in an illustrative rather than a restrictive sense.

Claims

1. A performance-enhanced computing system, comprising: A transmitter implemented in one or more configurable logic or fixed function hardware logic for outputting a high dynamic range (HDR) image; a memory including a set of instructions; and a processor, wherein when executed by the processor, the instructions cause the system to: dividing the HDR image into a plurality of regions including a brighter region and a darker region each of which is darker than the brighter region; determining a brightness level of the HDR image on a per-region basis, wherein the brightness level of brighter regions is greater than the brightness level of darker regions; and The amount of code is selected for each of the multiple regions on a per-region basis by: an increase in the amount of code when the brightness level is identified as being not greater than a first threshold, wherein the increased amount of code is used to increase image compression, and a reduction in the amount of code when the brightness level is identified as being greater than a second threshold, wherein the second threshold will be greater than the first threshold, wherein the reduced amount of code will reduce image compression; The amount of coding in the brighter area is less than that in the darker area; The regions including the brighter areas and the regions including the darker areas are independently encoded based on their respective brightness levels before being output through the link.

2. The system according to claim 1, further comprising a codec for encoding the lighter region of the plurality of regions with the code amount of the lighter region and encoding the darker region of the plurality of regions with the code amount of the darker region.

3. The system of claim 1 , wherein the instructions, when executed, cause the computing system to: detecting one or more foreground regions from among the plurality of regions; and The amount of coding in one or more foreground regions is reduced, wherein the reduced amount of coding in the one or more foreground regions is used to reduce image compression in the one or more foreground regions.

4. The system of claim 1 , wherein the instructions, when executed, cause the computing system to: detecting one or more background regions from among the plurality of regions; and The amount of code in one or more background regions is increased, wherein the increased amount of code in one or more foreground regions is used to increase image compression in the one or more foreground regions.

5. The system of any one of claims 1-4, wherein the instructions, when executed, cause the computing system to generate a brightness histogram for an HDR image.

6. A semiconductor packaging device comprising: substrate; as well as Logic coupled to the substrate, wherein the logic is implemented in one or more of configurable logic or fixed function hardware logic, the logic being configured to: dividing a high dynamic range (HDR) image into a plurality of regions including a brighter region and a darker region each being darker than the brighter region; determining a brightness level of the HDR image on a per-region basis, wherein the brightness level of brighter regions is greater than the brightness level of darker regions; as well as The amount of code is selected for each of the multiple regions on a per-region basis by: an increase in the amount of code when the brightness level is identified as being not greater than a first threshold, wherein the increased amount of code is used to increase image compression, and a reduction in the amount of code when the brightness level is identified as being greater than a second threshold, wherein the second threshold will be greater than the first threshold, wherein the reduced amount of code will reduce image compression; The amount of coding in the brighter area is less than that in the darker area; The regions including the brighter areas and the regions including the darker areas are independently encoded based on their respective brightness levels before being output through the link.

7. The apparatus of claim 6, wherein the logic is to: encoding a lighter region among the plurality of regions with an encoding amount of the lighter region; and The darker region among the plurality of regions is encoded with the encoding amount of the darker region.

8. The apparatus of claim 6, wherein the logic is to: detecting one or more foreground regions from among the plurality of regions; and The amount of coding in one or more foreground regions is reduced, wherein the reduced amount of coding in the one or more foreground regions is used to reduce image compression in the one or more foreground regions.

9. The apparatus of claim 6, wherein the logic is to: detecting one or more background regions from among the plurality of regions; and The amount of code in one or more background regions is increased, wherein the increased amount of code in the one or more background regions is used to increase image compression in the one or more background regions.

10. The apparatus of any of claims 6-9, wherein the logic is to generate a luminance histogram for an HDR image.

11. A method of operating a semiconductor packaging device, comprising: dividing a high dynamic range (HDR) image into a plurality of regions including a brighter region and a darker region each being darker than the brighter region; determining a brightness level of the HDR image on a per-region basis, wherein the brightness level of brighter regions is greater than the brightness level of darker regions; as well as The amount of code is selected for each of the multiple regions on a per-region basis by: an increase in the amount of code when the brightness level is identified as being not greater than a first threshold, wherein the increased amount of code is used to increase image compression, and a reduction in the amount of code when the brightness level is identified as being greater than a second threshold, wherein the second threshold will be greater than the first threshold, wherein the reduced amount of code will reduce image compression; The amount of coding in the brighter area is less than that in the darker area; The regions including the brighter areas and the regions including the darker areas are independently encoded based on their respective brightness levels before being output through the link.

12. The method according to claim 11, further comprising: encoding a first region among the plurality of regions with a first code amount; as well as A second region among the plurality of regions is encoded with a second code amount.

13. The method according to claim 11, further comprising: detecting one or more foreground regions among the plurality of regions; as well as An amount of encoding in one or more foreground regions is reduced, wherein the reduced amount of encoding in one or more background regions reduces image compression in the one or more background regions.

14. The method according to claim 11, further comprising: detecting one or more background regions among the plurality of regions; as well as An amount of code in one or more background regions is increased, wherein the increased amount of code in the one or more background regions increases image compression in the one or more background regions.

15. The method of any one of claims 11-14, wherein determining the brightness level comprises generating a brightness histogram for the HDR image.

16. A semiconductor packaging device comprising: means for dividing a high dynamic range (HDR) image into a plurality of regions including a brighter region and a darker region each darker than the brighter region; wherein the brightness level of the brighter area is greater than the brightness level of the darker area; means for determining a brightness level of the HDR image on a per-region basis; as well as means for selecting an amount of code for each of a plurality of regions on a per region basis by: an increase in the amount of code when the brightness level is identified as being not greater than a first threshold, wherein the increased amount of code is used to increase image compression, and a reduction in the amount of code when the brightness level is identified as being greater than a second threshold, wherein the second threshold will be greater than the first threshold, wherein the reduced amount of code will reduce image compression; The amount of coding in the brighter area is less than that in the darker area; The regions including the brighter areas and the regions including the darker areas are independently encoded based on their respective brightness levels before being output through the link.

17. The apparatus according to claim 16, further comprising: means for encoding a first region in a plurality of regions with a first code amount; as well as Means for encoding a second region of the plurality of regions with a second code amount.

18. The apparatus of claim 16, further comprising: means for detecting one or more foreground regions among the plurality of regions; as well as Means for reducing the amount of coding in one or more foreground regions, wherein the reduced amount of coding in one or more background regions reduces image compression in the one or more background regions.

19. The apparatus of claim 16, further comprising: means for detecting one or more background regions of the plurality of regions; as well as Means for increasing the amount of code in one or more background regions, wherein the increased amount of code in the one or more background regions increases image compression in the one or more background regions.

20. An apparatus as claimed in any one of claims 16 to 19, wherein the means for determining the brightness level comprises means for generating a brightness histogram for the HDR image.

21. A computer readable medium having instructions thereon which, when executed, cause a computer device to perform a method according to any one of claims 11-15.

Citation Information

Patent Citations

  • Brightness region-based apparatuses and methods for HDR image encoding and decoding

    WO2013144809A2