1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
// Copyright 2026 Ethan Wu
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
//
// SPDX-License-Identifier: Apache-2.0
//! Doorbell API for signaling events between cores. This is a low-level primitive used by higher-level channel and transport implementations.
use crate::;
/// Notifies the remote core that something has happened.
/// Carries no data - pure signaling primitive.
///
/// The meaning of Chan:
/// HSEM: semaphore gate ID (0..=31)
/// MU: transmit register index (0..=3)
/// Serial: logical channel byte in frame header
/// Host: Unix socket / TCP port logical channel
///
/// # Ordering contract
///
/// `ring` is the publication edge for data written before signaling the peer.
/// Implementations must ensure those writes happen-before the corresponding
/// `wait` completion or `pending` observation on the receiving side. For
/// software pending bits this means a release operation in `ring` (or in the
/// interrupt producer) paired with an acquire operation in `wait`/`pending`, or
/// stronger ordering. For hardware-backed doorbells, the interrupt or MMIO
/// signal must not be observed by the peer before the shared-memory writes that
/// the signal publishes are visible.