feat: Integrate coolbpf cpu profiling feature in loongcollector

[wokron]

No description provided.

[CLAassistant]

All committers have signed the CLA.

[Copilot]

Pull Request Overview

This PR integrates coolbpf CPU profiling capabilities into loongcollector by adding a new input_cpu_profiling plugin. The implementation enables continuous CPU profiling of specified processes through command-line pattern matching and container discovery.

Key changes:

• New CPU profiling plugin with process discovery mechanism
• Integration with coolbpf profiler library
• Plugin registration and lifecycle management

Reviewed Changes

Copilot reviewed 39 out of 39 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
core/plugin/input/InputCpuProfiling.{h,cpp}	New plugin implementation for CPU profiling input
core/ebpf/plugin/cpu_profiling/*	Core CPU profiling manager and process discovery logic
core/ebpf/driver/CpuProfiler.h	Wrapper for coolbpf profiler library integration
core/ebpf/Config.{h,cpp}	CPU profiling configuration option handling
core/ebpf/include/export.h	Type definitions for CPU profiling
core/unittest/input/InputCpuProfilingUnittest.cpp	Unit tests for the input plugin
core/unittest/ebpf/*Unittest.cpp	Unit tests for CPU profiling components
Various CMakeLists.txt	Build system updates for new components

Comments suppressed due to low confidence (1)

core/unittest/input/InputCpuProfilingUnittest.cpp:1

• Corrected spelling of 'CommandLines' to 'CommandLines' in comment context.

[Copilot]

Static members mHandler and mCtx accessed without synchronization in handler_without_ctx, which is called from Poll() while holding a lock, but could race with Start() and Stop() that modify these members. The callback could be invoked with stale or null pointer values.

[Copilot]

Passing null handler and context to buildCpuProfilingConfig during update will overwrite the valid handler set during initialization, breaking profiling event handling.

[Copilot]

[nitpick] Fixed 100ms sleep interval for process discovery polling is aggressive and could cause unnecessary CPU usage. Consider making this configurable or using exponential backoff when no changes are detected.

[Copilot]

[nitpick] Magic numbers 5 and 100 for retry attempts and sleep duration should be extracted as named constants or made configurable to improve maintainability and allow tuning.

Suggested change

	int maxRetry = 5;
	for (int retry = 0; retry < maxRetry; ++retry) {
	if (QueueStatus::OK == ProcessQueueManager::GetInstance()->PushQueue(info.mQueueKey, std::move(item))) {
	break;
	}
	std::this_thread::sleep_for(std::chrono::milliseconds(100));
	if (retry == maxRetry - 1) {
	for (int retry = 0; retry < kMaxQueuePushRetry; ++retry) {
	if (QueueStatus::OK == ProcessQueueManager::GetInstance()->PushQueue(info.mQueueKey, std::move(item))) {
	break;
	}
	std::this_thread::sleep_for(std::chrono::milliseconds(kQueuePushRetrySleepMs));
	if (retry == kMaxQueuePushRetry - 1) {

[Copilot]

Clearing mRouter in HandleProcessDiscoveryEvent creates a race condition with HandleCpuProfilingEvent which reads from mRouter. Events arriving between clear and rebuild could be lost or routed incorrectly.

[Copilot]

Static member variables for instance-specific handler and context violate encapsulation and prevent multiple CpuProfiler instances from working correctly. This TODO should be addressed before production use.