CN117130774A - Thread acceleration processing method and device - Google Patents

Abstract

The embodiment of the application provides a thread acceleration processing method and device, relates to the field of terminals, and can prevent an application program from being blocked and improve user experience. The method comprises the following steps: firstly, the electronic equipment receives a first operation of a user on an interface of a first application, wherein the first operation is used for triggering the electronic equipment to display target information; then, the electronic equipment acquires a thread identifier of a rendering thread, wherein the rendering thread is used for executing layer rendering to obtain a rendered layer, and the rendered layer corresponds to the target information; the electronic device determines a main thread with a wake-up relation with the rendering thread according to the thread identification of the rendering thread; the electronic device accelerates the rendering thread and the main thread.

Description

Thread acceleration processing method and device

Technical field

The present application relates to the field of terminals, and in particular, to a thread acceleration processing method and device.

Background technique

With the development of electronic technology, electronic devices (such as mobile phones, tablets or smart watches, etc.) have more and more functions. For example, electronic devices are installed with various applications, and the electronic devices can implement various functions through various applications.

Currently, applications running on electronic devices can customize key threads, and key threads can include the main thread and the rendering thread. When the resource allocation of key threads is insufficient, it will cause the application to lose frames and cause lag, resulting in poor user experience. Therefore, how to identify these key threads and schedule resources in time to avoid application lag has become an urgent problem to be solved.

Contents of the invention

Embodiments of the present application provide a thread acceleration processing method and device, which can avoid application lags and improve user experience.

In a first aspect, embodiments of the present application provide a thread acceleration processing method, which is applied to an electronic device, including: the electronic device receives a first operation by a user on an interface of a first application, and the first operation is used to trigger the electronic device to display target information. ; The electronic device obtains the thread identification of the rendering thread, and the rendering thread is used to perform layer rendering to obtain the rendered layer. The rendered layer corresponds to the target information; the electronic device determines that it has a wake-up relationship with the rendering thread based on the thread identification of the rendering thread. The main thread; the electronic device accelerates the rendering thread and the main thread.

Based on the method provided by the embodiments of the present application, after the electronic device receives the first operation for triggering the electronic device to display target information, it can obtain the thread identifier of the rendering thread, and can determine that it has a wake-up relationship with the rendering thread based on the thread identifier of the rendering thread. The main thread is used to accelerate the rendering thread and the main thread, which can avoid frame drops and freezes caused by slow processing speeds of the rendering thread and the main thread, thereby improving the user experience.

In a possible implementation, the acceleration process includes at least one of the following: adjusting the rendering thread and the main thread from the first priority scheduling group to the second priority scheduling group, and scheduling the threads in the second priority scheduling group Threads with a priority higher than the first priority scheduling group; increase the frequency of the rendering thread and the main thread; increase the thread priority of the rendering thread and the main thread. In this way, the electronic device can prioritize the rendering thread and the main thread to perform corresponding tasks, which can avoid frame drops and freezes caused by slow processing speeds of the rendering thread and the main thread, thus improving the user experience.

In a possible implementation, before the electronic device obtains the thread identification of the rendering thread, the method also includes: the electronic device inserts an instrumentation function into the insertion point of the queue function corresponding to the rendering thread; the electronic device obtains the thread identification of the rendering thread. Including: when the electronic device executes the insertion point of the queue function, the instrumentation information is obtained, and the instrumentation information includes the thread identification of the rendering thread. In this way, the electronic device can obtain the thread identifier of the rendering thread through the "instrumentation" method, and then determine the main thread that has a wake-up relationship with the rendering thread based on the thread identifier of the rendering thread, and then accelerate the rendering thread and the main thread, which can avoid Slow processing speeds of the rendering thread and main thread lead to frame drops and freezes, which can improve the user experience.

In one possible implementation, the electronic device determines the main thread that has a wake-up relationship with the rendering thread based on the thread identifier of the rendering thread, including: the electronic device traces the current situation based on the important event information recorded in the current drawing frame cycle, starting from the rendering thread. At least one thread with a wake-up relationship in the frame cycle. Important event information includes wake-up events between threads. The wake-up relationship is used to represent the relationship between wake-up and wake-up between threads; the electronic device is based on the wake-up between at least one thread. The relationship determines at least one target path; the electronic device determines the main thread based on at least one target path, and the main thread is the thread that serves as the end point of the path the most times in at least one target path. In this way, the main thread can be determined, and the main thread can be accelerated to avoid frame drops and freezes caused by slow processing speed of the main thread, thereby improving the user experience.

In a possible implementation, the important event information also includes the identifier of the processor corresponding to the awakened thread, the scheduling group corresponding to the awakened thread, the running time of the awakened thread on the processor, the number of seconds the awakened thread has been running on the processor At least one of the running frequencies, the awakened thread includes the rendering thread and the main thread; the electronic device's acceleration of the rendering thread and the main thread includes: the electronic device, according to the identifier of the processor corresponding to the awakened thread, At least one of the scheduling group, the running time of the awakened thread on the processor, and the running frequency of the awakened thread on the processor accelerates the rendering thread and the main thread. For example, if the scheduling group corresponding to the rendering thread and the main thread is determined to be the first priority scheduling group based on important event information before acceleration processing, the rendering thread and the main thread can be moved from the first priority scheduling group (for example, CFS scheduling group) Adjust to the second priority scheduling group (eg, VIP scheduling group), and the scheduling priority of the threads in the second priority scheduling group is higher than the threads in the first priority scheduling group. The electronic device may preferentially allocate processing resources to threads in the second priority scheduling group. For another example, assume that the frequency of the processor may include 1.0GHz, 1.5GHz, and 2.0GHz. If before acceleration processing, the frequency of the processor corresponding to the rendering thread and the main thread is determined to be 1.0GHz based on important event information, the frequency of the processor corresponding to the rendering thread and the main thread can be increased to 1.5GHz or 2.0GHz, thereby improving the rendering efficiency. The execution efficiency of threads and main threads.

In a possible implementation, the method also includes: when the electronic device traces back to a thread that is interrupted by a kernel thread or a system or woken up by an application thread, the trace is no longer continued.

In a possible implementation, the method further includes: the electronic device compares the thread identifier of the rendering thread with a standard thread identifier; the thread identifier of the rendering thread is different from the standard thread identifier. It can be understood that if the RTID of the currently obtained rendering thread is the same as the RTID in the preset table, it means that the currently obtained rendering thread is a standard rendering thread. Since the standard rendering thread has a corresponding acceleration solution, there is no need to perform acceleration. Blow. This avoids repeated acceleration processing of the standard rendering thread.

In a possible implementation, the thread ID of the rendering thread is a thread ID customized by the first application.

In a possible implementation, the rendering thread includes: at least one of a barrage rendering thread, a navigation rendering thread, a game rendering thread, and a mini program rendering thread. In this way, frame dropping problems in frame-drawing scenarios such as navigation, barrage, games, and mini programs can be avoided, thereby improving the user experience.

In one possible implementation, when the rendering thread is the barrage rendering thread, the rendered layer is the barrage layer; when the rendering thread is the navigation rendering thread, the rendered layer is the navigation layer. ; When the rendering thread is a game rendering thread, the rendered layer is the game layer; when the rendering thread is a mini program rendering thread, the rendered layer is the mini program layer. In this way, frame dropping problems in frame-drawing scenarios such as navigation, barrage, games, and mini programs can be avoided, thereby improving the user experience.

In a possible implementation manner, the rendering thread is used to perform rendering processing on the target information, including: the rendering thread is used to perform layer drawing and layer rendering to obtain a rendered layer. That is, the rendering thread can perform layer drawing and layer rendering.

In a possible implementation, the electronic device includes a rendering thread identification module, a message processing module, a main thread identification module and a key thread acceleration module; the electronic device obtains the thread identifier of the rendering thread including: the rendering thread identification module pre-registers the rendering thread corresponding to The instrumentation function is inserted into the insertion point of the queue function; when the insertion point of the queue function is executed, the rendering thread identification module obtains the instrumentation information, and the instrumentation information includes the thread identification of the rendering thread; the electronic device determines the thread ID of the rendering thread according to the thread ID of the rendering thread. The identification of the main thread that has a wake-up relationship with the rendering thread includes: the rendering thread identification module sends the thread identification of the rendering thread to the message processing module; the message processing module sends the thread identification of the rendering thread to the main thread identification module; the main thread identification module determines the thread identification of the rendering thread according to the rendering thread The thread identification determines the main thread that has a wake-up relationship with the rendering thread; the electronic device accelerates the rendering thread and the main thread according to the thread identification of the rendering thread and the thread identification of the main thread, including: the main thread identification module sends a message to the key thread acceleration module Key thread group information, the key thread group information includes the thread ID of the rendering thread and the thread ID of the main thread; the key thread acceleration module accelerates the key thread group, and the key thread group includes the rendering thread and the main thread. In this way, the electronic device can prioritize the rendering thread and the main thread to perform corresponding tasks, which can avoid frame drops and freezes caused by slow processing speeds of the rendering thread and the main thread, thus improving the user experience.

In a possible implementation, the electronic device also includes a layer processing module and an image synthesis system. Before the electronic device obtains the thread identifier of the rendering thread, the method further includes: in response to the user's operation, the main thread sends a message to the layer processing module. Create a layer request; the layer processing module sends a request to obtain the buffer queue to the image composition system; the image composition system returns the buffer queue corresponding to the layer to the layer processing module; the layer processing module returns the properties of the layer to the main thread information.

In a possible implementation, the method also includes: the main thread requests a vertical synchronization signal from the image synthesis system; the image synthesis system returns the vertical synchronization signal to the main thread; the main thread wakes up the rendering thread; and the rendering thread draws the rendering image.

In a possible implementation, the method also includes: the rendering thread sends a cache request command to the image synthesis system; the image synthesis system sends an instruction to the rendering thread to instruct the cache to dequeue; the rendering thread draws the rendered image into the cache into the buffer queue.

In a second aspect, the present application provides a chip system, which includes one or more interface circuits and one or more processors. The interface circuit and the processor are interconnected through lines. The above chip system can be applied to electronic devices including communication modules and memories. The interface circuit is configured to receive signals from the memory of the electronic device and send the received signals to the processor, the signals including computer instructions stored in the memory. When the processor executes the computer instructions, the electronic device can perform the method described in the first aspect and any possible design manner thereof.

In a third aspect, the present application provides a computer-readable storage medium that includes computer instructions. When the computer instructions are run on an electronic device (such as a mobile phone), the electronic device is caused to execute the method described in the first aspect and any possible design manner thereof.

In a fourth aspect, the present application provides a computer program product, which when the computer program product is run on a computer, causes the computer to execute the method described in the first aspect and any possible design manner thereof.

In the fifth aspect, embodiments of the present application provide a thread acceleration processing device, which includes a processor. The processor is coupled to a memory. The memory stores program instructions. When the program instructions stored in the memory are executed by the processor, the device achieves the above. The method described in the first aspect and any possible design method thereof. The device may be an electronic device or a server device; or may be a component of the electronic device or the server device, such as a chip.

In the sixth aspect, embodiments of the present application provide a thread acceleration processing device. The device can be divided into different logical units or modules according to functions, and each unit or module performs different functions, so that the device performs the above-mentioned first step. Aspects and methods described in any possible design method.

It can be understood that the chip system described in the second aspect, the computer-readable storage medium described in the third aspect, the computer program product described in the fourth aspect, and the devices described in the fifth and sixth aspects provided above are The beneficial effects that can be achieved can be referred to the beneficial effects in the first aspect and any possible design method thereof, which will not be described again here.

Based on the method provided by the embodiments of the present application, after the electronic device receives the first operation for triggering the electronic device to display target information, it can obtain the thread identifier of the rendering thread, and can determine that it has a wake-up relationship with the rendering thread based on the thread identifier of the rendering thread. The main thread is used to accelerate the rendering thread and the main thread, which can avoid frame drops and freezes caused by slow processing speeds of the rendering thread and the main thread, thereby improving the user experience.

Description of the drawings

Figure 1 is a schematic diagram of an interface display processing flow in the prior art;

Figure 2 is a schematic diagram of an interface display in the prior art;

Figure 3 is a schematic diagram of an interface display processing flow in the prior art;

Figure 4 is a schematic diagram of an interface display in the prior art;

Figure 5 is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application;

Figure 6 is a schematic diagram of the software architecture of an electronic device provided by an embodiment of the present application;

Figure 7 is a schematic diagram of an applicable scenario provided by the embodiment of the present application;

Figure 8 is a schematic diagram of interaction between modules provided by an embodiment of the present application;

Figure 9 is a schematic diagram of a layer provided by an embodiment of the present application;

Figure 10 is a schematic diagram of the relationship between a rendering thread, a queue function and an instrumentation function provided by an embodiment of the present application;

Figure 11 is a schematic diagram of a wake-up relationship between threads provided by an embodiment of the present application;

Figure 12 is a schematic diagram of another wake-up relationship between threads provided by an embodiment of the present application;

Figure 13 is a schematic diagram of an acceleration process provided by an embodiment of the present application;

Figure 14 is a schematic diagram of another acceleration process provided by the embodiment of the present application;

Figure 15 is a schematic diagram of an interface display processing flow provided by an embodiment of the present application;

Figure 16 is a schematic diagram of an interface display provided by an embodiment of the present application;

Figure 17 is a schematic structural diagram of a chip system provided by an embodiment of the present application.

Detailed ways

In order to describe the following embodiments clearly and concisely, a brief introduction to related concepts or technologies is first given:

Frame: refers to the smallest unit of a single picture in the interface display. A frame can be understood as a still picture, and displaying multiple connected frames in rapid succession can create the illusion of object movement. The frame rate refers to the number of frames that refresh the picture in one second. It can also be understood as the number of times the graphics processor in the terminal device refreshes the picture per second. A high frame rate results in smoother and more realistic animations. The more frames per second, the smoother the action shown will be.

It should be noted that the interface usually needs to go through processes such as drawing, rendering, and synthesis before displaying frames.

Frame drawing: refers to the picture drawing of the display interface. The display interface can be composed of one or more views. Each view can be drawn by the visual control of the view system. Each view is composed of subviews. One subview corresponds to a widget in the view. For example, one of the subviews corresponds to the picture view. a symbol in .

Frame rendering: It is to perform coloring operations on the drawn view or add 3D effects, etc. For example: 3D effects can be lighting effects, shadow effects, texture effects, etc.

Frame synthesis: It is the process of synthesizing multiple rendered views of one or more of the above into a display interface.

Thread: A thread is the smallest unit that the operating system can perform operation scheduling. It is included in the process and is the actual operating unit in the process. A thread refers to a single sequential control flow in a process. Multiple threads can run concurrently in a process, and each thread performs different tasks in parallel. Threads are the basic unit of independent scheduling and dispatch. The thread can be a kernel thread scheduled by the operating system kernel; it can also be a user thread scheduled by the user process; or a thread scheduled by a mixture of kernel and user processes.

Rendering thread: A thread used to perform frame drawing and/or frame rendering.

Main thread: The thread used to create or wake up the rendering thread.

Currently, applications running on electronic devices can customize key threads, and key threads can include the main thread and the rendering thread. When the resource allocation of these key threads is insufficient, it will cause the application to lose frames and cause lag, resulting in poor user experience. Therefore, how to identify these key threads and schedule resources in time to avoid application lag has become an urgent problem to be solved.

For example, FIG. 1 is a schematic diagram of a barrage display processing flow of an electronic device. In chronological order, the content displayed by the electronic device corresponds to frame 1, frame 2, and frame 3. Electronic devices can display based on vertical synchronization (Vsync) signals to synchronize processes such as image drawing, rendering, synthesis, and screen refresh display.

Taking the display of frame 1 as an example, first, the main thread corresponding to the barrage layer of the video application can draw frame 1, and the rendering thread (for example, thread 205) corresponding to the barrage layer of the video application can draw frame 1. render. After the drawing and rendering of frame 1 is completed, the rendering thread of the electronic device sends the rendered frame 1 to the image synthesis system (for example, SurfaceFlinger, SF). The image synthesis system synthesizes the rendered frame 1. After frame 1 is synthesized, the electronic device can start the display driver by calling the kernel layer to display the content corresponding to frame 1 on the screen (display). Frame 3 is also synthesized and displayed in a process similar to that of frame 1, which will not be described again here. It should be noted that the rendering thread (thread 205) is in the running state for a long time when rendering frame 1 and frame 3, so frame 1 and frame 3 can be rendered smoothly (the frames can be completed within one Vsync cycle respectively). 1 or frame 3) and sent to the image composition system. However, when the rendering thread (thread 205) renders frame 2, because the rendering thread (thread 205) is in the waiting execution (Runnable) state for a long time, the rendering of frame 2 cannot be completed in one Vsync cycle, and it needs to be executed in multiple Vsync cycles. The rendering was completed within the cycle, resulting in frame 2 being unable to be synthesized and displayed in time, which in turn caused the barrage to freeze.

For example, as shown in Figure 2, the electronic device can be a mobile phone, and the mobile phone can run a video application. As shown in (a) of Figure 2, the mobile phone can display a video interface 1001, and the video interface 1001 can include barrage 1002, barrage 1004, video characters 1003, and other video content (for example, cliff). Danmaku (danmaku 1002, barrage 1004) can be scrolled and displayed along with the video playback progress.

During video playback, if the resource allocation of the key threads of the barrage layer (for example, the rendering thread) is insufficient, the barrage will freeze. As shown in (b) of Figure 2, as the video playback progress changes, the mobile phone can switch from the video interface 1001 to the video interface 1005, and the video content changes, for example, the display position of the video character 1003 changes. However, barrage 1002 and barrage 1004 are still displayed in their original positions, that is, the barrage display is stuck, which affects the user experience.

As another example, FIG. 3 is a schematic diagram of a display processing flow of a map application of an electronic device. In chronological order, the content displayed by the electronic device corresponds to frame 1, frame 2, and frame 3. Electronic devices can display based on Vsync signals to synchronize processes such as image drawing, rendering, synthesis, and screen refresh display.

For the main thread and rendering thread (for example, thread GL MAP) corresponding to the navigation layer of the map application, the drawing, rendering and synthesis process of frame 1 and frame 2 can refer to the relevant description in Figure 1. It should be noted that when the rendering thread (for example, thread GL MAP) corresponding to the navigation layer renders frame 1 and frame 2, the rendering thread (thread GL MAP) is in the running state for a long time, so the frame can be rendered smoothly. 1 and frame 2 and sent to the image synthesis system. However, when the rendering thread (thread 205) renders frame 3, because the rendering thread (thread GL MAP) is in the waiting execution (Runnable) state for a long time, that is, the rendering thread (thread GL MAP) has insufficient resource allocation, resulting in the rendering thread (Thread GL MAP) cannot complete the rendering of frame 3 in time (the rendering of frame 3 cannot be completed in one Vsync cycle and needs to be completed in multiple Vsync cycles), resulting in the failure of frame 3 to be synthesized and displayed in time, which in turn causes the display of the map application The interface is stuck.

For example, as shown in Figure 4, the electronic device can be a mobile phone, and the mobile phone can run a map application. As shown in (a) of FIG. 4 , the mobile phone may display a route selection interface 4001 , and the route selection interface 4001 may include a start walking navigation control 4002 . In response to the user clicking to start the operation of the walking navigation control 4002, if the resource allocation of the key thread (for example, the rendering thread) corresponding to the walking navigation layer is insufficient, as shown in (b) of Figure 4, the map application will freeze and display Interface lag 4003, the walking navigation interface cannot be displayed in time, affecting the user experience.

In related technologies, the standard main thread (UIThread) and rendering thread (RenderThread) have fixed thread names, which can be identified and accelerated by the thread name. For example, The main thread name is cent.tmgp.sgame,/> The main thread name is tv.danmaku.bili. The main thread can be used to speed up processing when creating application processes. The name of the rendering thread may be, for example, RenderThread. You can traverse all threads under the application process, identify the rendering thread by thread name and accelerate processing.

However, application-customized main threads, rendering threads, etc. cannot be recognized and accelerated because the thread names are not fixed. For example, the custom rendering threads Thread-205 and GL-Map of the video application and map application mentioned above cannot be recognized and accelerated because the thread names are not fixed.

Embodiments of the present application provide a thread acceleration processing method and device, which can accurately identify key threads customized by the application program for drawing frames based on the actual running status of the application program. The key threads may include the main thread and the rendering thread. In addition, resource allocation and acceleration can be performed on the identified key threads on demand, reducing frame loss, avoiding application lags, and improving user experience.

Embodiments of the present application can be applied to frame-drawing scenarios such as sliding, navigation, barrage, games, and applets (for example, WebView applets), and can avoid errors in frame-drawing scenarios such as sliding, navigation, barrage, games, and WebView applets. Frame loss problem to improve user experience.

FIG. 5 is a schematic structural diagram of an electronic device 100 provided by an embodiment of the present application.

As shown in FIG. 5 , the electronic device 100 may include a processor 110 , an external memory interface 120 , an internal memory 121 , a universal serial bus (USB) interface 130 , a charging management module 140 , a power management module 141 , and a battery 142 , Antenna 1, Antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193 , display screen 194, and subscriber identification module (subscriber identification module, SIM) card interface 195, etc.

Among them, the sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and an environment. Light sensor 180L, bone conduction sensor 180M, etc.

It can be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 100 . In other embodiments, the electronic device 100 may include more or fewer components than illustrated, some components may be combined, some components may be separated, or components may be arranged differently. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), an image signal processor ( image signal processor (ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (NPU), etc. . Among them, different processing units can be independent devices or integrated in one or more processors.

The controller may be the nerve center and command center of the electronic device 100 . The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuitsound, I2S) interface, a pulse code modulation (PCM) interface, and a universal asynchronous receiver (universal asynchronous receiver) /transmitter, UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface, and/or Universal serial bus (USB) interface, etc.

It can be understood that the interface connection relationships between the modules illustrated in this embodiment are only schematic illustrations and do not constitute a structural limitation of the electronic device 100 . In other embodiments, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The charging management module 140 is used to receive charging input from the charger. While the charging management module 140 charges the battery 142, it can also provide power to the electronic device through the power management module 141.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, internal memory 121, external memory, display screen 194, camera 193, wireless communication module 160, etc. In some other embodiments, the power management module 141 may also be provided in the processor 110 . In other embodiments, the power management module 141 and the charging management module 140 may also be provided in the same device.

The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example: Antenna 1 can be reused as a diversity antenna for a wireless LAN.

The mobile communication module 150 can provide solutions for wireless communication including 2G/3G/4G/5G applied on the electronic device 100 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, perform filtering, amplification and other processing on the received electromagnetic waves, and transmit them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves through the antenna 1 for radiation.

A modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs sound signals through audio devices (not limited to speaker 170A, receiver 170B, etc.), or displays images or videos through display screen 194.

The wireless communication module 160 can provide applications on the electronic device 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (bluetooth, BT), and global navigation satellite system. (global navigation satellite system, GNSS), frequency modulation (FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (codedivision multiple access, CDMA), broadband code Wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM , and/or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou satellite navigation system (beidounavigation satellite system, BDS), quasi-zenith satellite system (quasi- zenith satellitesystem (QZSS) and/or satellite based augmentation systems (SBAS).

The electronic device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is an image processing microprocessor and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can use a liquid crystal display (LCD), a light-emitting diode (LED), an organic light-emitting diode (OLED), an active matrix organic light-emitting diode or an active matrix Organic light-emitting diode (active-matrix organic light emitting diode, AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light emitting diode (QLED) )wait.

The electronic device 100 can implement the shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like. The ISP is used to process the data fed back by the camera 193. Camera 193 is used to capture still images or video. Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. In this way, the electronic device 100 can play or record videos in multiple encoding formats, such as moving picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The cameras 193 may include 1 to N cameras. For example, the electronic device may include 2 front cameras and 4 rear cameras. NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can continuously learn by itself. Intelligent cognitive applications of the electronic device 100 can be implemented through the NPU, such as image recognition, face recognition, speech recognition, text understanding, etc.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100 . The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card. Internal memory 121 may be used to store computer executable program code, which includes instructions. The processor 110 executes instructions stored in the internal memory 121 to execute various functional applications and data processing of the electronic device 100 . For example, in the embodiment of the present application, the processor 110 can execute instructions stored in the internal memory 121, and the internal memory 121 can include a program storage area and a data storage area. Among them, the stored program area can store an operating system, at least one application program required for a function (such as a sound playback function, an image playback function, etc.). The storage data area may store data created during use of the electronic device 100 (such as audio data, phone book, etc.). In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (UFS), etc.

The electronic device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playback, recording, etc.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. Audio module 170 may also be used to encode and decode audio signals. Speaker 170A, also called "speaker", is used to convert audio electrical signals into sound signals. Receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals. Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. The headphone interface 170D is used to connect wired headphones.

The buttons 190 include a power button, a volume button, etc. Key 190 may be a mechanical key. It can also be a touch button. The electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100 . The motor 191 can generate vibration prompts. The motor 191 can be used for vibration prompts for incoming calls and can also be used for touch vibration feedback. The indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, or may be used to indicate messages, missed calls, notifications, etc. The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195 . The electronic device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. SIM card interface 195 can support Nano SIM card, Micro SIM card, SIM card, etc.

The methods in the following embodiments can all be implemented in the electronic device 100 with the above hardware structure.

The software system of the above-mentioned electronic device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. This embodiment of the present invention takes the Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100 .

The layered architecture divides the software into several layers, and each layer has clear roles and division of labor. The layers communicate through interfaces. In some embodiments, the Android system may include an application layer, an application framework layer, a kernel layer and a hardware layer. It should be noted that the embodiments of the present application are illustrated by taking the Android system as an example. In other operating systems (such as Hongmeng system, IOS system, etc.), as long as the functions implemented by each functional module are similar to those of the embodiments of the present application, the present application can also be implemented. plan.

Among them, the application layer can include a series of application packages.

As shown in Figure 6, application packages can include videos, games, maps, WLAN, music, short messages, galleries, calls, navigation, etc. Of course, the application layer may also include other application packages, such as Bluetooth, calendar, camera, settings and other applications, which are not limited in this application.

The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions. For example, it may include an activity manager, a window manager, a content provider, a view system, a resource manager, a notification manager, etc. This embodiment of the present application does not impose any restrictions on this.

In the embodiment of this application, the application framework layer may also include a layer processing module, an image synthesis system, a rendering thread identification module, etc.

Among them, the layer processing module can perform layer creation, layer drawing and other processing.

The image synthesis system is used to control image synthesis and generate vertical synchronization (veticalsynchronization, Vsync) signals.

The rendering thread identification module is used to identify rendering threads in the current drawing frame cycle, which may include rendering thread 1 and rendering thread 2, for example.

The kernel layer is the layer between hardware and software. The kernel layer contains at least a display driver, camera driver, audio driver, and sensor driver (not shown in the figure). The kernel layer can also include real time (RT) scheduler, VIP (very important person, VIP) scheduler, completely fair scheduler (CFS) scheduler/energy aware scheduler (EAS) scheduler, etc. .

In the embodiment of this application, the kernel layer may also include a message processing module, a main thread identification module, and a key thread acceleration module.

The message processing module is used to receive notification messages from the rendering thread identification module. The notification message may include the thread identifier of the rendering thread identified by the rendering thread identification module. The message processing module may send the thread identification of the rendering thread to the main thread identification module.

The main thread identification module can trace the awakening relationship between the threads running in the current drawing frame cycle and the rendering thread based on the important event information recorded in the current drawing frame cycle. Then based on the wake-up relationship between the thread running in the current drawing frame cycle and the rendering thread, the main thread in the current drawing frame cycle is determined. The main thread identification module may send the thread identification of the rendering thread and the thread identification of the main thread to the key thread acceleration module. The thread identity of the rendering thread may be, for example, RTID (renderthread identity), and the thread identity of the main thread may be, for example, UTID (user interface threadidentity).

The key thread acceleration module can allocate resources to the rendering thread and the main thread based on the RTID of the rendering thread and the UTID of the main thread to achieve accelerated processing of the rendering thread and the main thread.

The hardware layer includes central processing unit/processor (CPU), GPU, double data rate synchronous dynamic random access memory (double data rate SDRAM (synchronous dynamic random-access memory), DDR SDRAM), etc. Of course, the hardware layer can also include other hardware, such as displays, cameras, etc.

The Android system may also include other layers (not shown in the figure), such as Android runtime and system libraries, hardware abstraction layer (HAL), etc., which are not limited in this application.

System libraries can include multiple functional modules. For example: surface manager (surface manager), media libraries (Media Libraries), 3D graphics processing library (for example: OpenGL ES), 2D graphics engine (for example: SGL), etc.

The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

OpenGL ES is used to implement three-dimensional graphics drawing, image rendering, composition, and layer processing.

SGL is a drawing engine for 2D drawing.

Android Runtime includes core libraries and virtual machines. The Android runtime is responsible for the scheduling and management of the Android system. The core library contains two parts: one is the functional functions that need to be called by the Java language, and the other is the core library of Android. The application layer and application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and application framework layer into binary files. The virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions.

The HAL layer encapsulates the Linux kernel driver, provides an interface upwards, and shields the implementation details of the low-level hardware.

The following describes the software modules involved in the thread acceleration processing method provided by the embodiment of the present application and the interaction between the modules.

As shown in Figure 6, the rendering thread identification module can identify the rendering threads in the current drawing frame cycle, which may include rendering thread 1 and rendering thread 2, for example. After the rendering thread identification module identifies the rendering thread in the current drawing frame cycle, it can send a notification message to the message processing module of the kernel layer through a system call. The notification message can include the RTID of the rendering thread identified by the rendering thread identification module. The message processing module can send the RTID of the rendering thread to the main thread identification module. The main thread identification module can trace the awakening relationship between the threads running in the current drawing frame period and the rendering thread based on the important event information recorded in the current drawing frame period. Then based on the wake-up relationship between the thread running in the current drawing frame cycle and the rendering thread, the main thread in the current drawing frame cycle is determined. Then, the main thread identification module can send the RTID of the rendering thread and the UTID of the main thread to the key thread acceleration module. The key thread acceleration module can allocate resources between the rendering thread and the main thread based on the RTID of the rendering thread and the UTID of the main thread to achieve Accelerate processing of the rendering thread and the main thread to avoid the problem of application lag caused by frame loss, which can improve the user experience.

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

Among them, in the description of this application, various terms and English abbreviations, such as wake-up relationship, target path, frame period, etc., are illustrative examples given for convenience of description and should not constitute any limitation on this application. This application does not exclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

Among them, in the description of this application, unless otherwise specified, "at least one" refers to one or more, and "plurality" refers to two or more than two. In addition, in order to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as “first” and “second” are used to distinguish identical or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the number and execution order, and words such as "first" and "second" do not limit the number and execution order.

The application scenarios provided by the embodiments of the present application are illustrated below with reference to the accompanying drawings.

For example, as shown in (a) of FIG. 7 , the electronic device may receive the user's operation to start playing (for example, the user's operation of clicking the play button 702 ) on the video playback interface 701 of the video application, and the electronic device responds to the user's operation. The operation performs frame drawing, rendering, synthesis and other processes to display video content and barrage content.

As shown in (b) of FIG. 7 , the electronic device can receive the user's operation to start navigation (for example, the user clicks the start walking navigation button 704 ) on the route selection interface 703 of the map application, and the electronic device responds to the user's operation. Frame drawing, rendering, synthesis and other processes are used to display the walking navigation interface.

As shown in (c) in Figure 7, electronic devices can The display interface 705 receives the user's operation of opening the applet (for example, the user's operation of clicking the applet entrance 706). The electronic device responds to the user's operation by performing processes such as frame drawing, rendering, and synthesis to display the interface of the applet.

As shown in (d) of Figure 7 , the electronic device can receive the user's sliding operation (for example, the user's sliding up or sliding down operation) on the display interface 707 of the gallery application, and the electronic device performs frame drawing in response to the user's operation. , rendering, synthesis and other processes to display the sliding interface.

It should be understood that the application scenarios provided by the embodiments of the present application may also include other interfaces of other applications, and the user's operations may also include other operations (for example, double-click, triple-click, etc.). The operation is not specifically limited.

For ease of understanding, the interaction process between various modules involved in the thread acceleration processing method provided by the embodiment of the present application will be described below with reference to FIG. 8 .

Among them, the modules involved in the data processing method provided by the embodiment of the present application may include: the main thread and rendering thread of the application program, the layer processing module of the application framework layer, the image synthesis system (Surfaceflinger), the rendering thread identification module, the kernel layer Message processing module, main thread identification module and key thread acceleration module.

801. The electronic device receives the user's first operation on the interface of the first application. In response to the first operation, the main thread of the first application sends a create layer request to the layer processing module of the application framework layer.

The first application may include video applications, navigation applications, social networking applications, search engine applications, etc., which are not limited in this application.

The first operation is used to trigger the electronic device to display the target information. Target information may include, for example, barrage information, navigation information, game information, mini-program information, etc. The first operation may include click, slide and other operations, which are not limited in this application.

Exemplarily, taking the first application as a video application, as shown in (a) of Figure 7 , in response to the user clicking the play button 702 (an example of the first operation), the main thread of the video application can Send a layer creation request to the application framework layer layer processing module. The layer creation request may include the layer object and the ID of the buffer queue corresponding to the layer.

For example, as shown in (a) of Figure 9 , the layer to be created may include a barrage layer, and as shown in (b) of Figure 9 , the layer to be created may include a video layer. Of course, the layers to be created may also include other layers, such as program window layers, station logo layers, etc., which are not limited in this application.

802. The layer processing module of the application framework layer sends a request to obtain the buffer queue (BufferQueue) to Surfaceflinger.

Among them, the Get BufferQueue request is used to request Surfaceflinger to allocate a BufferQueue for the layer. Get the ID of the buffer queue corresponding to the layer that can be carried in the BufferQueue request.

803. Surfaceflinger returns the BufferQueue corresponding to the layer to the layer processing module.

It is understandable that different layers can correspond to different BufferQueue.

For example, the barrage layer can correspond to BufferQueue 1, and BufferQueue 1 can include one or more buffers. The video layer can correspond to BufferQueue 2, and BufferQueue 2 can include one or more buffers. BufferQueue1 is different from BufferQueue2.

804. The layer processing module returns the attribute information of the layer to the main thread.

Among them, the attribute information of the layer includes but is not limited to height, width, center coordinates, scaling attributes, rotation attributes, etc.

805. The main thread requests the Vsync signal from Surfaceflinger.

Among them, the Vsync signal can be Vsync-APP, and Vsync-APP is used to trigger the drawing and rendering process.

806. Surfaceflinger returns the Vsync signal to the main thread.

After the main thread receives the Vsync signal, it can calculate the frame interval based on the timestamp of the Vsync signal. For example, the main thread can calculate the difference between the timestamp of the Vsync-APP signal received this time and the timestamp of the Vsync-APP signal received last time. The difference is the frame interval corresponding to the previous frame rendering. The main thread can also calculate the displacement, which is the product of the frame interval and the speed. The main thread can determine the speed based on a pre-stored speed profile.

807. The main thread wakes up the rendering thread.

The main thread can send the frame interval and the displacement of the current frame to the rendering thread to wake up the rendering thread. After the rendering thread is awakened, it starts drawing the rendered image.

It should be noted that the name of the rendering thread of the application (first application) may be customized by the application. For example, a video application can customize the name of the rendering thread of the barrage layer to be thread 205. For another example, the navigation application can customize the name of the rendering thread of the navigation layer to be thread 205.

808. The rendering thread draws the rendering image.

The rendering thread is used to perform layer rendering to obtain a rendered layer, which corresponds to the target information.

For example, when the rendering thread is a barrage rendering thread, the rendered layer is a barrage layer; when the rendering thread is a navigation rendering thread, the rendered layer is a navigation layer; the rendering thread is In the case of the game rendering thread, the rendered layer is the game layer; in the case of the rendering thread being the applet rendering thread, the rendered layer is the applet layer.

809. The rendering thread sends a request cache command to Surfaceflinger.

Among them, the request cache command is used to request cache from Surfaceflinger to store the rendered image.

810. Surfaceflinger sends an instruction to the rendering thread to instruct the cache to dequeue.

After receiving the request cache command sent by the rendering thread, Surfaceflinger can reserve space to store the rendered image and send an instruction to the rendering thread to instruct the cache to dequeue.

811. The rendering thread stores the rendered image in the buffer queue.

After the rendering thread receives the instruction to instruct the cache to dequeue, it draws the rendered image according to the displacement, and stores the drawn and rendered image into the buffer queue (BufferQueue) by calling the queue (queueBuffer) function. The buffer queue can also be called a cache queue, which is not limited in this application.

Further, the rendering thread notifies Surfaceflinger to read rendering data from the BufferQueue. Surfaceflinger can synthesize rendering data. After the synthesis is completed, the electronic device can start the display driver by calling the kernel layer to display the content corresponding to the rendered synthesized frame on the screen (display screen).

812. The rendering thread identification module obtains rendering thread information.

In this embodiment of the present application, the electronic device can obtain the thread identifier of the rendering thread through the rendering thread identification module. The rendering thread identification module can "instrument" in the queue (queueBuffer) function, that is, insert the instrumentation function into the insertion point of the queueBuffer function in advance. When the insertion point of the queueBuffer function is executed, the instrumentation function is executed, and then the instrumentation function can be executed. Get the thread ID of the rendering thread in real time. Among them, the queueBuffer function is used to submit the rendered image, that is, to fill the rendered image into the buffer queue (BufferQueue).

For example, as shown in Figure 10, after the rendering thread is awakened by the main thread, it can perform a frame rendering operation to obtain rendering data. For example, the rendering thread can perform a rendering operation on frame 1 in the previous Vsync cycle to obtain rendering data and store it in the buffer queue. In the next Vsync cycle, the rendering operation is performed on frame 2 to obtain the rendering data and stored in the buffer queue. When the rendering thread stores rendering data into the buffer queue, the thread ID of the rendering thread can be obtained in real time through the instrumentation function inserted into the insertion point of the buffer queue.

In one possible design, the electronic device can filter the thread identifier of the rendering thread obtained through "instrumentation". For example, the electronic device may compare the currently obtained RTID of the rendering thread with the RTID in the preset table. Among them, the name of the standard thread is stored in the preset table. If the RTID of the currently obtained rendering thread is the same as the RTID in the preset table, then the currently obtained rendering thread is filtered, and there is no need to trace and accelerate the currently obtained rendering thread, that is, the following steps 813-817 are not performed. . If the currently obtained RTID of the rendering thread is different from the RTID in the preset table, the currently obtained rendering thread is traced and accelerated, that is, the following steps 813-817 are continued.

It can be understood that if the RTID of the currently obtained rendering thread is the same as the RTID in the preset table, it means that the currently obtained rendering thread is a standard rendering thread. Since the standard rendering thread has a corresponding acceleration scheme, there is no need to execute it again. Steps 813-817 are described below. This avoids repeated acceleration processing of the standard rendering thread.

813. The rendering thread identification module sends the rendering thread information to the message processing module of the kernel layer.

The rendering thread information may include the RTID of the rendering thread.

814. The message processing module sends the rendering thread information to the main thread identification module.

After receiving the rendering thread information, the message processing module of the kernel layer can send the rendering thread information to the main thread identification module.

815. The main thread identification module determines the main thread that has a wake-up relationship with the rendering thread according to the thread identifier of the rendering thread.

In one possible design, the main thread identification module can trace the wake-up relationship between the threads running in the current draw frame cycle and the rendering thread based on the important event information recorded in the current draw frame cycle, and determine the main thread based on the wake-up relationship.

The current drawing frame period may refer to the time between the execution time of the queueBuffer function corresponding to the current frame (for example, frame 1) and the execution time of the queueBuffer function corresponding to the next frame (for example, frame 2). Alternatively, the current frame period may refer to the time between the Vsync signal corresponding to the current frame (eg, frame 1) and the Vsync signal corresponding to the next frame (eg, frame 2).

In each frame cycle, the electronic device can execute multiple threads, and during the execution of the multiple threads, the electronic device can record important event information. The electronic device can record important event information through the scheduling event collection module of the kernel layer, and the main thread identification module can obtain important event information from the scheduling event collection module. Among them, important event information may include wake-up events between threads. Wake-up events between threads can include a running thread waking up a sleeping thread, a running thread creating a thread and waking up the created thread.

For example, the main thread identification module of the electronic device can obtain the sleeping thread awakened by the running thread through the wake-up parameter/function (such as SCHED_WAKING), and can obtain the running thread through the wake-up new thread parameter/function (such as SCHED_PROCESS_FORK). Create a thread and wake up the created thread.

Optionally, the above important event information may also include the process identification (process id, PID) of the awakened thread, the scheduling group corresponding to the awakened thread, the timestamp corresponding to the awakened thread (the time when the thread was awakened), the awakened thread The identification of the corresponding processor, the length of time the awakened thread has been running on the processor, the running frequency and other information. Among them, the awakened threads include rendering threads and main threads.

The main thread identification module of the electronic device can use the rendering thread as a starting point and use a traceback (backtracking) method to determine multiple threads with a wake-up relationship. When tracing back to a thread awakened by a kernel thread or a system interrupt, the electronic device no longer traces back. The electronic device obtains the execution order of the multiple threads based on the wake-up relationship between the multiple threads, and determines the target path based on the execution order of the multiple threads. The execution order of the multiple threads may be arranged from back to front (from late to early) according to the wake-up time.

It should be noted that the target path may include at least one (one or more). The starting point of each target path can be a rendering thread, and the end point of each target path can be a thread that is interrupted by a kernel thread or system, or awakened by an application thread.

Exemplarily, FIG. 11 shows a schematic diagram of a target path (first target path). As shown in Figure 11, the thread that wakes up the rendering thread is thread B, and the rendering thread is awakened by thread B at time point t2 (that is, thread B wakes up thread A at time point t2). The thread that wakes up thread B is thread A, and Thread B is awakened by thread A at time point t1. If thread A is awakened by a kernel thread or a system interrupt, the electronic device will no longer trace back. Among them, time point t2 is later than time point t1. The first target path may include the rendering thread, thread B, and thread A. The starting point of the first target path is the rendering thread and the end point is thread A.

In addition, in Figure 11 above, thread B not only wakes up the rendering thread, but also wakes up thread D. Since thread D is a thread that cannot be traced back to the rendering thread as the starting point, thread D is not included in the first target path. .

Exemplarily, FIG. 12 shows a schematic diagram of yet another target path (the second target path). As shown in Figure 12, the rendering thread can be awakened by thread C at time point t4, thread C can be awakened by the rendering thread at time point t5, and the rendering thread can be awakened by thread A at time point t6. It should be understood that the rendering thread can enter the dormant state after waking up thread C at time point t5, and then be reawakened by thread C at time point t4. If thread A is awakened by a kernel thread or a system interrupt, the electronic device will no longer trace back. Among them, time point t4 is later than time point t5, and time point t5 is later than time point t6. The second target path may include rendering thread, thread C, rendering thread, thread A. The starting point of the first target path is the rendering thread and the end point is thread A.

The electronic device may determine the main thread based on at least one target path. The main thread is the thread that serves as the end point most often on at least one target path.

For example, if at least one target path includes the first target path as shown in Figure 11 and the second target path as shown in Figure 12, since the end points of the first target path and the second target path are both thread A, therefore Thread A is the main thread.

816. The main thread identification module sends key thread group information to the key thread acceleration module.

The key thread group information is used to indicate the key thread group, and the key thread group may include a rendering thread and a main thread.

For example, the key thread group information may include the thread ID of the rendering thread and the thread ID of the main thread.

817. The key thread acceleration module accelerates key thread groups.

The key thread acceleration module can determine the scheduling group corresponding to the rendering thread and the main thread, the identifier of the processor, the running time on the processor, the running frequency and other information based on important event information, and accelerate the rendering thread and the main thread based on the above information. deal with.

The key thread acceleration module's acceleration of the rendering thread and main thread can include at least one of the following:

1). Increase the priority of the scheduling group corresponding to the rendering thread and the main thread. For example, if the scheduling group corresponding to the rendering thread and the main thread is determined to be the first priority scheduling group based on important event information before acceleration processing, the rendering thread and the main thread can be moved from the first priority scheduling group (for example, CFS scheduling group) Adjust to the second priority scheduling group (eg, VIP scheduling group), and the scheduling priority of the threads in the second priority scheduling group is higher than the threads in the first priority scheduling group. The electronic device may preferentially allocate processing resources to threads in the second priority scheduling group. In this way, the electronic device can prioritize threads in the second priority scheduling group to execute corresponding tasks.

2). Increase the frequency of the rendering thread and main thread.

The key thread acceleration module can increase the frequency of the corresponding processors of the rendering thread and the main thread, thereby improving the execution efficiency of the rendering thread and the main thread. For example, it is assumed that the frequency of the processor may include 1.0GHz, 1.5GHz, and 2.0GHz. If the frequency of the processor corresponding to the rendering thread and the main thread is determined to be 1.0GHz based on important event information before acceleration processing, the frequency of the processor corresponding to the rendering thread and the main thread can be increased to 1.5GHz or 2.0GHz.

Optionally, a processor with higher computing power can be allocated to the rendering thread and the main thread, thereby improving the execution efficiency of the rendering thread and the main thread. For example, if before acceleration processing, it is determined based on important event information that the rendering thread and the main thread correspond to the first CPU and the frequency of the first CPU is 1.0GHz, the rendering thread and the main thread can be reallocated to the second CPU and the frequency of the second CPU for 1.5GHz or 2.0GHz.

3). Increase the thread priority of the rendering thread and the main thread.

That is, the priority of the rendering thread and the main thread in the scheduling group can be increased. For example, if the thread priority of the rendering thread and the main thread is the third priority before acceleration processing, the rendering thread and the main thread can be raised from the third priority to the fourth priority, and the fourth priority is higher than the third priority. Priority, the fourth priority thread in the same scheduling group executes before the third priority thread.

For example, as shown in Figure 13, the scheduling group of the rendering thread and/or the main thread can be set to the VIP scheduling group instead of the CFS scheduling group. It should be understood that the processing performance of the real time (RT) scheduling group is higher than that of the VIP scheduling group, and the processing performance of the VIP scheduling group is higher than that of the completely fair scheduler (CFS) scheduling group. Further, the processor corresponding to the rendering thread and/or the main thread can be set to a large-core processor. It should be understood that a large-core processor has a higher processing speed than a mid-core processor, and a mid-core processor has a higher processing speed than a small-core processor. Furthermore, the frequency of the rendering thread and/or the main thread can be increased. Furthermore, you can set the thread priority of the rendering thread and/or the main thread to high.

Alternatively, as shown in Figure 14, the scheduling group of the rendering thread and/or the main thread can be set to the VIP scheduling group instead of the CFS scheduling group. Further, the rendering thread and/or the main thread can be increased in frequency. Furthermore, you can set the thread priority of the rendering thread and/or the main thread to high.

It should be understood that in scenarios where barrage display, navigation display, or the user continues to slide the interface, processes such as frame drawing, rendering, and synthesis can be carried out all the time, and steps 808 to 817 can be executed in a loop. In a scenario where the barrage display is turned off (the barrage is turned off), the navigation display is turned off (the navigation is turned off), or the sliding interface is stopped, steps 808 to 817 may no longer be executed.

Based on the method provided by the embodiments of this application, by identifying the rendering thread and the main thread, and then accurately allocating resources to the rendering thread and the main thread, frame loss and lag can be avoided, thereby improving the user experience.

Taking the video application as an example, after experimental verification, after using the solution provided by the embodiment of the present application to identify and accelerate the rendering thread and main thread corresponding to the barrage layer of the video application, as shown in Figure 15, the number of rendering threads can be significantly reduced The time (for example, thread 205) is in the runnable state. As shown in Table 1, when the increase in power consumption is small (the increase in current is small and the increase in power consumption is small), the frame rate can be significantly increased (an average increase of 4 frames per second), frame loss can be reduced, and lags can be avoided. . As shown in (a) and (b) in Figure 16, compared with Figure 2, the barrage 1002 and barrage 1004 of the barrage layer can be scrolled and displayed as the video plays, without any lag, thus improving the user experience. experience.

Table 1

Some embodiments of the present application provide an electronic device, which may include a touch screen, a memory, and one or more processors. The touch screen, memory and processor are coupled. The memory is used to store computer program code, which includes computer instructions. When the processor executes computer instructions, the electronic device may perform various functions or steps performed by the electronic device in the above method embodiments. The structure of the electronic device may refer to the structure of the electronic device 100 shown in FIG. 5 .

An embodiment of the present application also provides a chip system (for example, a system on a chip (SoC)). As shown in FIG. 17 , the chip system includes at least one processor 1701 and at least one interface circuit 1702 . The processor 1701 and the interface circuit 1702 may be interconnected by wires. For example, interface circuitry 1702 may be used to receive signals from other devices, such as memory of an electronic device. As another example, interface circuit 1702 may be used to send signals to other devices, such as processor 1701 or a touch screen of an electronic device. For example, the interface circuit 1702 can read instructions stored in the memory and send the instructions to the processor 1701. When the instructions are executed by the processor 1701, the electronic device can be caused to perform various steps in the above embodiments. Of course, the chip system may also include other discrete devices, which are not specifically limited in the embodiments of this application.

Embodiments of the present application also provide a computer-readable storage medium. The computer-readable storage medium includes computer instructions. When the computer instructions are run on the above-mentioned electronic device, the electronic device causes the electronic device to execute the electronic device in the above method embodiment ( For example, each function or step performed by a mobile phone).

Embodiments of the present application also provide a computer program product. When the computer program product is run on an electronic device, it causes the electronic device to perform various functions or steps performed by the electronic device (for example, a mobile phone) in the above method embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In practical applications, the above functions can be allocated according to needs. Different functional modules are completed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be The combination can either be integrated into another device, or some features can be omitted, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated. The components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place, or they may be distributed to multiple different places. . Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application are essentially or contribute to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the software product is stored in a storage medium , including several instructions to cause a device (which can be a microcontroller, a chip, etc.) or a processor to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes.

The above contents are only specific implementation modes of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be covered by the protection scope of the present application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (18)

1. A thread acceleration processing method, applied to electronic equipment, characterized by including: The electronic device receives a first operation from the user on the interface of the first application, and the first operation is used to trigger the electronic device to display target information; The electronic device obtains the thread identifier of the rendering thread, and the rendering thread is used to perform layer rendering to obtain a rendered layer, and the rendered layer corresponds to the target information; The electronic device determines the main thread that has a wake-up relationship with the rendering thread according to the thread identifier of the rendering thread; The electronic device performs accelerated processing on the rendering thread and the main thread. 2. The method according to claim 1, characterized in that the accelerated processing includes at least one of the following: Adjust the rendering thread and the main thread from the first priority scheduling group to the second priority scheduling group, and the scheduling priority of the threads in the second priority scheduling group is higher than the first priority scheduling Threads in the group; Perform frequency increase processing on the rendering thread and the main thread; Increase the thread priority of the rendering thread and the main thread. 3. The method according to claim 1 or 2, characterized in that before the electronic device obtains the thread identifier of the rendering thread, the method further includes: The electronic device inserts an instrumentation function into the insertion point of the queue function corresponding to the rendering thread; The electronic device obtains the thread identifier of the rendering thread including: When the electronic device executes the insertion point of the enqueuing function, instrumentation information is obtained, and the instrumentation information includes the thread identification of the rendering thread. 4. The method according to any one of claims 1 to 3, characterized in that, the electronic device determines the main thread that has a wake-up relationship with the rendering thread according to the thread identifier of the rendering thread, including: The electronic device traces at least one thread with a wake-up relationship in the current drawing frame period based on the important event information recorded in the current drawing frame period, starting from the rendering thread, and the important event information includes the relationship between threads. A wake-up event, and the wake-up relationship is used to represent the relationship between threads waking up and being woken up; The electronic device determines at least one target path based on a wake-up relationship between the at least one thread; The electronic device determines the main thread according to the at least one target path, and the main thread is the thread that serves as the end point of the path the most times in the at least one target path. 5. The method according to claim 4, characterized in that, The important event information also includes the identifier of the processor corresponding to the awakened thread, the scheduling group corresponding to the awakened thread, the running time of the awakened thread on the processor, the time the awakened thread has been running on the processor. At least one of running frequency on the processor, the awakened thread includes the rendering thread and the main thread; The electronic device's acceleration of the rendering thread and the main thread includes: The electronic device determines according to the identifier of the processor corresponding to the awakened thread, the scheduling group corresponding to the awakened thread, the running time of the awakened thread on the processor, and the time the awakened thread has been running on the processor. At least one of a running frequency on the processor accelerates the rendering thread and the main thread. 6. The method according to claim 4 or 5, characterized in that the method further comprises: When the electronic device traces back to a thread that is awakened by a kernel thread or a system interrupt or an application thread, the trace is no longer continued. 7. The method according to any one of claims 1-6, characterized in that the method further includes: The electronic device compares the thread identifier of the rendering thread with a standard thread identifier; The thread identifier of the rendering thread is different from the standard thread identifier. 8. The method according to any one of claims 1-7, characterized in that, The thread identifier of the rendering thread is the thread identifier customized by the first application. 9. The method according to any one of claims 1-8, characterized in that, The rendering thread includes: at least one of a barrage rendering thread, a navigation rendering thread, a game rendering thread, and a mini program rendering thread. 10. The method according to claim 9, characterized in that, When the rendering thread is a barrage rendering thread, the rendered layer is a barrage layer; When the rendering thread is a navigation rendering thread, the rendered layer is a navigation layer; When the rendering thread is a game rendering thread, the rendered layer is a game layer; When the rendering thread is an applet rendering thread, the rendered layer is an applet layer. 11. The method according to any one of claims 1 to 10, characterized in that the rendering thread used to perform rendering processing on the target information includes: The rendering thread is used to perform layer drawing and layer rendering to obtain a rendered layer. 12. The method according to any one of claims 1 to 11, characterized in that the electronic device includes a rendering thread identification module, a message processing module, a main thread identification module and a key thread acceleration module; the electronic device obtains rendering The thread identifier of the thread includes: The rendering thread identification module pre-inserts an instrumentation function into the insertion point of the queue function corresponding to the rendering thread; When the insertion point of the queued function is executed, the rendering thread identification module obtains instrumentation information, and the instrumentation information includes the thread identification of the rendering thread; The electronic device determines the main thread that has a wake-up relationship with the rendering thread according to the thread identifier of the rendering thread, including: The rendering thread identification module sends the thread identification of the rendering thread to the message processing module; The message processing module sends the thread identification of the rendering thread to the main thread identification module; The main thread identification module determines the main thread that has a wake-up relationship with the rendering thread according to the thread identifier of the rendering thread; The electronic device accelerates the rendering thread and the main thread according to the thread identifier of the rendering thread and the thread identifier of the main thread, including: The main thread identification module sends key thread group information to the key thread acceleration module, where the key thread group information includes the thread identification of the rendering thread and the thread identification of the main thread; The key thread acceleration module performs acceleration processing on the key thread group, and the key thread group includes the rendering thread and the main thread. 13. The method according to claim 12, wherein the electronic device further includes a layer processing module and an image synthesis system, and before the electronic device obtains the thread identifier of the rendering thread, the method further includes: In response to the user's operation, the main thread sends a create layer request to the layer processing module; The layer processing module sends a request to obtain a buffer queue to the image synthesis system; The image synthesis system returns the buffer queue corresponding to the layer to the layer processing module; The layer processing module returns the attribute information of the layer to the main thread. 14. The method according to claim 13, characterized in that the method further comprises: The main thread requests a vertical synchronization signal from the image synthesis system; The image synthesis system returns a vertical synchronization signal to the main thread; The main thread wakes up the rendering thread; The rendering thread draws the rendered image. 15. The method according to claim 14, characterized in that the method further comprises: The rendering thread sends a request cache command to the image synthesis system; The image synthesis system sends an instruction for instructing cache dequeuing to the rendering thread; The rendering thread stores the rendered image into the buffer queue. 16. An electronic device, characterized in that the electronic device includes a processor, and the processor is used to run a computer program stored in a memory, so that the electronic device implements any one of claims 1-15 Methods. 17. A chip system, characterized in that it includes a processor, the processor is coupled to a memory, and the processor executes a computer program stored in the memory to implement the method according to any one of claims 1-15 . 18. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, and when the computer program is run on a processor, the method according to any one of claims 1-15 is implemented. .