sparrow-kata-full/apps/system/components/MemoryManager/MemoryManager.camkes
Sam Leffler b099005951 kata-os-logger: support no logging interface connection out of a component
When a CAmkES component lacks an outbound connection to send log msgs
there will be no logger_log symbol. Use a weak ref here to handle that
without resorting to a feature or similar.

Mark logger connections as "maybe" so they are optional.

Change-Id: I6ecd939014d26a612d115741fd2ac673afa40857
GitOrigin-RevId: 0b1bf2611cbb628500cae37889c6547a996d50e9
2022-10-06 19:00:19 +00:00

36 lines
1.3 KiB
Plaintext

// Copyright 2022 Google LLC
//
// 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
//
// https://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.
// Kata OS MemoryManager service.
import <LoggerInterface.camkes>;
import <MemoryInterface.camkes>;
component MemoryManager {
provides MemoryInterface memory;
maybe uses LoggerInterface logger;
// Enable KataOS CAmkES support.
attribute int kataos = true;
// Mark the component that should receive the unallocated UntypedMemory
// passed to the rootserver from the kernel. In addition to the
// capabilities the component also gets a page with Bootinfo data that
// includes updated UntypedMemory descriptors. In order to pass the
// capabilitiies the component's cnode is up-sized to be large enough
// to hold the extra capabilties.
attribute int untyped_memory = true;
}