================ @@ -120,6 +120,47 @@ In any case, if we want the normal detach behavior we will just send: D ``` +## jAcceleratorPluginInitialize + +This packet requests initialization data from all accelerator plugins +installed in lldb-server. Accelerator plugins allow lldb-server to support +debugging of hardware accelerators (e.g. GPUs, FPGAs) alongside the native +host process. This packet is only sent when the server reports the +`accelerator-plugins+` feature in its `qSupported` response. + +``` +LLDB SENDS: jAcceleratorPluginInitialize +STUB REPLIES: [<accelerator_action>,...] +``` + +Each `accelerator_action` is a JSON object with the following required fields: + +| Key | Type | Description | +|----------------|---------|-------------| +| `plugin_name` | string | Unique name identifying the accelerator plugin (e.g. `"mock"`, `"amdgpu"`). Each installed plugin has a distinct name. | +| `session_name` | string | Name for the DAP debug session associated with this plugin. May be empty. | ---------------- DavidSpickett wrote:
Please explain why this needs its own DAP session ID. It seems like a thing lldb-dap should be taking care of, when the underlying lldb has multiple targets, but I don't know a lot about how DAP works. Putting a DAP thing in the gdb-remote protocol seems strange on the surface. https://github.com/llvm/llvm-project/pull/198907 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
