A flexible multi-user graphics architecture.
The GPU architecture with multiple cores assigned to virtual machines addresses inefficiencies by optimizing resource allocation and performance through dynamic configuration, ensuring efficient graphics processing for multiple applications.
Patent Information
- Application Number
- JP2022515814
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-06-26
- Filing Date
- 2020-09-18
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2040-09-18
AI Technical Summary
Existing graphics processing systems struggle to efficiently manage multiple applications and virtual machines, leading to inefficiencies and resource contention in shared graphics processing units.
A graphics processing unit (GPU) architecture with multiple cores, each assigned to a specific virtual machine, and a hypervisor or GPU virtualization driver that configures and manages these cores for optimal performance and resource allocation based on the number of active applications, ensuring independent operation and efficient utilization.
This approach allows for seamless sharing of GPU resources among multiple virtual machines, enhancing performance and reducing the impact of resource contention, thereby optimizing graphics processing for multiple applications.
Smart Images

Figure 0007588637000001 
Figure 0007588637000002 
Figure 0007588637000003
Abstract
Description
[Technical field]
[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of pending U.S. Provisional Patent Application No. 62 / 905,010, entitled "FLEXIBLE MULTI-USER GRAPHICS ARCHITECTURE," filed on September 24, 2019, and pending U.S. Patent Application No. 16 / 913,562, entitled "FLEXIBLE MULTI-USER GRAPHICS ARCHITECTURE," filed on June 26, 2020, which are hereby incorporated by reference in their entireties. [Background technology]
[0002] Graphics processing hardware accelerates graphics rendering tasks for applications. Server-scale hardware-based rendering is becoming increasingly common, and improvements to such rendering are being made frequently.
[0003] A more detailed understanding can be had from the following description taken in conjunction with the accompanying drawings, in which: [Brief description of the drawings]
[0004] [Figure 1A] FIG. 1 is a block diagram of a cloud gaming system, according to an example. [Figure 1B] FIG. 1 is a block diagram of an example device capable of implementing one or more features disclosed. [Figure 1C] FIG. 13 illustrates details of adding a server, according to an example. [Diagram 2] FIG. 2 is a block diagram illustrating details of a graphics core, according to an example. [Diagram 3] FIG. 3 is a block diagram illustrating additional details of the graphics processing pipeline shown in FIG. [Figure 4] 1 is a flowchart of a method of operating a graphics processor having multiple graphics cores, according to an example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0005] Techniques are provided for operating a processor including multiple cores, the techniques including determining a number of active applications, selecting a processor configuration for the processor based on the number of active applications, configuring the processor according to the selected processor configuration, and executing the active applications with the configured processor.
[0006] 1A is a block diagram of a cloud gaming system 101, according to an example. A server 103 communicates with one or more clients 105. The server 103 executes gaming applications, at least in part using graphics hardware. The server 103 receives inputs, such as button presses and mouse movements, from one or more clients 105. The server 103 provides those inputs to applications running on the server 103, and the server 103 processes the inputs and generates video data for transmission to the client 105. The server 103 transmits this video data to the client 105 for display, and the client 105 displays the video data.
[0007] FIG. 1B is a block diagram of an example device 100 capable of implementing one or more features disclosed herein. In various embodiments, the server 103 and / or the client 105 of FIG. 1A are implemented as the device 100. The server includes a graphics processor 107. In different embodiments, the client 105 may or may not include a graphics processor 107. In various embodiments, the device 100 includes, for example, a computer, a gaming device, a handheld device, a set-top box, a television, a mobile phone, or a tablet computer. The device 100 includes a processor 102, a memory 104, a storage device 106, one or more input devices 108, and one or more output devices 110. The device 100 also includes an optional input driver 112 and an output driver 114. It should be understood that the device 100 may include additional components not shown in FIG. 1B.
[0008] In various alternatives, the processor 102 includes a central processing unit (CPU), a graphics processing unit (GPU), a CPU and a GPU located on the same die, or one or more processor cores, each of which may be a CPU or a GPU. In various alternatives, the memory 104 is located on the same die as the processor 102 or is located separately from the processor 102. The memory 104 includes volatile or non-volatile memory (e.g., random access memory (RAM), dynamic RAM, cache).
[0009] The storage devices 106 include fixed or removable storage devices (e.g., hard disk drives, solid state drives, optical disks, flash drives). The input devices 108 include, but are not limited to, a keyboard, a keypad, a touch screen, a touch pad, a detector, a microphone, an accelerometer, a gyroscope, a biometric scanner, or a network connection (e.g., a wireless local area network card for transmitting and / or receiving wireless IEEE 802 signals). The output devices 110 include, but are not limited to, a display, a speaker, a printer, a haptic feedback device, one or more lights, an antenna, or a network connection (e.g., a wireless local area network card for transmitting and / or receiving wireless IEEE 802 signals).
[0010] The input driver 112 communicates with the processor 102 and the input device 108, allowing the processor 102 to receive input from the input device 108. The output driver 114 communicates with the processor 102 and the output device 110, allowing the processor 102 to send output to the output device 110. The output driver 114 includes a graphics processor 107. The graphics processor 107 is configured to accept graphics rendering commands from the processor 102, process those calculations and the graphics rendering commands, and provide pixel output to a display device for display.
[0011] FIG. 1C illustrates additional details of server 103, according to an example. Processor 102 is configured to support a virtualization scheme in which multiple virtual machines execute on processor 102. Each virtual machine (VM) "appears" to software executing within the VM as a fully "real" hardware computer system, but in reality includes a virtualized computing environment that may share device 100 with other virtual machines. Virtualization may be supported fully in software, partially in hardware, partially in software, or fully in hardware. Graphics processor 107 supports virtualization, which means that graphics processor 107 may be shared across multiple virtual machines executing on processor 102, with each VM "believing" that it has full ownership of the actual hardware graphics processor 107. Graphics processor 107 supports virtualization by assigning a different graphics core 116 of graphics processor 107 to each active guest VM 204. Each graphics core 116 performs graphics operations for its associated guest VM 204 and not for other guest VMs 204.
[0012] Processor 102 supports multiple virtual machines, including one or more guest VMs 204 and, in some embodiments, a host VM 202. Host VM 202 performs one or more aspects related to managing the virtualization of graphics processor 107 for guest VM 204. Hypervisor 206 provides virtualization support for the virtual machines by performing a wide variety of functions, such as managing resources assigned to the virtual machines, spawning and killing virtual machines, handling system calls, managing access to peripheral devices, managing memory and page tables, and various other functions. In some embodiments, host VM 202 provides an interface for an administrator or management software to control configuration operations of graphics processor 107 related to virtualization. In some systems, the functions of host VM 202 described herein are instead performed by hypervisor 206 (which is why GPU virtualization driver 121 is shown with a dotted line in hypervisor 206).
[0013] Host VM 202 and guest VM 204 have operating system 120. Host VM 202 has management application 123 and GPU virtualization driver 121. Guest VM 204 has application 126, operating system 120 and GPU driver 122. These elements control various aspects of the operation of processor 102 and graphics processor 107.
[0014] GPU virtualization driver 121 of host VM 202 is not a traditional graphics driver that simply communicates with graphics processor 107 and sends graphics rendering (or other) commands to graphics processor 107 without understanding the virtualization aspects of graphics processor 107. Instead, GPU virtualization driver 121 communicates with graphics processor 107 to configure various aspects of graphics processor 107 for virtualization. In some examples, in addition to performing configuration functions, GPU virtualization driver 121 issues traditional graphics rendering commands to graphics processor 107 or other commands not directly related to the configuration of graphics processor 107.
[0015] Guest VM 204 includes operating system 120, GPU driver 122, and application 126. Operating system 120 is any type of operating system that executes on processor 102. GPU driver 122 is a "native" driver for graphics processor 107 in that it controls the operation of graphics processor 107 for the guest VM 204 in which it is executing, and sends tasks, such as graphics rendering tasks or other work, to graphics processor 107 for processing. The native driver may be an unmodified or slightly modified version of a device driver for the GPU present in a bare-bones, non-virtualized computing system.
[0016] Although GPU virtualization driver 121 is described as being contained within host VM 202, in other embodiments, GPU virtualization driver 121 may instead be contained within hypervisor 206. In such embodiments, host VM 202 may not be present and the functions of host VM 202 may be performed by hypervisor 206.
[0017] The operating systems 120 of the host VM 202 and guest VMs 204 perform the standard functions of an operating system in a virtualized environment, such as communicating with hardware, managing resources and file systems, managing virtual memory, managing a network stack, and many other functions. The GPU driver 122 controls the operation of the graphics processor 107 for any particular guest VM 204, for example, by providing application programming interfaces (APIs) to software (e.g., applications 126) to access various functions of the graphics processor 107. In some embodiments, the driver 122 includes a just-in-time compiler that compiles programs for execution by the processing components of the graphics core 116 (such as the SIMD unit 138, described in more detail below). For any particular guest VM 204, the GPU driver 122 controls functions for the graphics core 116 associated with that guest VM 204, but not for other VMs.
[0018] Graphics processor 107 includes multiple graphics cores 116 , a shared data fabric 144 , a shared physical interface 142 , a shared cache 140 , a shared multimedia processor 146 , and a shared graphics processor memory 118 .
[0019] The graphics cores 116 of the graphics processor 107 are individually assignable to different guest VMs 204. More specifically, the GPU virtualization driver 121 exclusively assigns a physical graphics core 116 to a particular guest VM 204 for use in performing processing tasks such as graphics processing and computational processing.
[0020] The shared multimedia processor 146, the graphics processor memory 118, the shared cache 140, the shared physical interface 142 and the shared data fabric 144 are all allocable among the different graphics cores.
[0021] The graphics processor memory 118 includes multiple memory portions. In some configurations, the graphics processor memory 118 is divided into portions, each of which is assigned to a different graphics core 116. In such configurations, the GPU virtualization driver 121 assigns a specific portion of the graphics processor memory 118 to a particular graphics core 116. In such configurations, a graphics core 116 can access the portion of the graphics processor memory 118 assigned to that graphics core 116, and a graphics core 116 cannot access the portion of the graphics processor memory 118 that is not assigned to that graphics core 116. In some embodiments, the portions that are assignable to different graphics cores 116 are physical subdivisions of the graphics processing memory 118, such as specific memory banks, etc. In some embodiments, multiple portions of memory are assigned to a single graphics core 116, and in some embodiments, are assigned to all (or multiple) graphics cores 116.
[0022] Shared cache 140 is sharable in that different graphics cores 116 can cache data in any portion of shared cache 140. However, in alternative embodiments, shared cache 140 is configured differently. More specifically, in one embodiment, cache 140 is partitioned into portions, and each portion is assigned to a graphics core 116 (e.g., for exclusive use). In another embodiment, when graphics cores 116 access the same data, the entire cache 140 is shared between graphics cores 116 to reduce external memory traffic. Shared physical interface 142 is an input / output interface to components external to graphics processor 107. Shared physical interface 142 is sharable between graphics cores 116 in that shared physical interface 142 can route data and commands for each graphics core 116 to components external to graphics processor 107. Shared data fabric 114 routes memory transactions between graphics cores 116 and graphics processor memory 118. The shared data fabric 114 is shareable between different graphics cores 116, in that each graphics core 116 interfaces with the shared data fabric 114 to access a portion of the graphics processor memory 118 allocated to that graphics core 116.
[0023] In various configurations, the graphics cores 116 are capable of operating at different performance levels. In some embodiments, one or more of the graphics cores 116 differs from one or more of the other graphics cores 116 in terms of the number of resources physically present within that graphics core. In some examples, those resources include an amount of memory, an amount of cache memory, and / or one or more of a number of compute units 132.
[0024] In some examples, the graphics cores 116 are switchable between different performance levels at run-time. In some embodiments, each graphics core 116 has an adjustable performance level with respect to one or more of a clock speed or a number of components enabled. In some embodiments, a higher clock speed applied to the graphics core 116 or a greater number of components enabled for the graphics core 116 results in a greater power usage for the graphics core 116 and / or a greater amount of heat dissipation for the graphics core 116. Generally, the higher the performance level of the graphics core 116, the greater the power usage and the amount of heat dissipation.
[0025] In some examples, the hypervisor 206 configures the device 103 for use by a particular number of active guest VMs 204. Depending on the number of active guest VMs 204 and the performance requirements of the guest VMs 204, the hypervisor 206 configures different graphics cores 116 performance levels. In some embodiments, the hypervisor 206 identifies a power budget and a thermal budget for the entire graphics processor 107 and sets the performance levels of the enabled graphics cores 116 based on the total power budget and the total thermal budget. Thus, in some embodiments, in a situation where more guest VMs 204 are enabled, the hypervisor 206 sets the performance levels of one or more graphics cores 116 to a lower performance level than in a situation where fewer guest VMs 204 are enabled.
[0026] In some embodiments, graphics processor 107 is switchable between a set of a fixed number of configurations, each of which indicates a number of graphics cores 116 that are enabled and a particular performance level for each enabled graphics core 116.
[0027] In some embodiments, the set of fixed configurations includes at least one configuration in which the first graphics core 116 is enabled and the second graphics core 116 is disabled, and another configuration in which both the first graphics core 116 and the second graphics core 116 are enabled, where in the first configuration the first graphics core has a higher performance level than the first graphics core in the second configuration.
[0028] The graphics processor memory 118 has a certain amount of bandwidth for the graphics core 116. In configurations where multiple graphics cores 116 are enabled, the bandwidth is divided between the different graphics cores 116. When one graphics core 116 is enabled, the graphics core 116 has access to the entire memory bandwidth. In some configurations, each graphics core 116 can access the entire graphics processor memory 118. In some configurations, all of the components of the graphics processor 107 are included on a single die. In some embodiments, each graphics core 116, shared cache 140, shared physical interface 142, shared data fabric 144, shared multimedia processor 146, and graphics processor memory 118 have their own individually adjustable clocks.
[0029] 2 is a block diagram illustrating details of the graphics core 116, according to an example. The graphics core 116 executes commands and programs for selected functions, such as graphics and non-graphics operations that may be suitable for parallel processing. The graphics core 116 may be used to perform graphics pipeline operations, such as pixel operations, geometry calculations, and rendering images to a display device, based on commands received from the processor 102. The graphics core 116 also performs computational processing operations not directly related to graphics operations, such as video-related operations, physics simulations, computational fluid dynamics, or other tasks, based on commands received from the processor 102. The command processor 213 accepts commands from the processor 102 (or another source) and delegates tasks related to those commands to various elements of the graphics core 116, such as the graphics processing pipeline 134 and the computational units 132.
[0030] The graphics core 116 includes a computation unit 132 that includes one or more SIMD units 138 configured to execute operations in parallel according to the SIMD paradigm as required by the processor 102. The SIMD paradigm allows multiple processing elements to share a single program control flow unit and program counter, thus executing the same program, but with different data. In one example, each SIMD unit 138 includes 16 lanes, each lane executing the same instruction simultaneously with other lanes in the SIMD unit 138, but with different data. If not all lanes need to execute a given instruction, the lane may be switched off by conditional execution control (predication). Conditional execution control may also be used to execute a program with branching control flow. More specifically, for a program having instructions such as conditional branches, where the control flow is based on the calculations performed by the individual lanes, the lane corresponding to the control flow path not currently executed may be conditionally executed, and the different control flow paths may be executed serially, allowing arbitrary control flow.
[0031] The basic unit of execution in compute units 132 is a work item. Each work item represents a single instantiation of a program that executes in parallel within a particular lane. Work items may be executed simultaneously as a "wavefront" on a single SIMD processing unit 138. One or more wavefronts are included in a "workgroup," which includes a collection of work items designed to execute the same program. A workgroup may be executed by executing each of the wavefronts that make up the workgroup. In alternative examples, a wavefront may be executed sequentially on a single SIMD unit 138, or may be executed partially or fully in parallel on different SIMD units 138. Scheduler 136 is configured to perform operations related to scheduling various workgroups and wavefronts on different compute units 132 and SIMD units 138.
[0032] The parallelism provided by the computation units 132 is well suited for graphics-related operations such as pixel value calculations, vertex transformations, and other graphics operations. Thus, in some examples, a graphics pipeline 134, which accepts graphics processing commands from the processor 102, provides computation tasks to the computation units 132 for execution in parallel.
[0033] Computation units 132 are also used to perform non-graphics related computational tasks, or computational tasks that are not performed as part of the "normal" operations of graphics pipeline 134 (e.g., custom computations performed to supplement the processing performed on the operations of graphics pipeline 134). Applications 126 or other software executing on processor 102 send programs defining such computational tasks to graphics core 116 for execution.
[0034] As described elsewhere herein, the graphics processor 107 includes multiple graphics cores 116. Each graphics core 116 has its own command processor 213. Thus, each graphics core 116 independently processes the command stream received from the guest VM 204 assigned to that graphics core 116. Thus, the operation of a particular graphics core 116 does not affect the operation of another graphics core 116. For example, if one graphics core 116 becomes unresponsive or experiences a stall or slowdown, the unresponsiveness, stall, or slowdown does not affect a different graphics core 116 within the same graphics processor 107.
[0035] A graphics core 116 is described herein as being associated with and used by a single guest VM 204 in a virtualized computing scheme. However, it should be understood that other embodiments are possible. More specifically, any embodiment in which the server 103 includes multiple independent server-side entities, each of which communicates with a different client 105, each of which is associated with a particular graphics core 116, each of which transmits a command stream to the associated graphics core 116 and transmits the results (e.g., pixels) of such a command stream to the associated client 105, falls within the scope of this disclosure. Generally, such server-side entities are referred to herein as server applications. In some examples, one or more server applications are video games, and the server 103 assigns a different graphics core 116 of the graphics processor 107 to each such video game.
[0036] Further, the configuration of the graphics processor 107 is described herein as being controlled by the hypervisor 206. However, any other component of the server 103 (implemented as hardware, software, or a combination thereof) may instead control the configuration of the graphics processor 107. Generally, such a component is referred to herein as a graphics processor configuration controller.
[0037] Figure 3 is a block diagram illustrating additional details of the graphics processing pipeline 134 shown in Figure 2. The graphics processing pipeline 134 includes stages, each of which performs a specific function. The stages represent subdivisions of the functionality of the graphics processing pipeline 134. Each stage may be implemented partially or fully as a shader program executing within the compute units 132, or partially or fully as non-programmable hardware that is a fixed function external to the compute units 132.
[0038] The input assembler stage 302 reads primitive data from a user-filled buffer (e.g., a buffer filled at the request of software executed by the processor 102, such as application 126) and assembles the data into primitives for use by the rest of the pipeline. The input assembler stage 302 may generate different types of primitives based on the primitive data contained in the user-filled buffer. The input assembler stage 302 formats the assembled primitives for use by the rest of the pipeline.
[0039] The vertex shader stage 304 processes the vertices of the primitives assembled by the input assembler stage 302. The vertex shader stage 304 performs various per-vertex operations, such as transformation, skinning, morphing, per-vertex lighting, etc. Transformation operations include various operations that transform the coordinates of the vertices. These operations include one or more of a modeling transformation, a viewing transformation, a projection transformation, a perspective division, and a viewport transformation. As used herein, such transformations are considered to modify the coordinates or "position" of the vertex on which the transformation is performed. Other operations of the vertex shader stage 304 modify attributes other than coordinates.
[0040] The vertex shader stage 304 is implemented partially or completely as a vertex shader program that executes on one or more compute units 132. The vertex shader program is provided by the processor 102 and is based on a program pre-written by a computer programmer. The driver 122 compiles such a computer program to generate a vertex shader program having a suitable format for execution within the compute units 132.
[0041] The hull shader stage 306, tessellator stage 308, and domain shader stage 310 cooperate to perform tessellation, which converts simple primitives into more complex primitives by subdividing the primitives. The hull shader stage 306 generates patches for tessellation based on input primitives. The tessellator stage 308 generates a set of samples for the patch. The domain shader stage 310 calculates vertex positions for vertices that correspond to the samples for the patch. The hull shader stage 306 and domain shader stage 310 may be implemented as shader programs executing on the compute unit 132.
[0042] The geometry shader stage 312 performs vertex operations for each primitive. A variety of different types of operations may be performed by the geometry shader stage 312, including operations such as point sprint expansion, dynamic particle system operations, fur-fin generation, shadow volume generation, single pass render-to-cubemap, per-primitive material swapping, per-primitive material setup, etc. In some examples, a shader program executing on the compute unit 132 performs the operations for the geometry shader stage 312.
[0043] The rasterizer stage 314 accepts and rasterizes simple primitives and generated upstream. Rasterization consists of determining which screen pixels (or sub-pixel samples) are covered by a particular primitive. Rasterization is performed by fixed function hardware.
[0044] The pixel shader stage 316 calculates output values for screen pixels based on the upstream and rasterization results generated by primitives. The pixel shader stage 316 may apply textures from texture memory. The operations for the pixel shader stage 316 are performed by shader programs executing on the compute units 132.
[0045] The output merger stage 318 accepts the outputs from the pixel shader stage 316, merges them, and performs operations such as Z-testing and alpha blending to determine the final color for the screen pixels.
[0046] 4 is a flow chart of a method 400 of operating a graphics processor 107 having multiple graphics cores 116, according to one example. Although described with respect to the systems of FIGS. 1A-3, one skilled in the art will understand that any system configured to perform the steps of method 400 in any technically feasible order falls within the scope of the present disclosure.
[0047] Method 400 begins at step 402, where a graphics processor configuration controller (e.g., hypervisor 206) determines a number of active server applications (e.g., guest VMs 204). An active server application is a server application configured to require work to be performed by an associated graphics core 116. In some examples, the graphics processor configuration controller receives a request from another entity, such as a workload scheduler of the cloud gaming system, to configure processor 102 to run a particular number of active server applications and the same number of graphics cores 116 of graphics processor 107. In various examples, the request is based on the number of clients 105 using the services of the cloud gaming system.
[0048] At step 404, the graphics processor configuration controller selects a graphics processor configuration based on the number of active server applications. In some examples, the graphics processor configuration controller can vary the performance level of one or more graphics cores 116 based on the number of active server applications, and therefore based on the number of active graphics cores 116. In some examples, the graphics processor configurations differ in that in a configuration in which fewer graphics cores 116 are enabled, more of the available power and thermal budget is available to those fewer graphics cores 116 than in a configuration in which a greater number of graphics cores 116 are enabled. Thus, in a configuration in which fewer graphics cores 116 are enabled, at least one graphics core is given a higher performance level than would the same graphics core 116 be given in a graphics processor configuration in which a greater number of graphics cores 116 are enabled. In various examples, the performance level defines one or more of a clock frequency of the graphics core 116, an amount of memory bandwidth available to the graphics core 116, an amount of memory or cache available for use by the graphics core 116, or other characteristics that define the performance level of the graphics core 116.
[0049] In step 406, the graphics processor configuration controller configures the graphics processor 107 according to the selected graphics processor configuration. In particular, the graphics processor configuration controller enables the graphics cores 116 that are considered enabled according to the selected graphics processor configuration, and sets the performance level of each of the enabled graphics cores 116 according to the selected graphics processor configuration.
[0050] In step 408, the graphics processor configuration controller causes the active server application to be executed with the configured graphics processor 107. Executing the server application includes having the server application forward a stream of commands for processing by the associated graphics core 116 of the graphics processor 107. More specifically, as described elsewhere herein, each server application is assigned a particular graphics core 116. Each server application sends a stream of commands to the graphics core 116 associated with the server application. At any particular graphics core 116, the command processor 213 of that graphics core executes the command stream to process commands and data through the graphics processing pipeline 134 and / or to process computational commands.
[0051] It should be understood that many variations are possible based on the disclosure herein. Although features and elements are described above in a particular combination, each feature or element can be used alone without other features and elements, or in various combinations with or without other features and elements. In some embodiments, the graphics core 116 has been described as including a graphics processing pipeline 134 that includes fixed-function components, but it should be understood that a graphics core 116 having a graphics processing pipeline 134 implemented entirely through shaders without fixed-function hardware, or a graphics core 116 having general-purpose computing capabilities but no graphics processing capabilities, is contemplated herein. In other words, in the present disclosure, the graphics core 116 may be replaced with a graphics core that does not include fixed-function elements (and thus is implemented entirely as a programmable shader program), or may be replaced with a general-purpose computing core that includes a computing unit 132 but does not include a graphics processing pipeline 134 and is capable of performing general-purpose computing operations.
[0052] Any of the disclosed functional blocks may be implemented as hardwired circuitry, software running on a processor, or a combination thereof. The provided methods may be implemented in a general purpose computer, processor, or processor core. Suitable processors include, by way of example, general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application specific integrated circuits (ASICs), field programmable gate array (FPGA) circuits, any other type of integrated circuit (IC), and / or state machines. Such processors may be manufactured by configuring a manufacturing process using the results of hardware description language (HDL) instructions and other intermediate data, including a netlist (instructions that may be stored on a computer readable medium). The results of such processing may be a mask work used in a semiconductor manufacturing process to manufacture a processor implementing features of the present disclosure.
[0053] The methods or flow charts provided herein may be implemented in a computer program, software, or firmware embodied in a non-transitory computer-readable storage medium for execution by a general purpose computer or processor. Examples of non-transitory computer-readable storage media include read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs).
Claims
1. 1. A method of operating a processor including multiple cores, comprising: determining a number of active applications, each active application including an application executing on a second processor, each active application configured to send commands to the processor for execution; selecting a processor configuration for the processor based on the number of active applications, the processor configuration including one active core for each active application; configuring the processor in accordance with the selected processor configuration; and executing the active application using the configured processor. method.
2. The processor configuration indicates a number of active cores of the processor.
2. The method of claim 1.
3. the number of active cores is equal to the number of active applications; The method of claim 2.
4. the processor configuration includes a performance level of the multiple cores of the processor; 2. The method of claim 1.
5. The performance level indicates a clock frequency. The method of claim 4.
6. The processor includes a graphics processor.
2. The method of claim 1.
7. Each core is a graphics core that includes a command processor and a graphics processing pipeline. The method of claim 6.
8. The application is a server application.
2. The method of claim 1.
9. Each application runs on a different virtual machine.
2. The method of claim 1.
10. A system for operating a processor including multiple cores, the processor; a control processor; The control processor includes: determining a number of active applications, each active application including an application executing on a second processor, each active application configured to send commands to the processor for execution; selecting a processor configuration for the processor based on the number of active applications, the processor configuration including one active core for each active application; configuring the processor in accordance with the selected processor configuration; executing the active application with the configured processor; [0023] system.
11. The processor configuration indicates a number of active cores of the processor. The system of claim 10.
12. the number of active cores is equal to the number of active applications; The system of claim 11.
13. the processor configuration includes a performance level of the multiple cores of the processor; The system of claim 10.
14. The performance level indicates a clock frequency. The system of claim 13.
15. The processor includes a graphics processor. The system of claim 10.
16. Each core is a graphics core that includes a command processor and a graphics processing pipeline.
16. The system of claim 15.
17. The application is a server application. The system of claim 10.
18. Each application runs on a different virtual machine. The system of claim 10.
19. A computer-readable storage medium storing instructions, comprising: The instructions, when executed by a first processor, determining a number of active applications, each active application including an application executing on the second processor, each active application configured to send commands to the processor for execution; selecting a processor configuration for the processor based on the number of active applications, the processor configuration including one active core for each active application; configuring the processor in accordance with the selected processor configuration; executing the active application with the configured processor; causing the first processor to operate the processor including a plurality of cores by A computer-readable storage medium.
20. The processor configuration indicates a number of active cores of the processor.
20. The computer readable storage medium of claim 19.
Citation Information
Patent Citations
Processor core hypervisor separation
JP2013516021A
Virtual machine arrangement device and resource management method
JP2017215884A
Information processing system
JP2018072907A
Maximizing Throughput of Multi-user Parallel Data Processing Systems
US20130117168A1
