Files
TheRock/rocm-systems/projects/clr/rocclr/device/devhcmessages.hpp
T
derek.holloway 7502bf64a4
CodeQL / Analyze (actions) (push) Canceled after 0s
CodeQL / Analyze (python) (push) Canceled after 0s
pre-commit / pre-commit (push) Canceled after 0s
Multi-Arch CI / setup (push) Canceled after 0s
Publish build_manylinux_x86_64 images / publish_build_manylinux_x86_64 (push) Canceled after 0s
Setup (Multi-Arch) / setup (push) Canceled after 0s
Multi-Arch CI / Linux::${{ fromJSON(needs.setup.outputs.linux_build_config || '{}').build_variant_label || 'skip' }} (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Publish no_rocm_image_ubi10 image / publish_no_rocm_image_ubi10 (push) Canceled after 0s
Multi-Arch CI / Windows::${{ fromJSON(needs.setup.outputs.windows_build_config || '{}').build_variant_label || 'skip' }} (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Multi-Arch CI / Manifest Diff (push) Canceled after 0s
TheRock Manifest Diff Report / Generate Manifest Diff Report (push) Canceled after 0s
Multi-Arch CI / CI Summary (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04 (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04_ocl_rt images / publish_no_rocm_image_ubuntu24_04_ocl_rt (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04_rocgdb (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04_rocgdb images / publish_no_rocm_image_ubuntu24_04_rocgdb (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04_ocl_rt (push) Canceled after 0s
Publish TheRock Docker image / build-and-push-image (push) Canceled after 0s
Unit Tests / Unit Tests :: ubuntu-24.04 (push) Canceled after 0s
Unit Tests / Unit Tests :: windows-2022 (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04_media (push) Canceled after 0s
Unit Tests / Unit Tests Summary (push) Canceled after 0s
Publish no_rocm_image_ubuntu24_04 images / publish_no_rocm_image_ubuntu24_04_openmpi (push) Canceled after 0s
Flatten subprojects into a single base monorepo
2026-09-02 16:34:47 -07:00

84 lines
2.9 KiB
C++

/*
* Copyright (c) Advanced Micro Devices, Inc., or its affiliates.
*
* SPDX-License-Identifier: MIT
*/
/** \file Concatenating hostcalls into a message
*
* A message is a stream of 64-bit integers transmitted as a series
* of hostcall invocations by the device code. Although the hostcall
* is "warp-wide", the message for each workitem is distinct.
*
* Of the eight uint64_t arguments in hostcall, the first argument is
* used as the message descriptor, while the rest are used for
* message contents. The descriptor consists of the following fields:
*
* - Bit 0 is the BEGIN flag.
* - Bit 1 is the END flag.
* - Bits 2-4 are reserved and must be zero.
* - Bits 5-7 indicate the number of elements being transmitted.
* - Bits 8-63 contain a 56-bit message ID.
*
* A hostcall with the BEGIN flag set in the descriptor indicates the
* start of a new message. A hostcall with the END flag set indicates
* the end of a message. A single hostcall can have both flags set if
* the message fits in the payload of a single hostcall. Each
* hostcall indicates the number of uint64_t elements in the payload
* that contain data to be appended to the message.
*
* When the message receives a hostcall with the BEGIN flag set, it allocates a
* new message ID, which is transmitted to the device via the first return
* value in the hostcall. Every subsequent hostcall containing the same message
* ID appends its payload to that message. The message is said to be "active"
* until a corresponding END hostcall is received.
*
* When the message handler receives a hostcall with the END flag set, it
* invokes the corresponding message handler on the contents of the
* accumulated message, and then discards the message. The handler
* may return up to two uint64_t values, that are transmitted to the
* device via the return value of the last hostcall.
*
* Behaviour is undefined in each of the following cases:
* - An END packet is received with a non-existent message ID, or with
* the ID of an inactive message (previously terminated by an END packet).
* - No END packet is received for an active message.
* - Any of the reserved bits are non-zero.
* - Different hostcalls indicate the same active message ID but a
* different service.
*/
#pragma once
#include <vector>
namespace amd {
enum ServiceID {
SERVICE_RESERVED = 0,
SERVICE_FUNCTION_CALL = 1,
SERVICE_PRINTF = 2,
SERVICE_DEVMEM = 3
#if defined(__clang__)
#if __has_feature(address_sanitizer)
,
SERVICE_SANITIZER = 4
#endif
#endif
};
struct Message;
class MessageHandler {
std::vector<uint64_t> freeSlots_;
std::vector<Message*> messageSlots_;
Message* newMessage();
Message* getMessage(uint64_t messageId);
void discardMessage(Message* message);
public:
~MessageHandler();
bool handlePayload(uint32_t service, uint64_t* payload);
};
} // namespace amd